[xwiki-devs] [VOTE] Better release strategy
Hi devs, I don't think that Monday is a good day for releases, since voting over the weekend is not a good thing. Thus, I propose to move the general release day to the Thursday of the week. The current release process doesn't really follow the VOTE rules, since the way it's done is: send vote mail at 10AM, wait a few hours, start the release around 1PM. The rule for VOTE emails is to wait for three days. Thus: - Send release VOTE on Monday - Prepare the release during the following three days (release plan, release notes) - Perform the maven release on Thursday, request tests for publishing the release (testing of the build) - Finalize the release on Friday (download, announcements, version update) -- Sergiu Dumitriu http://purl.org/net/sergiu/
+1 Caleb On 10/11/2010 06:00 AM, Sergiu Dumitriu wrote:
Hi devs,
I don't think that Monday is a good day for releases, since voting over the weekend is not a good thing. Thus, I propose to move the general release day to the Thursday of the week. The current release process doesn't really follow the VOTE rules, since the way it's done is: send vote mail at 10AM, wait a few hours, start the release around 1PM. The rule for VOTE emails is to wait for three days.
Thus: - Send release VOTE on Monday - Prepare the release during the following three days (release plan, release notes) - Perform the maven release on Thursday, request tests for publishing the release (testing of the build) - Finalize the release on Friday (download, announcements, version update)
+1 Thanks, Marius On 10/11/2010 01:00 PM, Sergiu Dumitriu wrote:
Hi devs,
I don't think that Monday is a good day for releases, since voting over the weekend is not a good thing. Thus, I propose to move the general release day to the Thursday of the week. The current release process doesn't really follow the VOTE rules, since the way it's done is: send vote mail at 10AM, wait a few hours, start the release around 1PM. The rule for VOTE emails is to wait for three days.
Thus: - Send release VOTE on Monday - Prepare the release during the following three days (release plan, release notes) - Perform the maven release on Thursday, request tests for publishing the release (testing of the build) - Finalize the release on Friday (download, announcements, version update)
+1, sounds good On Mon, Oct 11, 2010 at 12:00, Sergiu Dumitriu <[email protected]> wrote:
Hi devs,
I don't think that Monday is a good day for releases, since voting over the weekend is not a good thing. Thus, I propose to move the general release day to the Thursday of the week. The current release process doesn't really follow the VOTE rules, since the way it's done is: send vote mail at 10AM, wait a few hours, start the release around 1PM. The rule for VOTE emails is to wait for three days.
Thus: - Send release VOTE on Monday - Prepare the release during the following three days (release plan, release notes) - Perform the maven release on Thursday, request tests for publishing the release (testing of the build) - Finalize the release on Friday (download, announcements, version update)
-- Sergiu Dumitriu http://purl.org/net/sergiu/ _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
+1 Regards, Sorin B. On 10/11/2010 01:00 PM, Sergiu Dumitriu wrote:
Hi devs,
I don't think that Monday is a good day for releases, since voting over the weekend is not a good thing. Thus, I propose to move the general release day to the Thursday of the week. The current release process doesn't really follow the VOTE rules, since the way it's done is: send vote mail at 10AM, wait a few hours, start the release around 1PM. The rule for VOTE emails is to wait for three days.
Thus: - Send release VOTE on Monday - Prepare the release during the following three days (release plan, release notes) - Perform the maven release on Thursday, request tests for publishing the release (testing of the build) - Finalize the release on Friday (download, announcements, version update)
Hi Sergiu, In general yes, I would say it's ok to have it later in the week (but rarely on Friday). so my +1 . However, I think the release should take less than 5 days to complete. It really should be simpler than that. Happy releasing, Anca On 11.10.2010 12:00, Sergiu Dumitriu wrote:
Hi devs,
I don't think that Monday is a good day for releases, since voting over the weekend is not a good thing. Thus, I propose to move the general release day to the Thursday of the week. The current release process doesn't really follow the VOTE rules, since the way it's done is: send vote mail at 10AM, wait a few hours, start the release around 1PM. The rule for VOTE emails is to wait for three days.
Thus: - Send release VOTE on Monday - Prepare the release during the following three days (release plan, release notes) - Perform the maven release on Thursday, request tests for publishing the release (testing of the build) - Finalize the release on Friday (download, announcements, version update)
+1 Alex On 10/11/2010 12:00 PM, Sergiu Dumitriu wrote:
Hi devs,
I don't think that Monday is a good day for releases, since voting over the weekend is not a good thing. Thus, I propose to move the general release day to the Thursday of the week. The current release process doesn't really follow the VOTE rules, since the way it's done is: send vote mail at 10AM, wait a few hours, start the release around 1PM. The rule for VOTE emails is to wait for three days.
Thus: - Send release VOTE on Monday - Prepare the release during the following three days (release plan, release notes) - Perform the maven release on Thursday, request tests for publishing the release (testing of the build) - Finalize the release on Friday (download, announcements, version update)
On Oct 11, 2010, at 12:00 PM, Sergiu Dumitriu wrote:
Hi devs,
I don't think that Monday is a good day for releases, since voting over the weekend is not a good thing. Thus, I propose to move the general release day to the Thursday of the week. The current release process doesn't really follow the VOTE rules, since the way it's done is: send vote mail at 10AM, wait a few hours, start the release around 1PM. The rule for VOTE emails is to wait for three days.
Thus: - Send release VOTE on Monday - Prepare the release during the following three days (release plan, release notes) - Perform the maven release on Thursday, request tests for publishing the release (testing of the build) - Finalize the release on Friday (download, announcements, version update)
-0 For me the process should be: - Release Manager performs the release in the staging repo on the planned day (planned during the roadmap process), whatever the day - A vote is sent to release it 3 days later. This means users and devs get a chance to test the version that will be released - if the vote is passed then the Release Manager promotes the release Note: When we do roadmap emails we should differentiate RC1 (== staging) from Final by at least 3 days, I think 5 days is safer though. Thanks -Vincent
On Mon, Oct 11, 2010 at 14:57, Vincent Massol <[email protected]> wrote:
On Oct 11, 2010, at 12:00 PM, Sergiu Dumitriu wrote:
Hi devs,
I don't think that Monday is a good day for releases, since voting over the weekend is not a good thing. Thus, I propose to move the general release day to the Thursday of the week. The current release process doesn't really follow the VOTE rules, since the way it's done is: send vote mail at 10AM, wait a few hours, start the release around 1PM. The rule for VOTE emails is to wait for three days.
Thus: - Send release VOTE on Monday - Prepare the release during the following three days (release plan, release notes) - Perform the maven release on Thursday, request tests for publishing the release (testing of the build) - Finalize the release on Friday (download, announcements, version update)
-0
For me the process should be:
- Release Manager performs the release in the staging repo on the planned day (planned during the roadmap process), whatever the day - A vote is sent to release it 3 days later. This means users and devs get a chance to test the version that will be released - if the vote is passed then the Release Manager promotes the release
Sounds good to me, but I also agree with Sergiu that we should avoid release on Mondays, which could reduce the testing time of the staging release due to the WE. So having official release date on thursday and starting release on Friday or Monday when we are late, could probably helps. WDYT ? Denis
Note: When we do roadmap emails we should differentiate RC1 (== staging) from Final by at least 3 days, I think 5 days is safer though.
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO
Hi, +1 on the stages of the process, with the mention that it should be done in less then 5 days. -0 on finalizing/announcing the release on Friday. IMHO it's worst day to release(lower visibility, low user traction, offline xwiki personnel during the days following the release). Thanks, Florin Ciubotaru On Mon, Oct 11, 2010 at 1:00 PM, Sergiu Dumitriu <[email protected]> wrote:
Hi devs,
I don't think that Monday is a good day for releases, since voting over the weekend is not a good thing. Thus, I propose to move the general release day to the Thursday of the week. The current release process doesn't really follow the VOTE rules, since the way it's done is: send vote mail at 10AM, wait a few hours, start the release around 1PM. The rule for VOTE emails is to wait for three days.
Thus: - Send release VOTE on Monday - Prepare the release during the following three days (release plan, release notes) - Perform the maven release on Thursday, request tests for publishing the release (testing of the build) - Finalize the release on Friday (download, announcements, version update)
-- Sergiu Dumitriu http://purl.org/net/sergiu/ _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
participants (10)
-
Alex Busenius -
Anca Luca -
Caleb James DeLisle -
Denis Gervalle -
Florin Ciubotaru -
Marius Dumitru Florea -
Sergiu Dumitriu -
Sorin Burjan -
Thomas Mortagne -
Vincent Massol