openstack-poc team mailing list archive
-
openstack-poc team
-
Mailing list archive
-
Message #00121
Re: PPB Meeting on June 2nd
+1
On Tue, May 31, 2011 at 02:28:04PM -0700, Joshua McKenty wrote:
> +1
>
> Joshua McKenty
> Piston Cloud Computing, Inc.
> (650) 283-6846
> joshua@xxxxxxxxx
>
>
>
> On 2011-05-31, at 10:15 AM, John Purrier wrote:
>
> > +1.
> >
> > This will not slow the development of the projects and allows logical
> > management of the projects to be promoted to "core". In order to make this
> > happen we will need to lead the DS timelines, as ttx points out, to allow
> > PTL elections and to involve the new project PTL's in the upcoming DS
> > planning.
> >
> > This timeline should be published as part of the overall project lifecycle
> > we are developing (inception/affiliated -> incubation -> core project).
> > Always recognizing that some projects will stop/hold at specific steps in
> > the process (not all project should/can progress to incubated or core).
> >
> > John
> >
> > -----Original Message-----
> > From: openstack-poc-bounces+john=openstack.org@xxxxxxxxxxxxxxxxxxx
> > [mailto:openstack-poc-bounces+john=openstack.org@xxxxxxxxxxxxxxxxxxx] On
> > Behalf Of Thierry Carrez
> > Sent: Tuesday, May 31, 2011 4:35 AM
> > To: openstack-poc@xxxxxxxxxxxxxxxxxxx
> > Subject: [Openstack-poc] PPB Meeting on June 2nd
> >
> > Hey everyone,
> >
> > I won't be able to make the PPB meeting this Thursday. This is a bank
> > holiday over here and we are having people for dinner. If you have the
> > meeting without me, just a few remarks about Core projects promotion vs.
> > release management.
> >
> > I think projects shouldn't be promoted to "Core projects" status in the
> > middle of a development cycle. The reason is that I need to follow Core
> > projects from a release management perspective (plans, milestone
> > contents, etc.) and you can't just start doing it in the middle of a
> > cycle and pray for a successful coordinated release at the end. They
> > need to be Core projects for the whole cycle, so decided before the
> > design summit time.
> >
> > So we can definitely promote projects to Incubation status, at which
> > point I'd start educating them on release management requirements to
> > make sure they can move to Core status for the next release. And we
> > should decide, at least one month before the design summit, that a given
> > Incubating project will be a Core project for the E development cycle.
> > The corresponding PTLs can then join in time the design summit
> > organization committee and the PPB.
> >
> > But IMHO we shouldn't promote Dashboard, or Burrow, or ScalR to Core
> > status for Diablo, since Diablo is already well started.
> >
> > At that point I'd concentrate our efforts in defining "Incubation" and
> > making sure the right projects enter that state ASAP.
> >
> > --
> > Thierry Carrez (ttx)
> > Release Manager, OpenStack
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~openstack-poc
> > Post to : openstack-poc@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~openstack-poc
> > More help : https://help.launchpad.net/ListHelp
> >
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~openstack-poc
> > Post to : openstack-poc@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~openstack-poc
> > More help : https://help.launchpad.net/ListHelp
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack-poc
> Post to : openstack-poc@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack-poc
> More help : https://help.launchpad.net/ListHelp
Follow ups
References