Re: [openstack-dev] [requirements][all] Freeze starting soon!

[Tony Breeds]

On Thu, Jul 27, 2017 at 04:06:09PM +1000, Tony Breeds wrote:
> Hi All,
> As most of you working on milestone based projects know we're rigth
> at the end of the freeze week.  This means that at ~UTC Sat 29th
> requirements will also freeze.
> 
> global-requirements will be pretty hard frozen with only libraries with
> significant negative impact on the stability of Pike will be granted
> a feature freeze exception.
> 
> So if you have things you know are wrong in global-requirements now is
> the time to get them published.
> 
> The 'thaw' for global-requirements will be a little harder to define as
> we've had a number of projects take updates from n+1 into n branches so
> we'd like to try and avoid that this cycle.
> 
> upper-constraints will also be frozen but the impact on changes there is
> easier to back out so we wont be handing out FFEs like candy but it wont
> be quite so hard to get them in.
> 
> Of course we'll block the bot generated changes as soon as the freeze
> begins.

So this has been done.  There were a number of client releases that were
granted exceptions as they were just constraints bumps and it made
sense to get them into pike :)

The items that currently have excpetions are trackable here:
https://review.openstack.org/#/q/starredby:tonyb+is:open+project:openstack/requirements+branch:master

As you can see they both glance related.  I *think* the failure in the
nova py27 unit tests is bogus but we'll see after the recheck.

If it turns out to be persistent I'll need some help from the glance
team debugging that so we can take the updates.

The requirements team will discuss the status of these changes at the
next meeting if they haven't merged.


Yours Tony.


signature.asc
Description: PGP signature
__
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] Deadline extended for Community Voting

[Jimmy McArthur]

Hi all -

Just a quick note that we are extending the deadline for Community 
Voting due to some early issues we had with the voting system. The 
deadline is now Thursday, August 03 at 23:59 PM PDT / Friday, August 4 
at 6:59 AM UTC.


Thank you,
Jimmy

__
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][stable][release] stable/pike branches created for most libraries

[Dmitry Tantsur]

On 07/28/2017 11:13 PM, Doug Hellmann wrote:

As Thierry mentioned in his countdown email today, the release team has
now created the stable branches for most deliverables with type
"library".

We have 3 exceptions:

1. python-neutronclient had a late release, so I will be branching it
shortly.
2. python-barbicanclient was skipped until they have a chance to resolve
the critical bug they are working on.
3. tempest doesn't branch (we should probably reclassify that as
something other than a library to avoid issues with the automation)

All libraries should have had updates for the .gitreview file in the new
branch, the constraints URL in the tox.ini file, and the reno
configuration (in master, if the project uses reno).

Landing any of the patches in the stable/pike branch will trigger a new
documentation build publishing to docs.o.o/$project/pike.

Please take over any of the bot-created patches that do not pass your
validation jobs and fix them so that they can land as soon as possible.


Just to clarify: we cannot land the tox.ini change until the requirements repo 
is actually branched, right?




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] [openstack-doc] Attending PTG?

[Jay S Bryant]

Alex,

I will be there as well and would like to help out!

Jay


On 7/21/2017 8:41 AM, Alexandra Settle wrote:


Hey everyone,

Put your hand in the air* if you’re attending the PTG!

Myself and the potential PTL will need to start planning shortly, and 
it would be good to get an idea of numbers, and who we are planning for.


I will be looking at hosting a working bee or hack session for 
migration related issues throughout the week.


Cheers,

Alex

*reply to this ML thread



__
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] [Cinder] Not not running for PTL

[Jay S Bryant]

Sean,

Thank you for all you have done for the project over the last 4 cycles.  
Anyone who may step up to take your place will have big shoes to fill!


Jay


On 7/21/2017 6:05 AM, Sean McGinnis wrote:

Hey everyone,

So this isn't an "I'm stepping down at the end of this cycle" message, but
it is an encouragement for anyone thinking about running to step forward.

I'm fine with running again if needed. Pike is my 4th cycle as PTL, and I
think by now I've gotten the hang of most of it. But four cycles is more
than I had intended to do, and I do think it would be good for the project
to have some variety.

If you've been thinking about running but didn't want to "offend" me by
running against me or anything like that, please don't worry about it. We
have a good team and I think it is a healthy thing to switch up the lead
role once and awhile.

All that said, if no one else is in a position at the moment where they
can do this (job situation, other life commitments - please do think
about this!) then I'm certainly up for another round.

Feel free to ping me if you have any questions or want any input. I would
be glad to help.

Thanks!
Sean


__
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] [release] nominating Sean McGinnis for releases-core

[Jay S Bryant]

I too am not on the core team but know that Sean will be an asset in 
this role!


+1


On 7/27/2017 10:14 AM, Doug Hellmann wrote:

Sean has been increasingly active with the release team this cycle, and
wants to contribute. I think we should go ahead and add him to the
releases-core group.

Please respond +1/-1.

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] [docs][release][stable][ptl][infra] Strategic discussion regarding the future of documentation for EOL releases

[Jay S Bryant]

+2

I am in support of this approach.  It is clear that people are still 
looking for content from older releases long after it has been released 
but making it clearer that it is an EOL release is an improvement.


Jay


On 7/28/2017 4:38 AM, Thierry Carrez wrote:

Andreas Jaeger wrote:

On 2017-07-27 21:40, Doug Hellmann wrote:

[...]
Please encourage everyone there to explore options that require the
least amount of effort. An ideal solution is one we can implement
without heroic efforts or having to recruit an army of contributors.

I agree with the points made in general and want to stress we need
something that reduces our efforts.

Yes, agree on the general idea of keeping docs around "forever".


Two more ideas:

1) What about enhancing the openstackdocstheme to automatically add a
watermark if we publish a stable branch document?
Like on https://docs.openstack.org/mitaka/config-reference/ - which also
includes a warning that the branch is EOL. What about adding at *start*
of a branch a message to the index page like "This is the document for
the SERIES release. Please see https://releases.openstack.org/ whether
the SERIES release is still supported by the OpenStack community."

That would be a great way of ensuring that old content is not mistaken
for currently-maintained content, encouraging old users to migrate to
newer / better-supported versions.


2) The openstackdocstheme has the report a bug link feature. We can
disable this. If we EOL docs (so, push a change before we eol them), we
could remove the setting so that "report a bug" does not work.

Cheers,




__
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] [release]need help for python-tricircleclient

[Davanum Srinivas]

Hi Joe,

You can ping folks on -infra channel on monday to remove the old
branch and then we can merge the referenced review to create a fresh
one.

Thanks,
Dims

On Sat, Jul 29, 2017 at 2:22 AM, joehuang  wrote:
> Hello,
>
> The patch [1] is to add a tag for python-tricircleclient after new features
> were added to it since last release. But unfortunately, a branch called
> "stable/pike" was there in Apr., and lead to the patch can not pass the gate
> test.
>
> "deliverables/pike/python-tricircleclient.yaml:
> openstack/python-tricircleclient 563f700b62de6b57671ec077293da6fa348c250a
> not present in pike branch"
>
> Shall I cherry pick all latest introduced patches from master to the
> stable/pike branch, or the old branch which was created in Apr. should be
> renamed?
>
> [1] https://review.openstack.org/#/c/488903/
>
> Best Regards
> Chaoyi Huang (joehuang)
>
> __
> 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

[openstack-dev] [tc][dev][trove] Request to consider applying the status:maintenance-mode tag to the Trove project for the Queens cycle

[Amrith Kumar]

TC, Trove folks,

I've submitted [1] a request to the TC to consider applying the
status:maintenance-mode tag to the Trove project for the Queens cycle. If
you would like to comment on this, I suggest that you do it on the review
rather than this email thread.

Thanks

-amrith

[1] https://review.openstack.org/#/c/488947/1
__
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][stable][release] stable/pike branches created for most libraries

[ChangBo Guo]

Thanks for the reminder, I saw related patches showed up in the Gerrit,
will ensure them pass validation jobs.

2017-07-29 5:13 GMT+08:00 Doug Hellmann :

> As Thierry mentioned in his countdown email today, the release team has
> now created the stable branches for most deliverables with type
> "library".
>
> We have 3 exceptions:
>
> 1. python-neutronclient had a late release, so I will be branching it
>shortly.
> 2. python-barbicanclient was skipped until they have a chance to resolve
>the critical bug they are working on.
> 3. tempest doesn't branch (we should probably reclassify that as
>something other than a library to avoid issues with the automation)
>
> All libraries should have had updates for the .gitreview file in the new
> branch, the constraints URL in the tox.ini file, and the reno
> configuration (in master, if the project uses reno).
>
> Landing any of the patches in the stable/pike branch will trigger a new
> documentation build publishing to docs.o.o/$project/pike.
>
> Please take over any of the bot-created patches that do not pass your
> validation jobs and fix them so that they can land as soon as possible.
>
> 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
>



-- 
ChangBo Guo(gcb)
__
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] [release]need help for python-tricircleclient

[joehuang]

Hello,

The patch [1] is to add a tag for python-tricircleclient after new features 
were added to it since last release. But unfortunately, a branch called 
"stable/pike" was there in Apr., and lead to the patch can not pass the gate 
test.

"deliverables/pike/python-tricircleclient.yaml: 
openstack/python-tricircleclient 563f700b62de6b57671ec077293da6fa348c250a not 
present in pike branch"

Shall I cherry pick all latest introduced patches from master to the 
stable/pike branch, or the old branch which was created in Apr. should be 
renamed?

[1] https://review.openstack.org/#/c/488903/

Best Regards
Chaoyi Huang (joehuang)
__
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