Sorry to come in late. We have to include "incubating" in the release artifact name. See: http://incubator.apache.org/guides/releasemanagement.html
+1 to first running a vote on phoenix dev first. This will make release process longer, but it may be worth it. It would also be good to have a release document started somewhere where the release managers would just carry out the tasks. Similar to http://hbase.apache.org/book/releasing.html or http://wiki.apache.org/hadoop/HowToRelease. Enis On Sun, Feb 16, 2014 at 5:48 PM, lars hofhansl <[email protected]> wrote: > Agreed. > > > > ________________________________ > From: Andrew Purtell <[email protected]> > To: dev <[email protected]> > Sent: Sunday, February 16, 2014 5:30 PM > Subject: Re: [VOTE] The 3rd Phoenix 2.2.3 release candidate is available > for download > > > I do think it is good that Phoenix runs its own vote first. > > > > On Sun, Feb 16, 2014 at 5:19 PM, lars hofhansl <[email protected]> wrote: > > > I guess there is no formal process *before* you put this up for vote on > > the incubator list. > > Once you put it up for vote there 3 PMC member need to +1. > > James, wanna put it for vote there? I promise I'll check out the release. > > > > -- Lars > > > > > > > > ________________________________ > > From: James Taylor <[email protected]> > > To: "[email protected]" <[email protected] > >; > > lars hofhansl <[email protected]> > > Sent: Sunday, February 16, 2014 4:56 PM > > Subject: Re: [VOTE] The 3rd Phoenix 2.2.3 release candidate is available > > for download > > > > > > I thought we needed three +1 votes from IPMC members? Or do we close this > > and open a new one on the general list? > > > > > > > > On Sun, Feb 16, 2014 at 1:44 PM, lars hofhansl <[email protected]> wrote: > > > > > Three +1's are sufficient. Sorry I did not manage to look at it. > > > > > > > > > > > > ________________________________ > > > From: James Taylor <[email protected]> > > > To: "[email protected]" < > [email protected] > > > > > > Sent: Sunday, February 16, 2014 12:57 PM > > > Subject: Re: [VOTE] The 3rd Phoenix 2.2.3 release candidate is > available > > > for download > > > > > > > > > So far, we have 3 +1 votes from myself, Mujtaba, and Andrew. Should we > > > close the vote and start a new one on the general list? Wait longer? > Not > > > sure how to proceed, but I'd like to get this out before we release > 3.0! > > > > > > Thanks, > > > James > > > > > > > > > > > > On Wed, Feb 12, 2014 at 4:48 PM, Mujtaba Chohan <[email protected]> > > > wrote: > > > > > > > The 3rd Phoenix 2.2.3 release candidate (RC2) is available for > download > > > at > > > > http://people.apache.org/~mujtaba/phoenix-2.2.3RC2/ > > > > Signed with my code signing key: 17AF6E3F > > > > > > > > This is source and binary release. Unfortunately the last > > > > RC1<http://people.apache.org/~mujtaba/phoenix-2.2.3RC1/> was > > > > sunk due some files missing license header and containing copyright [ > > > > PHOENIX-45 <https://issues.apache.org/jira/browse/PHOENIX-45>] . > > > > > > > > Jenkins run for 2.2.3 RC2 > > > > https://builds.apache.org/job/Phoenix-2.2.3/5/ > > > > > > > > Please try out the new RC. It would upgrade your existing table > > metadata > > > on > > > > first connection. > > > > > > > > Vote +1/-1 by Feb 14 on whether we should release this as 2.2.3. > > > > > > > > Thanks, > > > > Mujtaba > > > > > > > > > > > > > -- > Best regards, > > - Andy > > Problems worthy of attack prove their worth by hitting back. - Piet Hein > (via Tom White) >
