Re: [openstack-dev] [ironic] RFC: stop using launchpad milestones and blueprints

FYI, this work was completed. Docs are here: http://docs.openstack.org/developer/ironic/dev/code-contribution-guide.html#adding-new-features // jim On Wed, Dec 09, 2015 at 01:58:34PM -0800, Jim Rollenhagen wrote: > On Fri, Dec 04, 2015 at 05:38:43PM +0100, Dmitry Tantsur wrote: > > Hi! > > > >

Re: [openstack-dev] [ironic] RFC: stop using launchpad milestones and blueprints

On 12/09/2015 10:58 PM, Jim Rollenhagen wrote: On Fri, Dec 04, 2015 at 05:38:43PM +0100, Dmitry Tantsur wrote: Hi! As you all probably know, we've switched to reno for managing release notes. What it also means is that the release team has stopped managing milestones for us. We have to

Re: [openstack-dev] [ironic] RFC: stop using launchpad milestones and blueprints

Hi all, fix for tests in #2 is on review, https://review.openstack.org/#/c/255811/ cheers, On Thu, Dec 10, 2015 at 1:15 PM Dmitry Tantsur wrote: > On 12/09/2015 10:58 PM, Jim Rollenhagen wrote: > > On Fri, Dec 04, 2015 at 05:38:43PM +0100, Dmitry Tantsur wrote: > >> Hi! >

Re: [openstack-dev] [ironic] RFC: stop using launchpad milestones and blueprints

On Fri, Dec 04, 2015 at 05:38:43PM +0100, Dmitry Tantsur wrote: > Hi! > > As you all probably know, we've switched to reno for managing release notes. > What it also means is that the release team has stopped managing milestones > for us. We have to manually open/close milestones in launchpad, if

Re: [openstack-dev] [ironic] RFC: stop using launchpad milestones and blueprints

On 12/08/2015 08:12 AM, Pavlo Shchelokovskyy wrote: Hi all, I have a question regarding #1 (Stop using LP for blueprints): what should we now use instead of "specifies" and "implements" Gerrit tags in commit messages? Simple Depends-On: should suffice but is not visually specific enough, and

Re: [openstack-dev] [ironic] RFC: stop using launchpad milestones and blueprints

>>> I wonder how to avoid giving impression that development has stopped on >>> 4.2.0. E.g. Launchpad would show 4.2.0 as the last released tarball, as >>> we no longer push tarballs to launchpad. .0 is clear indication that's GA tarball, but to make it clear you can update Launchpad series

Re: [openstack-dev] [ironic] RFC: stop using launchpad milestones and blueprints

Alan Pevec wrote: > Count me confused, when I saw Ironic 4.2.2 announcement and then 4.2.1 > as latest in Launchpad. > I propose to remove https://launchpad.net/ironic/+milestone/4.2.1 - it > has no release notes and only one minor bug, so that's not much > information loss and cuts this confusing

Re: [openstack-dev] [ironic] RFC: stop using launchpad milestones and blueprints

On 12/08/2015 11:32 AM, Pavlo Shchelokovskyy wrote: Hi Dmitry, not true, the gate-ironic-specs-python27 requires that LP blueprint is provided in a spec [0]. If we are to get away from LP blueprints and at least not register new ones, this must be fixed. I'll test if the job accepts a link to

Re: [openstack-dev] [ironic] RFC: stop using launchpad milestones and blueprints

Hi Dmitry, not true, the gate-ironic-specs-python27 requires that LP blueprint is provided in a spec [0]. If we are to get away from LP blueprints and at least not register new ones, this must be fixed. I'll test if the job accepts a link to LP RFE bug instead of LP blueprint though. [0]

Re: [openstack-dev] [ironic] RFC: stop using launchpad milestones and blueprints

Hi all, I have a question regarding #1 (Stop using LP for blueprints): what should we now use instead of "specifies" and "implements" Gerrit tags in commit messages? Simple Depends-On: should suffice but is not visually specific enough, and only replaces "implements" tag. Also as a side note,

Re: [openstack-dev] [ironic] RFC: stop using launchpad milestones and blueprints

Excerpts from Dmitry Tantsur's message of 2015-12-07 13:18:22 +0100: > On 12/07/2015 10:48 AM, Thierry Carrez wrote: > > Dmitry Tantsur wrote: > >> > >> 2015-12-04 18:26 GMT+01:00 Doug Hellmann >> >: > >> > > >> > >> Please don't delete

Re: [openstack-dev] [ironic] RFC: stop using launchpad milestones and blueprints

On 12/07/2015 02:42 PM, Doug Hellmann wrote: Excerpts from Dmitry Tantsur's message of 2015-12-07 13:18:22 +0100: On 12/07/2015 10:48 AM, Thierry Carrez wrote: Dmitry Tantsur wrote: 2015-12-04 18:26 GMT+01:00 Doug Hellmann >:

Re: [openstack-dev] [ironic] RFC: stop using launchpad milestones and blueprints

Dmitry Tantsur wrote: > > 2015-12-04 18:26 GMT+01:00 Doug Hellmann >: > > Excerpts from Dmitry Tantsur's message of 2015-12-04 17:38:43 +0100: > > Hi! > > > > As you all probably know, we've switched to reno for managing

Re: [openstack-dev] [ironic] RFC: stop using launchpad milestones and blueprints

On 12/07/2015 10:48 AM, Thierry Carrez wrote: Dmitry Tantsur wrote: 2015-12-04 18:26 GMT+01:00 Doug Hellmann >: Please don't delete anything older than Mitaka. Do you have any hints how to not confuse users in this case? I

Re: [openstack-dev] [ironic] RFC: stop using launchpad milestones and blueprints

2015-12-04 18:26 GMT+01:00 Doug Hellmann : > Excerpts from Dmitry Tantsur's message of 2015-12-04 17:38:43 +0100: > > Hi! > > > > As you all probably know, we've switched to reno for managing release > > notes. What it also means is that the release team has stopped

Re: [openstack-dev] [ironic] RFC: stop using launchpad milestones and blueprints

Excerpts from Dmitry Tantsur's message of 2015-12-04 17:38:43 +0100: > Hi! > > As you all probably know, we've switched to reno for managing release > notes. What it also means is that the release team has stopped managing > milestones for us. We have to manually open/close milestones in >

[openstack-dev] [ironic] RFC: stop using launchpad milestones and blueprints

Hi! As you all probably know, we've switched to reno for managing release notes. What it also means is that the release team has stopped managing milestones for us. We have to manually open/close milestones in launchpad, if we feel like. I'm a bit tired of doing it for inspector, so I'd