I'm okay with Michael's earlier proposal for a 4 week release cycle. That would mean we're releasing at the end of the July and end of August, which is good.
Eli, I think we'll get the hang of turning the crank on the release management stuff. The first time through might be a little painful though. -N Nicholas Gallardo WebSphere - REST & WebServices Development [email protected] Phone: 512-286-6258 Building: 903 / 5G-016 "Baram, Eliezer" <[email protected]> To 07/21/2009 05:35 "[email protected]" AM <[email protected]> cc Please respond to Subject wink-...@incubato RE: [discuss] Wink Release Strategy r.apache.org Hi +1 for the regular release schedule. I haven't gather an opinion regarding the gap between releases. I rather releasing every end of month (easier to sync, and it should leave enough time for development), but I'm concern about the time it take to actually release the RC. I guess that after a release or two we will have better notion about the time the release process takes. --Eli -----Original Message----- From: Michael Elman [mailto:[email protected]] Sent: Tuesday, July 21, 2009 9:05 AM To: [email protected] Subject: Re: [discuss] Wink Release Strategy +1 for regular release. IMO for the next 2-3 releases, the interval can be shorter: a month. So we can head the release to the end of the month: 0.1 end of July, 0.2 end of August and 0.3 end of September. Thus, the development will last about 3 weeks and about 10 days are left the the release candidates. This will shorten the development time of the release, but we will be able to be more responsive to the problems that users may rise. On Tue, Jul 21, 2009 at 8:36 AM, Nicholas L Gallardo <[email protected]>wrote: > > > All, > > The discussion started last week to release Wink 0.1 as soon as possible. > In the interest of preventing scope creep and getting something out soon, > I'd like to make a proposal for release strategy for Wink beyond the 0.1 > release. > > A regular (or semi-regular) release interval will provide developers steady > time lines with which to plan contributions to Wink. Regular releases also > give users an interval in which they can expect service for issues they've > found in previous releases. I propose we find a regular release interval > for Wink so that we can start laying out what features we want to > prioritize and roll into the next few releases. > > For the short term (maybe through the next 3-4 releases), how does a 6-week > release interval sound? That provide at least 4 weeks of development time > and 2 week for publishing a release candidate and doing any additional > clean-up. Once the churn slows down, the interval could extend out if > there's nothing significant to release. > > Thoughts? > > -Nick > > > > Nicholas Gallardo > WebSphere - REST & WebServices Development > [email protected] > Phone: 512-286-6258 > Building: 903 / 5G-016
