Hi Dan! I've seen you did some tagging, branching _after_ we voted. I know this is kind of nit picking but we must ship _exactly_ the source binary we've voted on! No single bit change is allowed, that must have the exact same sha1!
Of course, we can do a release without the -RCx postfix, but we would then need to re-do the vote again. I know this sounds ridiculous in the first moment, but if the md5 changes, how could you be safe that nothing important got changed? LieGrue, strub --- On Mon, 6/20/11, Dan Haywood <[email protected]> wrote: > From: Dan Haywood <[email protected]> > Subject: Re: [VOTE] [RESULT] Apache Isis release candidate > 0.1.2-RC4-incubating > To: [email protected] > Date: Monday, June 20, 2011, 10:55 AM > Nour, > will do... > > can I ask though that you please don't post to [email protected], > > because I would like to. (I want to explain how the > release I would > like the vote on general relates to the release candidate > that was voted > on in isis-dev). > > Thx > Dan > > > > On 20/06/2011 10:49, Mohammad Nour El-Din wrote: > > +1 @Mark > > > > Would you please do it Dan so I announce the [VOTE] > pass on general@ > > and then we are ready to [VOTE] on there. > > > > On Mon, Jun 20, 2011 at 11:09 AM, Mark Struberg<[email protected]> > wrote: > >> Hi Dan! > >> > >> It's usus to explicitly list the names (or > apacheids) of those who voted. Just to make it a bit easier > to control. Could you please add those? > >> > >> txs and LieGrue, > >> strub > >> > >> --- On Mon, 6/20/11, Dan Haywood<[email protected]> > wrote: > >> > >>> From: Dan Haywood<[email protected]> > >>> Subject: [VOTE] [RESULT] Apache Isis release > candidate 0.1.2-RC4-incubating > >>> To: [email protected] > >>> Date: Monday, June 20, 2011, 7:43 AM > >>> This vote is now closed, and has > >>> passed: > >>> > >>> 6 +1 votes (+3 from members). > >>> No 0 votes > >>> No -1 votes. > >>> > >>> I am now going to cut the final release > (0.1.2-incubating) > >>> from the same revision, and will request a > lazy consensus > >>> vote on [email protected] > >>> for the final release. > >>> > >>> Thanks, all > >>> Dan > >>> > >>> > >>> > > > > >
