Michael brought this up yesterday w/ the suggestion that we make cutting a release even easier still by including a standard ./release script (actually he suggested ./configure but I think that convention might come w/ unintended baggage).
I'm not convinced the speed issue w/ cutting a release is the actual compile/compose we do today---but it would make the Coho tool significantly dumber which would make it way easier for downstream distributions to live w/ what we do. I'm realizing--this warrants a new thread---I'll kick that up. On Wed, Dec 19, 2012 at 10:38 AM, Joe Bowser <[email protected]> wrote: > Actually, given that it takes us a week to actually do a release, I > don't think we can get the final release out by the end of the week, > even though it appears activity on the repositories is slowing down. > :S > > I'll have to agree to a January release. > > On Wed, Dec 19, 2012 at 10:14 AM, Filip Maj <[email protected]> wrote: >> It's getting awfully close to a break. I'm heading out on vacation >> tomorrow. >> >> How do people feel about letting rc2 simmer over the break and releasing >> 2.3 first thing January? >> >> On 12/19/12 10:10 AM, "Joe Bowser" <[email protected]> wrote: >> >>>Can we start tagging the release today? >>> >>>On Wed, Dec 19, 2012 at 6:33 AM, Marcel Kinard <[email protected]> wrote: >>>> +1, FWIW. I'd like to see 2.3.0 out before the break. >>>> >>>> -- Marcel Kinard >>>> >>>> >>>> On 12/17/2012 1:25 PM, Joe Bowser wrote: >>>>> >>>>> Hey >>>>> >>>>> How about Wednesday/Thursday for tagging 2.3.0 final? I know that we >>>>> haven't fully released 2.3.0rc2, but I know that many, if not the >>>>> majority of the committers are going to be on holiday at the end of >>>>> this week and it would be good if we could get 2.3.0 out before break. >>>>> >>>>> Thoughts? >>>>> >>>>> Joe >>>> >>>> >>
