Remove the Code Freeze
Dev: https://dev.gitlab.org/gitlab/gitlabhq/issues/2166
It is hard for the core team since they constantly have to check slack to see if the code freeze is cancelled.
- Remove from monthly.md
- announce in core room
Sid
Dmitriy is OK with this.
P.S. As on 9/Dec/2015 this is listed as 7months ago.
Marin
Could you share your experience with the lack of code freeze for this release, if it influenced the release and update the documents accordingly?
Job
Lack of code freeze seemed really scary, but I think we broke it every release before it anyway. In the end it turned out the same as every release before it.
The lesson learned however, this release, is that you need ample time to
a) write good code and tests
b) release a package out of that
c) test it thoroughly on GitLab.com
d) release it to the world
Especially testing becomes more and more important and if anything goes wrong there, you're back to (a). That is something that bit us a bit with these releases.
Sid
Right now creating the stable branches is mentioned as part of 'Prepare CHANGELOG for next release' https://dev.gitlab.org/gitlab/gitlabhq/blob/master/doc/release/monthly.md#prepare-changelog-for-next-release
This is not mentioned in the schedule anywhere. Where are the stable branches created?
