Re: [openstack-dev] [stable] Stable branch status and proposed stable-maint members mentoring

2015-01-14 Thread Adam Gandelman
Thanks, Ihar. Lets make this the 'official' tracking pad for stable
branches.  We were previously using branch-specific pads (ie,
https://etherpad.openstack.org/p/StableJuno) but it makes sense to track
both releases in one place.  I've updated it with current staus there and
added a reference on the stable branch wiki page [1]

Cheers,
Adam

[1] https://wiki.openstack.org/wiki/StableBranch#Gate_Status

On Wed, Jan 14, 2015 at 4:37 AM, Ihar Hrachyshka ihrac...@redhat.com
wrote:

 On 01/09/2015 01:02 PM, Ihar Hrachyshka wrote:

 I think we should have some common document (etherpad?) with branch
 status and links.


 OK, I moved forward and created an Etherpad. I also filed it in with
 current state. Please fill it in with updates.

 https://etherpad.openstack.org/p/stable-tracker

 __
 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] [stable] Stable branch status and proposed stable-maint members mentoring

2015-01-14 Thread Ihar Hrachyshka

On 01/09/2015 01:02 PM, Ihar Hrachyshka wrote:
I think we should have some common document (etherpad?) with branch 
status and links. 


OK, I moved forward and created an Etherpad. I also filed it in with 
current state. Please fill it in with updates.


https://etherpad.openstack.org/p/stable-tracker

__
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] [stable] Stable branch status and proposed stable-maint members mentoring

2015-01-09 Thread Thierry Carrez
Hi stable-maint people,

We seem to still have a number of issues with stable branch in the gate,
both in Icehouse and Juno. I'd like to help where I can but I have a bit
of a hard time tracking down the remaining failures and things that have
already been worked on (we really need a dashboard there...)

Ihar  Adam: as Icehouse and Juno champions, could you post a quick
status update here, and let us know where the rest of us can help ?

In the future, how could we better communicate on that ? Should we make
more use of #openstack-stable to communicate on issues and progress ?
Should we set up a Stable status wiki page ?

Another topic is the mentoring of new propose $PROJECT-stable-maint
members. We have a number of proposed people to contact and introduce
the stable branch policy to (before we add them to the group):

Erno Kuvaja (glance-stable-maint)
Amrith Kumar (trove-stable-maint)
Lin-Hua Cheng (horizon-stable-maint)

Is someone in stable-maint-core interested in reaching out to them ? If
not I'll probably handle that.

-- 
Thierry Carrez (ttx)

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [stable] Stable branch status and proposed stable-maint members mentoring

2015-01-09 Thread Ihar Hrachyshka

On 01/09/2015 11:44 AM, Thierry Carrez wrote:

Hi stable-maint people,

We seem to still have a number of issues with stable branch in the gate,
both in Icehouse and Juno. I'd like to help where I can but I have a bit
of a hard time tracking down the remaining failures and things that have
already been worked on (we really need a dashboard there...)

Ihar  Adam: as Icehouse and Juno champions, could you post a quick
status update here, and let us know where the rest of us can help ?


Icehouse:

current:
- tempest, nova failures due to fresh boto release.
To be fixed with: https://review.openstack.org/#/c/146049/ (needs 
backports to Juno and Icehouse, and merge of openstack bot patches to 
nova and tempest repos)


recently fixed:
- keystone failed before due to new pip, fixed with 
I3e0f1c2d9a859f276f74cb1d1477f92fe8a7524e.
- nova failed before due to huge logs filled with DeprecationWarning 
warnings (fixed with latest stevedore release).


Other than that, there were some failures due to pypi mirror issues.



In the future, how could we better communicate on that ? Should we make
more use of #openstack-stable to communicate on issues and progress ?
Should we set up a Stable status wiki page ?
I think we should have some common document (etherpad?) with branch 
status and links.


Another topic is the mentoring of new propose $PROJECT-stable-maint
members. We have a number of proposed people to contact and introduce
the stable branch policy to (before we add them to the group):

Erno Kuvaja (glance-stable-maint)
Amrith Kumar (trove-stable-maint)
Lin-Hua Cheng (horizon-stable-maint)

Is someone in stable-maint-core interested in reaching out to them ? If
not I'll probably handle that.

I would expect stable liaisons to handle that. Don't we have those 
assigned to the projects?


/Ihar

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [stable] Stable branch status and proposed stable-maint members mentoring

2015-01-09 Thread Thierry Carrez
Ihar Hrachyshka wrote:
 On 01/09/2015 11:44 AM, Thierry Carrez wrote:
 Another topic is the mentoring of new propose $PROJECT-stable-maint
 members. We have a number of proposed people to contact and introduce
 the stable branch policy to (before we add them to the group):

 Erno Kuvaja (glance-stable-maint)
 Amrith Kumar (trove-stable-maint)
 Lin-Hua Cheng (horizon-stable-maint)

 Is someone in stable-maint-core interested in reaching out to them ? If
 not I'll probably handle that.

 I would expect stable liaisons to handle that. Don't we have those
 assigned to the projects?

Well, some of them are the proposed liaisons :) Also I think we should
not dilute the message too much and, as guardians of the policy, apply
the brainwashing directly and get a clear feel of how well it is
understood. I don't mind doing it (it's just an email with offer for QA
on IRC) if nobody wants it.

-- 
Thierry Carrez (ttx)

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev