cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Tutkowski <mike.tutkow...@solidfire.com>
Subject Re: [VOTE] Apache Cloudstack 4.2.0
Date Fri, 23 Aug 2013 20:01:20 GMT
OK - thanks for the info...just trying to make sure I understand the
process pretty well.


On Fri, Aug 23, 2013 at 1:58 PM, Sudha Ponnaganti <
sudha.ponnaganti@citrix.com> wrote:

> It was good to have but never a blocker for release from prior releases.
> However if community can close critical/blockers atleast that would help
> greatly to have confidence in the fixed areas.
>
> -----Original Message-----
> From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com]
> Sent: Friday, August 23, 2013 12:53 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [VOTE] Apache Cloudstack 4.2.0
>
> Would we consider releasing if those resolved defects that were referred
> to in another e-mail have not been formally closed or is that a
> prerequisite for release?
>
> Thanks
>
>
> On Fri, Aug 23, 2013 at 1:47 PM, Maurice Lawler <maurice.lawler@me.com
> >wrote:
>
> > Thank you both for directing me to the correct link, greatly appreciated.
> >
> >
> >
> > On Aug 23, 2013, at 03:19 PM, Chiradeep Vittal <
> > Chiradeep.Vittal@citrix.com> wrote:
> >
> > You may be looking at the 4.1 section. The actual RN will contain the
> > complete list. In the meantime
> > https://issues.apache.org/jira/issues/?filter=12323963
> >
> > From: Maurice Lawler
> > <maurice.lawler@me.com<mailto:maurice.lawler@me.com>>
> > Reply-To:
> > "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" <
> > dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>>
> > Date: Friday, August 23, 2013 12:12 PM
> > To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" <
> > dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>>
> > Cc: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" <
> > dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>>
> > Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> >
> > I was reviewing the changes, I do not see what was previously told me
> > that there would be multiple IP support in 4.2
> >
> >
> > https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;
> > f=CHANGES;hb=4.2
> >
> > Did that hit the cutting room floor for this pending release?
> >
> > - Maurice
> >
> > On Aug 23, 2013, at 02:55 PM, Animesh Chaturvedi <
> > animesh.chaturvedi@citrix.com<mailto:animesh.chaturvedi@citrix.com>>
> > 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=shortlog;h=
> > refs/heads/4.2
> > Commit: 06f28722b6fe5827d58861e9a9d47fe46aaafefa
> >
> > List of changes:
> >
> > https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;
> > 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+test+pr
> > ocedure
> >
> > 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)
> >
> >
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkowski@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud<http://solidfire.com/solution/overview/?video=play>
> *(tm)*
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*™*

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message