Re: [openstack-dev] [ptl][release] flushing unreleased client library changes

2015-09-08 Thread Doug Hellmann 
Excerpts from Ben Swartzlander's message of 2015-09-04 16:54:13 -0400:
> 
> On 09/04/2015 03:21 PM, Doug Hellmann wrote:
> > Excerpts from Ben Swartzlander's message of 2015-09-04 14:51:10 -0400:
> >> On 09/04/2015 12:39 PM, Doug Hellmann wrote:
> >>> PTLs,
> >>>
> >>> We have quite a few unreleased client changes pending, and it would
> >>> be good to go ahead and publish them so they can be tested as part
> >>> of the release candidate process. I have the full list of changes for
> >>> each project below, so please find yours and review them and then
> >>> propose a release request to the openstack/releases repository.
> >> Manila had multiple gate-breaking bugs this week and I've extended our
> >> feature freeze to next Tuesday to compensate. As a result our L-3
> >> milestone release is not really representative of Liberty and we'd
> >> rather not do a client release until we reach RC1.
> > Keep in mind that the unreleased changes are not being used to test
> > anything at all in the gate, so there's an integration "penalty" for
> > delaying releases. You can have as many releases as you want, and we can
> > create the stable branch from the last useful release any time after it
> > is created. So, I still recommend releasing early and often unless you
> > anticipate making API or CLI breaking changes between now and RC1.
> 
> There is currently an API breaking change that needs to be fixed. It 
> will be fixed before the RC so that Kilo<->Liberty upgrades go smoothly 
> but the L-3 milestone is broken regarding forward and backward 
> compatibility.
> 
> https://bugs.launchpad.net/manila/+bug/1488624
> 
> I would actually want to release a milestone between L-3 and RC1 after 
> we get to the real Manila FF date but since that's not in line with the 
> official release process I'm okay waiting for RC1. Since there is no 
> official process for client releases (that I know about) I'd rather just 
> wait to do the client until RC1. We'll plan for an early RC1 by 
> aggressively driving the bugs to zero instead of putting time into 
> testing the L-3 milestone.

If master is broken right now, I agree it's not a good idea to
release.  That said, you still don't want to wait any later than
you have to. Gate jobs only install libraries from packages, so no
projects that are co-gating with manila, including manila itself,
are using the source version of the client library. That means when
there's a release, the new package introduces all of the new changes
into the integration tests at the same time.

We want to release clients as often as possible to keep the number
of changes small. This is why we release Oslo libraries weekly --
we still break things once in a while, but when we do we have a
short list of changes to look at to figure out why.

I'll be proposing that we do a weekly client change review for all
managed clients starting next cycle, and release when there are changes
that warrant (probably not just for requirements changes, unless
it's necessary). I haven't worked out the details of how to do the
review without me contacting release liaisons directly, so suggestions
on that are welcome.

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] [ptl][release] flushing unreleased client library changes

2015-09-08 Thread Thierry Carrez 
Doug Hellmann wrote:
> Excerpts from Ben Swartzlander's message of 2015-09-04 16:54:13 -0400:
>> [...]
>> I would actually want to release a milestone between L-3 and RC1 after 
>> we get to the real Manila FF date but since that's not in line with the 
>> official release process I'm okay waiting for RC1. Since there is no 
>> official process for client releases (that I know about) I'd rather just 
>> wait to do the client until RC1. We'll plan for an early RC1 by 
>> aggressively driving the bugs to zero instead of putting time into 
>> testing the L-3 milestone.
> 
> If master is broken right now, I agree it's not a good idea to
> release.  That said, you still don't want to wait any later than
> you have to. Gate jobs only install libraries from packages, so no
> projects that are co-gating with manila, including manila itself,
> are using the source version of the client library. That means when
> there's a release, the new package introduces all of the new changes
> into the integration tests at the same time.

Yes, that creates unnecessary risk toward the end of the release cycle.
This is why we want to release near-final version of libraries this week
(from which we create the library release/stable branches) -- to keep
risk under control and start testing with the latest code ASAP.

> We want to release clients as often as possible to keep the number
> of changes small. This is why we release Oslo libraries weekly --
> we still break things once in a while, but when we do we have a
> short list of changes to look at to figure out why.
> 
> I'll be proposing that we do a weekly client change review for all
> managed clients starting next cycle, and release when there are changes
> that warrant (probably not just for requirements changes, unless
> it's necessary). I haven't worked out the details of how to do the
> review without me contacting release liaisons directly, so suggestions
> on that are welcome.

+1

-- 
Thierry Carrez (ttx)

__
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] [ptl][release] flushing unreleased client library changes

2015-09-04 Thread Doug Hellmann 

PTLs,

We have quite a few unreleased client changes pending, and it would
be good to go ahead and publish them so they can be tested as part
of the release candidate process. I have the full list of changes for
each project below, so please find yours and review them and then
propose a release request to the openstack/releases repository.

On a separate note, for next cycle we need to do a better job of
releasing these much much earlier (a few of these changes are at
least a month old). Remember that changes to libraries do not go
into the gate for consuming projects until that library is released.
If you have any suggestions for how to do improve our tracking for
needed releases, let me know.

Doug


[ Unreleased changes in openstack/python-barbicanclient ]

Changes in python-barbicanclient 3.3.0..97cc46a
---
4572293 2015-08-27 19:38:39 -0500 Add epilog to parser
17ed50a 2015-08-25 14:58:25 + Add Unit Tests for Store and Update Payload 
when Payload is zero
34256de 2015-08-25 09:56:24 -0500 Allow Barbican Client Secret Update 
Functionality

[ Unreleased changes in openstack/python-ceilometerclient ]

Changes in python-ceilometerclient 1.4.0..2006902
-
2006902 2015-08-26 14:09:00 + Updated from global requirements
2429dae 2015-08-25 01:32:56 + Don't try to get aodh endpoint if auth_url 
didn't provided
6498d55 2015-08-13 20:21:24 + Updated from global requirements

[ Unreleased changes in openstack/python-cinderclient ]

Changes in python-cinderclient 1.3.1..1c82825
-
1c82825 2015-09-02 17:18:28 -0700 Update path to subunit2html in post_test_hook
471aea8 2015-09-02 00:53:40 + Adds command to fetch specified backend 
capabilities
2d979dc 2015-09-01 22:35:28 +0800 Volume status management for volume migration
50758ba 2015-08-27 09:39:58 -0500 Fixed test_password_prompted
dc6e823 2015-08-26 23:04:16 -0700 Fix help message for reset-state commands
f805f5a 2015-08-25 15:15:20 +0300 Add functional tests for python-cinderclient
8cc3ee2 2015-08-19 18:05:34 +0300 Add support '--all-tenants' for cinder 
backup-list
2c3169e 2015-08-11 10:18:01 -0400 CLI: Non-disruptive backup
5e26906 2015-08-11 13:14:04 +0300 Add tests for python-cinderclient
780a129 2015-08-09 15:57:00 +0900 Replace assertEqual(None, *) with 
assertIsNone in tests
a9405b1 2015-08-08 05:36:45 -0400 CLI: Clone CG
03542ee 2015-08-04 14:21:52 -0700 Fix ClientException init when there is no 
message on py34
2ec9a22 2015-08-03 11:14:44 +0800 Fixes table when there are multiline in 
result data
04caf88 2015-07-30 18:24:57 +0300 Set default OS_VOLUME_API_VERSION to '2'
bae0bb3 2015-07-27 01:28:00 + Add commands for modifying image metadata
629e548 2015-07-24 03:34:55 + Updated from global requirements
b51e43e 2015-07-21 01:04:02 + Remove H302
b426b71 2015-07-20 13:21:02 +0800 Show backup and volume info in backup_restore
dc1186d 2015-07-16 19:45:08 -0700 Add response message when volume delete
075381d 2015-07-15 09:20:48 +0800 Add more details for replication
953f766 2015-07-14 18:51:58 +0800 New mock release(1.1.0) broke unit/function 
tests
8afc06c 2015-07-08 12:11:07 -0500 Remove unnecessary check for tenant 
information
c23586b 2015-07-08 11:42:59 +0800 Remove redundant statement and refactor
891ef3e 2015-06-25 13:27:42 + Use shared shell arguments provided by Session

[ Unreleased changes in openstack/python-congressclient ]

Changes in python-congressclient 1.1.0..0874721
---
0f699f8 2015-09-02 14:47:32 +0800 Add actions listing command
d7fa523 2015-08-26 14:09:29 + Updated from global requirements
36f2b47 2015-08-11 01:38:32 + Updated from global requirements
ee07cb3 2015-07-27 15:47:12 +0800 Fix constant name
f9858a8 2015-07-27 15:19:04 +0800 Support version list API in client
9693132 2015-06-20 22:38:10 +0900 Adding a test of datasource table show CLI
a102014 2015-05-21 04:52:12 -0300 Favor the use of importlib over Python 
internal __import__ statement
726d560 2015-05-07 23:37:04 + Updated from global requirements
b8a176b 2015-04-24 16:31:49 +0800 Replace stackforge with openstack in 
README.rst
8c31d3f 2015-03-31 15:33:53 -0700 Add api bindings for datasource 
request-request trigger

[ Unreleased changes in openstack/python-cueclient ]

Changes in python-cueclient 0.0.1..d9ac712
--
d9ac712 2015-08-26 14:09:42 + Updated from global requirements
47b81c3 2015-08-11 13:38:14 -0700 Update python-binding section for keystone v3 
support
d30c3b1 2015-08-11 01:38:34 + Updated from global requirements
14e5f05 2015-08-06 10:15:13 -0700 Adding size field cue cluster list command
0c7559b 2015-07-16 10:29:07 -0700 Rename end_points to endpoints in API
0e36051 2015-07-13 12:55:29 -0700 updating docs from stackforge->openstack
cda 2015-07-13 12:29:04 -0700 fixing oslo_serialization

Re: [openstack-dev] [ptl][release] flushing unreleased client library changes

2015-09-04 Thread Ben Swartzlander 

On 09/04/2015 12:39 PM, Doug Hellmann wrote:

PTLs,

We have quite a few unreleased client changes pending, and it would
be good to go ahead and publish them so they can be tested as part
of the release candidate process. I have the full list of changes for
each project below, so please find yours and review them and then
propose a release request to the openstack/releases repository.


Manila had multiple gate-breaking bugs this week and I've extended our 
feature freeze to next Tuesday to compensate. As a result our L-3 
milestone release is not really representative of Liberty and we'd 
rather not do a client release until we reach RC1.


-Ben Swartzlander



On a separate note, for next cycle we need to do a better job of
releasing these much much earlier (a few of these changes are at
least a month old). Remember that changes to libraries do not go
into the gate for consuming projects until that library is released.
If you have any suggestions for how to do improve our tracking for
needed releases, let me know.

Doug


[ Unreleased changes in openstack/python-barbicanclient ]

Changes in python-barbicanclient 3.3.0..97cc46a
---
4572293 2015-08-27 19:38:39 -0500 Add epilog to parser
17ed50a 2015-08-25 14:58:25 + Add Unit Tests for Store and Update Payload 
when Payload is zero
34256de 2015-08-25 09:56:24 -0500 Allow Barbican Client Secret Update 
Functionality

[ Unreleased changes in openstack/python-ceilometerclient ]

Changes in python-ceilometerclient 1.4.0..2006902
-
2006902 2015-08-26 14:09:00 + Updated from global requirements
2429dae 2015-08-25 01:32:56 + Don't try to get aodh endpoint if auth_url 
didn't provided
6498d55 2015-08-13 20:21:24 + Updated from global requirements

[ Unreleased changes in openstack/python-cinderclient ]

Changes in python-cinderclient 1.3.1..1c82825
-
1c82825 2015-09-02 17:18:28 -0700 Update path to subunit2html in post_test_hook
471aea8 2015-09-02 00:53:40 + Adds command to fetch specified backend 
capabilities
2d979dc 2015-09-01 22:35:28 +0800 Volume status management for volume migration
50758ba 2015-08-27 09:39:58 -0500 Fixed test_password_prompted
dc6e823 2015-08-26 23:04:16 -0700 Fix help message for reset-state commands
f805f5a 2015-08-25 15:15:20 +0300 Add functional tests for python-cinderclient
8cc3ee2 2015-08-19 18:05:34 +0300 Add support '--all-tenants' for cinder 
backup-list
2c3169e 2015-08-11 10:18:01 -0400 CLI: Non-disruptive backup
5e26906 2015-08-11 13:14:04 +0300 Add tests for python-cinderclient
780a129 2015-08-09 15:57:00 +0900 Replace assertEqual(None, *) with 
assertIsNone in tests
a9405b1 2015-08-08 05:36:45 -0400 CLI: Clone CG
03542ee 2015-08-04 14:21:52 -0700 Fix ClientException init when there is no 
message on py34
2ec9a22 2015-08-03 11:14:44 +0800 Fixes table when there are multiline in 
result data
04caf88 2015-07-30 18:24:57 +0300 Set default OS_VOLUME_API_VERSION to '2'
bae0bb3 2015-07-27 01:28:00 + Add commands for modifying image metadata
629e548 2015-07-24 03:34:55 + Updated from global requirements
b51e43e 2015-07-21 01:04:02 + Remove H302
b426b71 2015-07-20 13:21:02 +0800 Show backup and volume info in backup_restore
dc1186d 2015-07-16 19:45:08 -0700 Add response message when volume delete
075381d 2015-07-15 09:20:48 +0800 Add more details for replication
953f766 2015-07-14 18:51:58 +0800 New mock release(1.1.0) broke unit/function 
tests
8afc06c 2015-07-08 12:11:07 -0500 Remove unnecessary check for tenant 
information
c23586b 2015-07-08 11:42:59 +0800 Remove redundant statement and refactor
891ef3e 2015-06-25 13:27:42 + Use shared shell arguments provided by Session

[ Unreleased changes in openstack/python-congressclient ]

Changes in python-congressclient 1.1.0..0874721
---
0f699f8 2015-09-02 14:47:32 +0800 Add actions listing command
d7fa523 2015-08-26 14:09:29 + Updated from global requirements
36f2b47 2015-08-11 01:38:32 + Updated from global requirements
ee07cb3 2015-07-27 15:47:12 +0800 Fix constant name
f9858a8 2015-07-27 15:19:04 +0800 Support version list API in client
9693132 2015-06-20 22:38:10 +0900 Adding a test of datasource table show CLI
a102014 2015-05-21 04:52:12 -0300 Favor the use of importlib over Python 
internal __import__ statement
726d560 2015-05-07 23:37:04 + Updated from global requirements
b8a176b 2015-04-24 16:31:49 +0800 Replace stackforge with openstack in 
README.rst
8c31d3f 2015-03-31 15:33:53 -0700 Add api bindings for datasource 
request-request trigger

[ Unreleased changes in openstack/python-cueclient ]

Changes in python-cueclient 0.0.1..d9ac712
--
d9ac712 2015-08-26 14:09:42 + Updated from global requirements
47b81c3 2015-08-11 13:38:14 -0700 Update python-binding section for keystone v3 
support
d30c3b1 2015-08-11

Re: [openstack-dev] [ptl][release] flushing unreleased client library changes

2015-09-04 Thread Doug Hellmann 
Excerpts from Ben Swartzlander's message of 2015-09-04 14:51:10 -0400:
> On 09/04/2015 12:39 PM, Doug Hellmann wrote:
> > PTLs,
> >
> > We have quite a few unreleased client changes pending, and it would
> > be good to go ahead and publish them so they can be tested as part
> > of the release candidate process. I have the full list of changes for
> > each project below, so please find yours and review them and then
> > propose a release request to the openstack/releases repository.
> 
> Manila had multiple gate-breaking bugs this week and I've extended our 
> feature freeze to next Tuesday to compensate. As a result our L-3 
> milestone release is not really representative of Liberty and we'd 
> rather not do a client release until we reach RC1.

Keep in mind that the unreleased changes are not being used to test
anything at all in the gate, so there's an integration "penalty" for
delaying releases. You can have as many releases as you want, and we can
create the stable branch from the last useful release any time after it
is created. So, I still recommend releasing early and often unless you
anticipate making API or CLI breaking changes between now and RC1.

Doug

> 
> -Ben Swartzlander
> 
> > On a separate note, for next cycle we need to do a better job of
> > releasing these much much earlier (a few of these changes are at
> > least a month old). Remember that changes to libraries do not go
> > into the gate for consuming projects until that library is released.
> > If you have any suggestions for how to do improve our tracking for
> > needed releases, let me know.
> >
> > Doug
> >
> >
> > [ Unreleased changes in openstack/python-barbicanclient ]
> >
> > Changes in python-barbicanclient 3.3.0..97cc46a
> > ---
> > 4572293 2015-08-27 19:38:39 -0500 Add epilog to parser
> > 17ed50a 2015-08-25 14:58:25 + Add Unit Tests for Store and Update 
> > Payload when Payload is zero
> > 34256de 2015-08-25 09:56:24 -0500 Allow Barbican Client Secret Update 
> > Functionality
> >
> > [ Unreleased changes in openstack/python-ceilometerclient ]
> >
> > Changes in python-ceilometerclient 1.4.0..2006902
> > -
> > 2006902 2015-08-26 14:09:00 + Updated from global requirements
> > 2429dae 2015-08-25 01:32:56 + Don't try to get aodh endpoint if 
> > auth_url didn't provided
> > 6498d55 2015-08-13 20:21:24 + Updated from global requirements
> >
> > [ Unreleased changes in openstack/python-cinderclient ]
> >
> > Changes in python-cinderclient 1.3.1..1c82825
> > -
> > 1c82825 2015-09-02 17:18:28 -0700 Update path to subunit2html in 
> > post_test_hook
> > 471aea8 2015-09-02 00:53:40 + Adds command to fetch specified backend 
> > capabilities
> > 2d979dc 2015-09-01 22:35:28 +0800 Volume status management for volume 
> > migration
> > 50758ba 2015-08-27 09:39:58 -0500 Fixed test_password_prompted
> > dc6e823 2015-08-26 23:04:16 -0700 Fix help message for reset-state commands
> > f805f5a 2015-08-25 15:15:20 +0300 Add functional tests for 
> > python-cinderclient
> > 8cc3ee2 2015-08-19 18:05:34 +0300 Add support '--all-tenants' for cinder 
> > backup-list
> > 2c3169e 2015-08-11 10:18:01 -0400 CLI: Non-disruptive backup
> > 5e26906 2015-08-11 13:14:04 +0300 Add tests for python-cinderclient
> > 780a129 2015-08-09 15:57:00 +0900 Replace assertEqual(None, *) with 
> > assertIsNone in tests
> > a9405b1 2015-08-08 05:36:45 -0400 CLI: Clone CG
> > 03542ee 2015-08-04 14:21:52 -0700 Fix ClientException init when there is no 
> > message on py34
> > 2ec9a22 2015-08-03 11:14:44 +0800 Fixes table when there are multiline in 
> > result data
> > 04caf88 2015-07-30 18:24:57 +0300 Set default OS_VOLUME_API_VERSION to '2'
> > bae0bb3 2015-07-27 01:28:00 + Add commands for modifying image metadata
> > 629e548 2015-07-24 03:34:55 + Updated from global requirements
> > b51e43e 2015-07-21 01:04:02 + Remove H302
> > b426b71 2015-07-20 13:21:02 +0800 Show backup and volume info in 
> > backup_restore
> > dc1186d 2015-07-16 19:45:08 -0700 Add response message when volume delete
> > 075381d 2015-07-15 09:20:48 +0800 Add more details for replication
> > 953f766 2015-07-14 18:51:58 +0800 New mock release(1.1.0) broke 
> > unit/function tests
> > 8afc06c 2015-07-08 12:11:07 -0500 Remove unnecessary check for tenant 
> > information
> > c23586b 2015-07-08 11:42:59 +0800 Remove redundant statement and refactor
> > 891ef3e 2015-06-25 13:27:42 + Use shared shell arguments provided by 
> > Session
> >
> > [ Unreleased changes in openstack/python-congressclient ]
> >
> > Changes in python-congressclient 1.1.0..0874721
> > ---
> > 0f699f8 2015-09-02 14:47:32 +0800 Add actions listing command
> > d7fa523 2015-08-26 14:09:29 + Updated from global requirements
> > 36f2b47 2015-08-11 01:38:32 + Updated from global requirements
> > ee07cb3

Re: [openstack-dev] [ptl][release] flushing unreleased client library changes

2015-09-04 Thread Doug Hellmann 
Excerpts from Ihar Hrachyshka's message of 2015-09-04 21:07:47 +0200:
> > On 04 Sep 2015, at 18:39, Doug Hellmann  wrote:
> > 
> > 
> > PTLs,
> > 
> > We have quite a few unreleased client changes pending, and it would
> > be good to go ahead and publish them so they can be tested as part
> > of the release candidate process. I have the full list of changes for
> > each project below, so please find yours and review them and then
> > propose a release request to the openstack/releases repository.
> > 
> > On a separate note, for next cycle we need to do a better job of
> > releasing these much much earlier (a few of these changes are at
> > least a month old). Remember that changes to libraries do not go
> > into the gate for consuming projects until that library is released.
> > If you have any suggestions for how to do improve our tracking for
> > needed releases, let me know.
> > 
> > Doug
> > 
> > 
> > [ Unreleased changes in openstack/python-barbicanclient ]
> > 
> > Changes in python-barbicanclient 3.3.0..97cc46a
> 
> 
> +++
> 
> It may also block some efforts, f.e. we cannot move with fullstack tests for 
> QoS feature in neutron because those rely on neutronclient changes that are 
> not yet released.

The next release of neutronclient has some breaking changes, and since
we're heading into a 3-day weekend here in the US Kyle and I have agreed
to put that release off until Tuesday of next week. I'll do it early
US/Eastern time.

Doug

> 
> Ihar

__
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] [ptl][release] flushing unreleased client library changes

2015-09-04 Thread Ihar Hrachyshka 
> On 04 Sep 2015, at 18:39, Doug Hellmann  wrote:
> 
> 
> PTLs,
> 
> We have quite a few unreleased client changes pending, and it would
> be good to go ahead and publish them so they can be tested as part
> of the release candidate process. I have the full list of changes for
> each project below, so please find yours and review them and then
> propose a release request to the openstack/releases repository.
> 
> On a separate note, for next cycle we need to do a better job of
> releasing these much much earlier (a few of these changes are at
> least a month old). Remember that changes to libraries do not go
> into the gate for consuming projects until that library is released.
> If you have any suggestions for how to do improve our tracking for
> needed releases, let me know.
> 
> Doug
> 
> 
> [ Unreleased changes in openstack/python-barbicanclient ]
> 
> Changes in python-barbicanclient 3.3.0..97cc46a


+++

It may also block some efforts, f.e. we cannot move with fullstack tests for 
QoS feature in neutron because those rely on neutronclient changes that are not 
yet released.

Ihar


signature.asc
Description: Message signed with OpenPGP using GPGMail
__
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