(stable) Promote 2015 Week 40
Description
Description
Details
Details
- Auditors
chad - Provenance
epriestley Authored on epriestley Pushed on Oct 3 2015, 12:09 PM - Differential Revision
- D14227: Improve Diffusion behavior for no-longer-existing commits
- Parents
- rP0db86cce7df7: Improve Diffusion behavior for no-longer-existing commits
rP6d7b78f791f0: (stable) Fix issue with "Publish/Notify" handling in repositories - Branches
- Unknown
- Tags
- Unknown
- Build Status
Buildable 8169 Build 9332: Run Core Tests
Event Timeline
Comment Actions
Don't stable releases typically trail master by a week? Does this intentionally promote the current state of master?
Comment Actions
master is always promoted directly to stable, we don't have a stable-candidate branch or anything like that. It's intentional that changes may promote to stable after being in master for a day (if they're committed on Friday) or even only momentarily (if they're committed early Saturday morning).
Merged Changes
Merged Changes
- 2728a9f9649e Allow builds to have parametersAuthor
- 98006f2cf365 Update Asana LogoAuthorRevisions
- 52040bc9e4b9 Update `quickstart.sql`AuthorRevisions
- ffbcefb62957 Fix a doc typoAuthorRevisions
