Placeholder .... for our next release.
helmo created an issue. See original summary.
We're long over due for a release ..
I'm preparing release notes in http://docs.aegirproject.org/en/3.x/release-notes/3.5/
I'd like to merge my patches from #2698027: Minor release to update core? and do an 3.5-rc1 release. (or a real one...)
Any other release blockers?
Would it work if I were to push a 3.5-rc1 and skip step 10 from http://docs.aegirproject.org/en/3.x/community/release-process/ ? Then the rc1 debian package should stay in the unstable channel of our repo.
To get the makefiles working I'd still need to create release nodes on Drupal.org though.
I just pushed the release tags ... will proceed with the next steps
Release notes on http://docs.aegirproject.org/en/3.x/release-notes/3.5/
Automatically closed - issue fixed for 2 weeks with no activity.
Comments
Comment #2
helmo commentedComment #3
helmo commentedWe're long over due for a release ..
I'm preparing release notes in http://docs.aegirproject.org/en/3.x/release-notes/3.5/
I'd like to merge my patches from #2698027: Minor release to update core? and do an 3.5-rc1 release. (or a real one...)
Any other release blockers?
Comment #4
helmo commentedWould it work if I were to push a 3.5-rc1 and skip step 10 from http://docs.aegirproject.org/en/3.x/community/release-process/ ?
Then the rc1 debian package should stay in the unstable channel of our repo.
To get the makefiles working I'd still need to create release nodes on Drupal.org though.
Comment #5
helmo commentedI just pushed the release tags ... will proceed with the next steps
Comment #6
helmo commentedComment #7
helmo commentedRelease notes on http://docs.aegirproject.org/en/3.x/release-notes/3.5/