Re: [openstack-dev] [all][ptl][release] final liberty cycle client library releases needed

[Renat Akhmerov]

> On 19 Sep 2015, at 16:04, Doug Hellmann  wrote:
> 
> Excerpts from Renat Akhmerov's message of 2015-09-19 00:35:49 +0300:
>> Doug,
>> 
>> python-mistralclient-1.1.0 (also on pypi) is the final release for Liberty. 
>> Here’s the patch updating global-requirements.txt: 
>> https://review.openstack.org/#/c/225330/ 
>>  
>> > > (upper-constraints.txt should be 
>> soon updated automatically, in my understanding)
> 
> Because we're in requirements freeze, we're trying not to update any of
> the global-requirements.txt entries unless absolutely necessary. At this
> point, no projects can be depending on the previously unreleased
> features in 1.1.0, so as long as python-mistralclient doesn't have a cap
> on the major version allowed the requirements list, it should only be
> necessary to update the constraints.
> 
> Please update the constraints file by hand, only changing
> python-mistralclient. That will allow us to land the update without
> changing any other libraries in the test infrastructure (the automated
> update submits all of the changes together, and we have several
> outstanding right now).

Ok, understood.

https://review.openstack.org/#/c/225491/ 

>> So far I have been doing release management for Mistral myself (~2 years), 
>> and the last year I’ve been trying to be aligned with OpenStack schedule. In 
>> may 2015 Mistral was accepted into Big Tent so does that mean I’m not longer 
>> responsible for doing that? Or I can still do it on my own? Even with final 
>> Mistral client for Liberty I’ve done it just myself (didn’t create a stable 
>> branch though yet), maybe I shouldn’t have. Clarifications would be helpful.
> 
> It means you can now ask the release management team to take over for
> the library, but that is not an automatic change.
>> Does this all apply to all Big Tent projects?
> 
> Yes, and to all horizontal teams. Every project team is expected
> to provide liaisons to all horizontal teams now. The degree to which
> a horizontal team does the work for you is up to each pair of teams
> to negotiate.

I’d prefer to take care about Liberty releases myself. We don’t have much time 
till the end of Liberty and we may not establish all required connections with 
horizontal teams. Is that ok?

Renat Akhmerov
@ Mirantis Inc.

__
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] [all][ptl][release] final liberty cycle client library releases needed

[Doug Hellmann]

Excerpts from Renat Akhmerov's message of 2015-09-20 19:06:20 +0300:
> 
> > On 19 Sep 2015, at 16:04, Doug Hellmann  wrote:
> > 
> > Excerpts from Renat Akhmerov's message of 2015-09-19 00:35:49 +0300:
> >> Doug,
> >> 
> >> python-mistralclient-1.1.0 (also on pypi) is the final release for 
> >> Liberty. Here’s the patch updating global-requirements.txt: 
> >> https://review.openstack.org/#/c/225330/ 
> >>  
> >>  >> > (upper-constraints.txt should 
> >> be soon updated automatically, in my understanding)
> > 
> > Because we're in requirements freeze, we're trying not to update any of
> > the global-requirements.txt entries unless absolutely necessary. At this
> > point, no projects can be depending on the previously unreleased
> > features in 1.1.0, so as long as python-mistralclient doesn't have a cap
> > on the major version allowed the requirements list, it should only be
> > necessary to update the constraints.
> > 
> > Please update the constraints file by hand, only changing
> > python-mistralclient. That will allow us to land the update without
> > changing any other libraries in the test infrastructure (the automated
> > update submits all of the changes together, and we have several
> > outstanding right now).
> 
> Ok, understood.
> 
> https://review.openstack.org/#/c/225491/ 
> 

+2

> >> So far I have been doing release management for Mistral myself (~2 years), 
> >> and the last year I’ve been trying to be aligned with OpenStack schedule. 
> >> In may 2015 Mistral was accepted into Big Tent so does that mean I’m not 
> >> longer responsible for doing that? Or I can still do it on my own? Even 
> >> with final Mistral client for Liberty I’ve done it just myself (didn’t 
> >> create a stable branch though yet), maybe I shouldn’t have. Clarifications 
> >> would be helpful.
> > 
> > It means you can now ask the release management team to take over for
> > the library, but that is not an automatic change.
> >> Does this all apply to all Big Tent projects?
> > 
> > Yes, and to all horizontal teams. Every project team is expected
> > to provide liaisons to all horizontal teams now. The degree to which
> > a horizontal team does the work for you is up to each pair of teams
> > to negotiate.
> 
> I’d prefer to take care about Liberty releases myself. We don’t have much 
> time till the end of Liberty and we may not establish all required 
> connections with horizontal teams. Is that ok?

That makes a lot of sense.

Doug

> 
> Renat Akhmerov
> @ Mirantis Inc.

__
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] [all][ptl][release] final liberty cycle client library releases needed

[Doug Hellmann]

Excerpts from Renat Akhmerov's message of 2015-09-19 00:35:49 +0300:
> Doug,
> 
> python-mistralclient-1.1.0 (also on pypi) is the final release for Liberty. 
> Here’s the patch updating global-requirements.txt: 
> https://review.openstack.org/#/c/225330/ 
> <https://review.openstack.org/#/c/225330/> (upper-constraints.txt should be 
> soon updated automatically, in my understanding)

Because we're in requirements freeze, we're trying not to update any of
the global-requirements.txt entries unless absolutely necessary. At this
point, no projects can be depending on the previously unreleased
features in 1.1.0, so as long as python-mistralclient doesn't have a cap
on the major version allowed the requirements list, it should only be
necessary to update the constraints.

Please update the constraints file by hand, only changing
python-mistralclient. That will allow us to land the update without
changing any other libraries in the test infrastructure (the automated
update submits all of the changes together, and we have several
outstanding right now).

> 
> I really apologize because I should have probably followed ML better and 
> attended corresponding meetings in order to know all of this release 
> management stuff.  But I still have a number questions on release management 
> like:

Yes, clearly we're going to have to do a better job of communicating
with project teams next cycle. I welcome suggestions for that.

> So far I have been doing release management for Mistral myself (~2 years), 
> and the last year I’ve been trying to be aligned with OpenStack schedule. In 
> may 2015 Mistral was accepted into Big Tent so does that mean I’m not longer 
> responsible for doing that? Or I can still do it on my own? Even with final 
> Mistral client for Liberty I’ve done it just myself (didn’t create a stable 
> branch though yet), maybe I shouldn’t have. Clarifications would be helpful.

It means you can now ask the release management team to take over for
the library, but that is not an automatic change.

> Same question about stable branches.

Same, for the stable maintenance team.

> Does this all apply to all Big Tent projects?

Yes, and to all horizontal teams. Every project team is expected
to provide liaisons to all horizontal teams now. The degree to which
a horizontal team does the work for you is up to each pair of teams
to negotiate.

> What exactly is upper-constraints.txt for? I’m still not sure why 
> global-requirements.txt is not enough.

global-requirements.txt tells what versions of libraries we are
compatible with. upper-constraints.txt tells the most recent version of
libraries actually being used in tests running in our CI system.
Currently that only applies to integration tests, but the work to apply
it to unit tests is coming along.

> What’s the best source of info about release management? Is it complete?

Documentation is one of the weak points right now, and we'll be
addressing that with clearer documentation for milestone dates and
expectations and probably some centralization so there is only one
place folks need to go. Right now we have a section in the project
team guide [1], descriptions of the tools in the release-tools
REAMDE [2], and for managed teams we have instructions in the
releases repository [3].  Deadlines are listed in the wiki [4].

[1] http://docs.openstack.org/project-team-guide/release-management.html
[2] http://git.openstack.org/cgit/openstack-infra/release-tools/tree/README.rst
[3] http://git.openstack.org/cgit/openstack/releases/tree/README.rst
[4] https://wiki.openstack.org/wiki/Liberty_Release_Schedule

> 
> Sorry for asking this probably basic stuff.
> 
> Let me know if some of what I’ve done is wrong. It’s a late night here but 
> I’ll check ML the first thing in the morning just in case.
> 
> Thanks
> 
> Renat Akhmerov
> @ Mirantis Inc.
> 
> > On 15 Sep 2015, at 22:24, Nikhil Komawar <nik.koma...@gmail.com> wrote:
> > 
> > Hi Doug,
> > 
> > And it would be good to lock in on glance_store (if it applies to this
> > email) 0.9.1 too. (that's on pypi)
> > 
> > On 9/14/15 9:26 AM, Kuvaja, Erno wrote:
> >> Hi Doug,
> >> 
> >> Please find python-glanceclient 1.0.1 release request 
> >> https://review.openstack.org/#/c/222716/
> >> 
> >> - Erno
> >> 
> >>> -----Original Message-
> >>> From: Doug Hellmann [mailto:d...@doughellmann.com]
> >>> Sent: Monday, September 14, 2015 1:46 PM
> >>> To: openstack-dev
> >>> Subject: [openstack-dev] [all][ptl][release] final liberty cycle client 
> >>> library
> >>> releases needed
> >>> 
> >>> PTLs and release liaisons,
> >>> 
> >>> In order to keep the rest of ou

Re: [openstack-dev] [all][ptl][release] final liberty cycle client library releases needed

[Renat Akhmerov]

Doug,

python-mistralclient-1.1.0 (also on pypi) is the final release for Liberty. 
Here’s the patch updating global-requirements.txt: 
https://review.openstack.org/#/c/225330/ 
<https://review.openstack.org/#/c/225330/> (upper-constraints.txt should be 
soon updated automatically, in my understanding)

I really apologize because I should have probably followed ML better and 
attended corresponding meetings in order to know all of this release management 
stuff.  But I still have a number questions on release management like:
So far I have been doing release management for Mistral myself (~2 years), and 
the last year I’ve been trying to be aligned with OpenStack schedule. In may 
2015 Mistral was accepted into Big Tent so does that mean I’m not longer 
responsible for doing that? Or I can still do it on my own? Even with final 
Mistral client for Liberty I’ve done it just myself (didn’t create a stable 
branch though yet), maybe I shouldn’t have. Clarifications would be helpful.
Same question about stable branches.
Does this all apply to all Big Tent projects?
What exactly is upper-constraints.txt for? I’m still not sure why 
global-requirements.txt is not enough.
What’s the best source of info about release management? Is it complete?

Sorry for asking this probably basic stuff.

Let me know if some of what I’ve done is wrong. It’s a late night here but I’ll 
check ML the first thing in the morning just in case.

Thanks

Renat Akhmerov
@ Mirantis Inc.



> On 15 Sep 2015, at 22:24, Nikhil Komawar <nik.koma...@gmail.com> wrote:
> 
> Hi Doug,
> 
> And it would be good to lock in on glance_store (if it applies to this
> email) 0.9.1 too. (that's on pypi)
> 
> On 9/14/15 9:26 AM, Kuvaja, Erno wrote:
>> Hi Doug,
>> 
>> Please find python-glanceclient 1.0.1 release request 
>> https://review.openstack.org/#/c/222716/
>> 
>> - Erno
>> 
>>> -Original Message-
>>> From: Doug Hellmann [mailto:d...@doughellmann.com]
>>> Sent: Monday, September 14, 2015 1:46 PM
>>> To: openstack-dev
>>> Subject: [openstack-dev] [all][ptl][release] final liberty cycle client 
>>> library
>>> releases needed
>>> 
>>> PTLs and release liaisons,
>>> 
>>> In order to keep the rest of our schedule for the end-of-cycle release 
>>> tasks,
>>> we need to have final releases for all client libraries in the next day or 
>>> two.
>>> 
>>> If you have not already submitted your final release request for this cycle,
>>> please do that as soon as possible.
>>> 
>>> If you *have* already submitted your final release request for this cycle,
>>> please reply to this email and let me know that you have so I can create 
>>> your
>>> stable/liberty branch.
>>> 
>>> Thanks!
>>> Doug
>>> 
>>> __
>>> 
>>> 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
> 
> -- 
> 
> Thanks,
> Nikhil
> 
> 
> __
> 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] [all][ptl][release] final liberty cycle client library releases needed

[Doug Hellmann]

Excerpts from Sergey Lukjanov's message of 2015-09-15 18:12:23 +0300:
> We're in a good shape with sahara client. 0.11.0 is the final minor release
> for it. Constraints are up to date.

Thanks, Sergey! We appreciate you and the rest of the Sahara team staying
on track with the work needed for the release schedule.

Doug

__
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] [all][ptl][release] final liberty cycle client library releases needed

[Doug Hellmann]

Excerpts from Renat Akhmerov's message of 2015-09-15 18:11:58 +0300:
> 
> > On 15 Sep 2015, at 17:45, Doug Hellmann  wrote:
> > 
> > We would like for the schedule to be the same for everyone. We need the
> > final versions for all libraries this week, so we can update
> > requirements constraints by early next week before the RC1.
> 
> 
> “for everyone” meaning “for all Big Tent projects”? I’m trying to figure out 
> if that affects projects like Mistral that are not massively interdependent 
> with other projects.

If you plan to have a Liberty release, we would like for you to follow
the same release schedule as everyone else.

Doug

__
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] [all][ptl][release] final liberty cycle client library releases needed

[Renat Akhmerov]

> On 15 Sep 2015, at 17:45, Doug Hellmann  wrote:
> 
> We would like for the schedule to be the same for everyone. We need the
> final versions for all libraries this week, so we can update
> requirements constraints by early next week before the RC1.


“for everyone” meaning “for all Big Tent projects”? I’m trying to figure out if 
that affects projects like Mistral that are not massively interdependent with 
other projects.

Thnx

Renat Akhmerov
@ Mirantis Inc.

__
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] [all][ptl][release] final liberty cycle client library releases needed

[Sergey Lukjanov]

We're in a good shape with sahara client. 0.11.0 is the final minor release
for it. Constraints are up to date.

On Tue, Sep 15, 2015 at 5:45 PM, Doug Hellmann 
wrote:

> Excerpts from Dmitry Tantsur's message of 2015-09-15 16:16:00 +0200:
> > On 09/14/2015 04:18 PM, Doug Hellmann wrote:
> > > Excerpts from Doug Hellmann's message of 2015-09-14 08:46:02 -0400:
> > >> PTLs and release liaisons,
> > >>
> > >> In order to keep the rest of our schedule for the end-of-cycle release
> > >> tasks, we need to have final releases for all client libraries in the
> > >> next day or two.
> > >>
> > >> If you have not already submitted your final release request for this
> > >> cycle, please do that as soon as possible.
> > >>
> > >> If you *have* already submitted your final release request for this
> > >> cycle, please reply to this email and let me know that you have so I
> can
> > >> create your stable/liberty branch.
> > >>
> > >> Thanks!
> > >> Doug
> > >
> > > I forgot to mention that we also need the constraints file in
> > > global-requirements updated for all of the releases, so we're actually
> > > testing with them in the gate. Please take a minute to check the
> version
> > > specified in openstack/requirements/upper-constraints.txt for your
> > > libraries and submit a patch to update it to the latest release if
> > > necessary. I'll do a review later in the week, too, but it's easier to
> > > identify the causes of test failures if we have one patch at a time.
> >
> > Hi Doug!
> >
> > When is the last and final deadline for doing all this for
> > not-so-important and non-release:managed projects like ironic-inspector?
> > We still lack some Liberty features covered in
> > python-ironic-inspector-client. Do we have time until end of week to
> > finish them?
>
> We would like for the schedule to be the same for everyone. We need the
> final versions for all libraries this week, so we can update
> requirements constraints by early next week before the RC1.
>
> https://wiki.openstack.org/wiki/Liberty_Release_Schedule
>
> Doug
>
> >
> > Sorry if you hear this question too often :)
> >
> > Thanks!
> >
> > >
> > > Doug
> > >
> > >
> __
> > > 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
>



-- 
Sincerely yours,
Sergey Lukjanov
Sahara Technical Lead
(OpenStack Data Processing)
Principal Software Engineer
Mirantis Inc.
__
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] [all][ptl][release] final liberty cycle client library releases needed

[Nikhil Komawar]

Hi Doug,

And it would be good to lock in on glance_store (if it applies to this
email) 0.9.1 too. (that's on pypi)

On 9/14/15 9:26 AM, Kuvaja, Erno wrote:
> Hi Doug,
>
> Please find python-glanceclient 1.0.1 release request 
> https://review.openstack.org/#/c/222716/
>
> - Erno
>
>> -Original Message-
>> From: Doug Hellmann [mailto:d...@doughellmann.com]
>> Sent: Monday, September 14, 2015 1:46 PM
>> To: openstack-dev
>> Subject: [openstack-dev] [all][ptl][release] final liberty cycle client 
>> library
>> releases needed
>>
>> PTLs and release liaisons,
>>
>> In order to keep the rest of our schedule for the end-of-cycle release tasks,
>> we need to have final releases for all client libraries in the next day or 
>> two.
>>
>> If you have not already submitted your final release request for this cycle,
>> please do that as soon as possible.
>>
>> If you *have* already submitted your final release request for this cycle,
>> please reply to this email and let me know that you have so I can create your
>> stable/liberty branch.
>>
>> Thanks!
>> Doug
>>
>> __
>> 
>> 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

-- 

Thanks,
Nikhil


__
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] [all][ptl][release] final liberty cycle client library releases needed

[Dmitry Tantsur]

On 09/14/2015 04:18 PM, Doug Hellmann wrote:

Excerpts from Doug Hellmann's message of 2015-09-14 08:46:02 -0400:

PTLs and release liaisons,

In order to keep the rest of our schedule for the end-of-cycle release
tasks, we need to have final releases for all client libraries in the
next day or two.

If you have not already submitted your final release request for this
cycle, please do that as soon as possible.

If you *have* already submitted your final release request for this
cycle, please reply to this email and let me know that you have so I can
create your stable/liberty branch.

Thanks!
Doug


I forgot to mention that we also need the constraints file in
global-requirements updated for all of the releases, so we're actually
testing with them in the gate. Please take a minute to check the version
specified in openstack/requirements/upper-constraints.txt for your
libraries and submit a patch to update it to the latest release if
necessary. I'll do a review later in the week, too, but it's easier to
identify the causes of test failures if we have one patch at a time.


Hi Doug!

When is the last and final deadline for doing all this for 
not-so-important and non-release:managed projects like ironic-inspector? 
We still lack some Liberty features covered in 
python-ironic-inspector-client. Do we have time until end of week to 
finish them?


Sorry if you hear this question too often :)

Thanks!



Doug

__
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] [all][ptl][release] final liberty cycle client library releases needed

[Doug Hellmann]

Excerpts from Dmitry Tantsur's message of 2015-09-15 16:16:00 +0200:
> On 09/14/2015 04:18 PM, Doug Hellmann wrote:
> > Excerpts from Doug Hellmann's message of 2015-09-14 08:46:02 -0400:
> >> PTLs and release liaisons,
> >>
> >> In order to keep the rest of our schedule for the end-of-cycle release
> >> tasks, we need to have final releases for all client libraries in the
> >> next day or two.
> >>
> >> If you have not already submitted your final release request for this
> >> cycle, please do that as soon as possible.
> >>
> >> If you *have* already submitted your final release request for this
> >> cycle, please reply to this email and let me know that you have so I can
> >> create your stable/liberty branch.
> >>
> >> Thanks!
> >> Doug
> >
> > I forgot to mention that we also need the constraints file in
> > global-requirements updated for all of the releases, so we're actually
> > testing with them in the gate. Please take a minute to check the version
> > specified in openstack/requirements/upper-constraints.txt for your
> > libraries and submit a patch to update it to the latest release if
> > necessary. I'll do a review later in the week, too, but it's easier to
> > identify the causes of test failures if we have one patch at a time.
> 
> Hi Doug!
> 
> When is the last and final deadline for doing all this for 
> not-so-important and non-release:managed projects like ironic-inspector? 
> We still lack some Liberty features covered in 
> python-ironic-inspector-client. Do we have time until end of week to 
> finish them?

We would like for the schedule to be the same for everyone. We need the
final versions for all libraries this week, so we can update
requirements constraints by early next week before the RC1.

https://wiki.openstack.org/wiki/Liberty_Release_Schedule

Doug

> 
> Sorry if you hear this question too often :)
> 
> Thanks!
> 
> >
> > Doug
> >
> > __
> > 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] [all][ptl][release] final liberty cycle client library releases needed

[Doug Hellmann]

PTLs and release liaisons,

In order to keep the rest of our schedule for the end-of-cycle release
tasks, we need to have final releases for all client libraries in the
next day or two.

If you have not already submitted your final release request for this
cycle, please do that as soon as possible.

If you *have* already submitted your final release request for this
cycle, please reply to this email and let me know that you have so I can
create your stable/liberty branch.

Thanks!
Doug

__
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] [all][ptl][release] final liberty cycle client library releases needed

[Davanum Srinivas]

Doug,

All oslo libraries are ready for stable/liberty branch.

Thanks,
-- Dims

On Mon, Sep 14, 2015 at 8:46 AM, Doug Hellmann 
wrote:

> PTLs and release liaisons,
>
> In order to keep the rest of our schedule for the end-of-cycle release
> tasks, we need to have final releases for all client libraries in the
> next day or two.
>
> If you have not already submitted your final release request for this
> cycle, please do that as soon as possible.
>
> If you *have* already submitted your final release request for this
> cycle, please reply to this email and let me know that you have so I can
> create your stable/liberty branch.
>
> Thanks!
> Doug
>
> __
> 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
>



-- 
Davanum Srinivas :: https://twitter.com/dims
__
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] [all][ptl][release] final liberty cycle client library releases needed

[Kuvaja, Erno]

Hi Doug,

Please find python-glanceclient 1.0.1 release request 
https://review.openstack.org/#/c/222716/

- Erno

> -Original Message-
> From: Doug Hellmann [mailto:d...@doughellmann.com]
> Sent: Monday, September 14, 2015 1:46 PM
> To: openstack-dev
> Subject: [openstack-dev] [all][ptl][release] final liberty cycle client 
> library
> releases needed
> 
> PTLs and release liaisons,
> 
> In order to keep the rest of our schedule for the end-of-cycle release tasks,
> we need to have final releases for all client libraries in the next day or 
> two.
> 
> If you have not already submitted your final release request for this cycle,
> please do that as soon as possible.
> 
> If you *have* already submitted your final release request for this cycle,
> please reply to this email and let me know that you have so I can create your
> stable/liberty branch.
> 
> Thanks!
> Doug
> 
> __
> 
> 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] [all][ptl][release] final liberty cycle client library releases needed

[Doug Hellmann]

Excerpts from Doug Hellmann's message of 2015-09-14 08:46:02 -0400:
> PTLs and release liaisons,
> 
> In order to keep the rest of our schedule for the end-of-cycle release
> tasks, we need to have final releases for all client libraries in the
> next day or two.
> 
> If you have not already submitted your final release request for this
> cycle, please do that as soon as possible.
> 
> If you *have* already submitted your final release request for this
> cycle, please reply to this email and let me know that you have so I can
> create your stable/liberty branch.
> 
> Thanks!
> Doug

I forgot to mention that we also need the constraints file in
global-requirements updated for all of the releases, so we're actually
testing with them in the gate. Please take a minute to check the version
specified in openstack/requirements/upper-constraints.txt for your
libraries and submit a patch to update it to the latest release if
necessary. I'll do a review later in the week, too, but it's easier to
identify the causes of test failures if we have one patch at a time.

Doug

__
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