Re: [openstack-dev] [Fuel] Moved blueprints out of 8.0

2015-12-11 Thread Dmitry Klenov 
Hi Mike,

Yes, I agree that we cannot move blueprints to "Implemented" unless all
dependencies are complete (incl tests and doc). Probably we can use "Beta
available" for such tickets instead of "Deployment" as we can already try
the functionality.

All development-related child blueprints for [1] were properly updated and
moved to "Implemented" state.

[1] https://blueprints.launchpad.net/fuel/+spec/dynamically-build-bootstrap

Thanks,
Dmitry.

On Fri, Dec 11, 2015 at 9:10 AM, Mike Scherbakov 
wrote:

> Hi all,
> I've moved the following blueprints:
> https://etherpad.openstack.org/p/fuel-moved-bps-from-8.0
>
> I called for blueprints status update at [1], [2], [3], [4], and suggested
> to move those which are not "Implemented". Now I finally did, except
> test/doc related (which can be done after FF).
>
> I think I moved a few which already implemented, as far as I'm aware of.
> For instance:
> https://blueprints.launchpad.net/fuel/+spec/master-on-centos7
> https://blueprints.launchpad.net/fuel/+spec/dynamically-build-bootstrap
> https://blueprints.launchpad.net/fuel/+spec/package-for-js-modules
> https://blueprints.launchpad.net/fuel/+spec/component-registry
>
> If those are in fact done, please move them back, and set proper status.
> There is uncertainty to what to do with those parent blueprints, like
> ubuntu bootstrap one, which have incomplete test- and docs- related. My
> suggestion would be to set status "Deployment" and move them back to 8.0,
> if all coding is done. Once dependent test/docs are done, parent blueprint
> should be updated and become "Implemented".
>
> Thank you,
>
> [1]
> http://lists.openstack.org/pipermail/openstack-dev/2015-December/081047.html
> [2] https://etherpad.openstack.org/p/fuel-8.0-FF-meeting, line 428
> [3]
> http://lists.openstack.org/pipermail/openstack-dev/2015-December/081131.html
> [4]
> http://eavesdrop.openstack.org/meetings/fuel/2015/fuel.2015-12-10-16.00.log.html,
> 16:32
>
> --
> Mike Scherbakov
> #mihgen
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Moved blueprints out of 8.0

2015-12-11 Thread Sergii Golovatiuk 
Hi Dmitry,

I would like not to overcomplicate blueprints. If additional work is
required there should be additional dependent blueprint. This will help us
to deliver all blueprints on time while other teams are working on own
blueprints (e.g. Documentation) with own release cadence.

[1] https://wiki.openstack.org/wiki/Blueprints



--
Best regards,
Sergii Golovatiuk,
Skype #golserge
IRC #holser

On Fri, Dec 11, 2015 at 2:35 PM, Dmitry Klenov  wrote:

> Hi Mike,
>
> Yes, I agree that we cannot move blueprints to "Implemented" unless all
> dependencies are complete (incl tests and doc). Probably we can use "Beta
> available" for such tickets instead of "Deployment" as we can already try
> the functionality.
>
> All development-related child blueprints for [1] were properly updated and
> moved to "Implemented" state.
>
> [1] https://blueprints.launchpad.net/fuel
> /+spec/dynamically-build-bootstrap
>
> Thanks,
> Dmitry.
>
> On Fri, Dec 11, 2015 at 9:10 AM, Mike Scherbakov  > wrote:
>
>> Hi all,
>> I've moved the following blueprints:
>> https://etherpad.openstack.org/p/fuel-moved-bps-from-8.0
>>
>> I called for blueprints status update at [1], [2], [3], [4], and
>> suggested to move those which are not "Implemented". Now I finally did,
>> except test/doc related (which can be done after FF).
>>
>> I think I moved a few which already implemented, as far as I'm aware of.
>> For instance:
>> https://blueprints.launchpad.net/fuel/+spec/master-on-centos7
>> https://blueprints.launchpad.net/fuel/+spec/dynamically-build-bootstrap
>> https://blueprints.launchpad.net/fuel/+spec/package-for-js-modules
>> https://blueprints.launchpad.net/fuel/+spec/component-registry
>>
>> If those are in fact done, please move them back, and set proper status.
>> There is uncertainty to what to do with those parent blueprints, like
>> ubuntu bootstrap one, which have incomplete test- and docs- related. My
>> suggestion would be to set status "Deployment" and move them back to 8.0,
>> if all coding is done. Once dependent test/docs are done, parent blueprint
>> should be updated and become "Implemented".
>>
>> Thank you,
>>
>> [1]
>> http://lists.openstack.org/pipermail/openstack-dev/2015-December/081047.html
>> [2] https://etherpad.openstack.org/p/fuel-8.0-FF-meeting, line 428
>> [3]
>> http://lists.openstack.org/pipermail/openstack-dev/2015-December/081131.html
>> [4]
>> http://eavesdrop.openstack.org/meetings/fuel/2015/fuel.2015-12-10-16.00.log.html,
>> 16:32
>>
>> --
>> Mike Scherbakov
>> #mihgen
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel] Moved blueprints out of 8.0

2015-12-10 Thread Mike Scherbakov 
Hi all,
I've moved the following blueprints:
https://etherpad.openstack.org/p/fuel-moved-bps-from-8.0

I called for blueprints status update at [1], [2], [3], [4], and suggested
to move those which are not "Implemented". Now I finally did, except
test/doc related (which can be done after FF).

I think I moved a few which already implemented, as far as I'm aware of.
For instance:
https://blueprints.launchpad.net/fuel/+spec/master-on-centos7
https://blueprints.launchpad.net/fuel/+spec/dynamically-build-bootstrap
https://blueprints.launchpad.net/fuel/+spec/package-for-js-modules
https://blueprints.launchpad.net/fuel/+spec/component-registry

If those are in fact done, please move them back, and set proper status.
There is uncertainty to what to do with those parent blueprints, like
ubuntu bootstrap one, which have incomplete test- and docs- related. My
suggestion would be to set status "Deployment" and move them back to 8.0,
if all coding is done. Once dependent test/docs are done, parent blueprint
should be updated and become "Implemented".

Thank you,

[1]
http://lists.openstack.org/pipermail/openstack-dev/2015-December/081047.html
[2] https://etherpad.openstack.org/p/fuel-8.0-FF-meeting, line 428
[3]
http://lists.openstack.org/pipermail/openstack-dev/2015-December/081131.html
[4]
http://eavesdrop.openstack.org/meetings/fuel/2015/fuel.2015-12-10-16.00.log.html,
16:32

-- 
Mike Scherbakov
#mihgen
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev