This process change is now completed for all "integrated" projects.
I updated the wiki so that it reflects the new usage of the blueprints
fields:
https://wiki.openstack.org/wiki/Blueprints
Regards,
--
Thierry Carrez (ttx)
___
OpenStack-dev mailing
No objections here. I'll sync with Flavio and see if we can take the
proposal for a test drive in Marconi.
On 6/28/13 9:53 AM, "Flavio Percoco" wrote:
>On 19/06/13 15:51 +0200, Thierry Carrez wrote:
>>
>>Thoughts ?
>
>Although it is not an integrated project - not even incubated - we've
>been do
On 19/06/13 15:51 +0200, Thierry Carrez wrote:
Thoughts ?
Although it is not an integrated project - not even incubated - we've
been doing this for Marconi as well and it's been quite a pain. Also,
I've been following how Glance's blueprints have evolved and again,
I've noticed how hard it is
Thierry Carrez wrote:
> Thierry Carrez wrote:
>> A script will automatically and regularly align "series goal" with
>> "target milestone", so that the series and milestone views are
>> consistent (if someone sets target milestone to "havana-3" then the
>> series goal will be set to "havana").
>
>
Thierry Carrez wrote:
> A script will automatically and regularly align "series goal" with
> "target milestone", so that the series and milestone views are
> consistent (if someone sets target milestone to "havana-3" then the
> series goal will be set to "havana").
Now if the Launchpad API was exp
Perfect.
On Thu, Jun 20, 2013 at 5:20 AM, Thierry Carrez wrote:
> Mark Washenberger wrote:
> > This sounds like a fantastic improvement. I'd really like to have a
> > "next" milestone as well as an "Ongoing" milestone, for tracking the
> > kinds of long, drawn out refactorings / code improvement
Mark Washenberger wrote:
> This sounds like a fantastic improvement. I'd really like to have a
> "next" milestone as well as an "Ongoing" milestone, for tracking the
> kinds of long, drawn out refactorings / code improvements that cannot
> fit in a single milestone but still need to be communicated
On Wed, Jun 19, 2013 at 2:16 PM, Russell Bryant wrote:
> On 06/19/2013 09:51 AM, Thierry Carrez wrote:
> > Thoughts ?
>
> Big +1 from me. Keeping series goal and milestone fields in sync has
> been quite a pain.
>
> --
> Russell Bryant
>
> ___
> OpenSt
On 06/19/2013 09:51 AM, Thierry Carrez wrote:
> Thoughts ?
Big +1 from me. Keeping series goal and milestone fields in sync has
been quite a pain.
--
Russell Bryant
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.opensta
On Wed, Jun 19, 2013 at 6:51 AM, Thierry Carrez wrote:
> Hi everyone,
>
> What follows is mostly of interest to PTLs and other $PROJECT-drivers
> that help them maintain Launchpad blueprints in order.
>
> Launchpad has a concept of "series goal" and "priority" (controlled by
> drivers), while most
On Wed, Jun 19 2013, Thierry Carrez wrote:
Hi,
[…]
> This also encourages people to set a target milestone, which is pretty
> essential in communicating out when a given feature is likely to land.
Which have been the most common problem Ceilometer had for the Havana
serie. People don't set mile
Hi everyone,
What follows is mostly of interest to PTLs and other $PROJECT-drivers
that help them maintain Launchpad blueprints in order.
Launchpad has a concept of "series goal" and "priority" (controlled by
drivers), while most other fields (including "target milestone") can be
modified by blue
12 matches
Mail list logo
