> -----Original Message-----
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: Monday, August 26, 2013 1:22 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [VOTE] Apache Cloudstack 4.2.0
>
> I have actually received some critical info from VMworld about how
> people what to use the SolidFire plug-in.
>
> It is a small, but important change.
>
> Can I put my fix in?
>
[Animesh>] What is the nature of change and risk of regression? Can it wait for
4.2.1? Do you have a tested fix available now?
>
> On Mon, Aug 26, 2013 at 2:13 PM, Animesh Chaturvedi <
> animesh.chaturv...@citrix.com> wrote:
>
> >
> >
> > > -----Original Message-----
> > > From: Chip Childers [mailto:chip.child...@sungard.com]
> > > Sent: Monday, August 26, 2013 9:38 AM
> > > To: dev@cloudstack.apache.org
> > > Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> > >
> > > On Mon, Aug 26, 2013 at 12:02:32PM -0400, Chip Childers wrote:
> > > > On Fri, Aug 23, 2013 at 06:55:03PM +0000, Animesh Chaturvedi
> wrote:
> > > > >
> > > > >
> > > > > Hi All,
> > > > >
> > > > > I've created a 4.2.0 release, with the following artifacts up
> > > > > for a
> > > > > vote:
> > > > >
> > > > > Git Branch and Commit SH:
> > > > > https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=short
> > > > > log;
> > > > > h=refs/heads/4.2
> > > > > Commit: 06f28722b6fe5827d58861e9a9d47fe46aaafefa
> > > > >
> > > > > List of changes:
> > > > > https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_
> > > > > plai
> > > > > n;f=CHANGES;hb=4.2
> > > > >
> > > > > Source release (checksums and signatures are available at the
> > > > > same
> > > > > location):
> > > > > https://dist.apache.org/repos/dist/dev/cloudstack/4.2.0/
> > > > >
> > > > > PGP release keys (signed using 94BE0D7C):
> > > > > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> > > > >
> > > > > Testing instructions are here:
> > > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+t
> > > > > est+
> > > > > procedure
> > > > >
> > > > > Vote will be open for 72 hours.
> > > > >
> > > > > For sanity in tallying the vote, can PMC members please be sure
> > > > > to
> > > indicate "(binding)" with their vote?
> > > > >
> > > > > [ ] +1 approve
> > > > > [ ] +0 no opinion
> > > > > [ ] -1 disapprove (and reason why)
> > > > >
> > > > >
> > > >
> > > > -1 (binding)
> > > >
> > > > The reason is my fault. I forgot that I committed to adding the
> > > > legal docs for this: http://markmail.org/message/rrxypu25fwyxjdae
> > > >
> > > > I am working on it now.
> > > >
> > > > -chip
> > >
> > > Resolved now in master / 4.2 / 4.2-forward
> > [Animesh>] I will create a new RC and start a new VOTE. If this is the
> > only change (mostly textual) does the VOTE has to be open for still 72
> > hours?
> >
> >
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud<http://solidfire.com/solution/overview/?video=play>
> *(tm)*
