[OpenStack-docs] Fwd: [openstack-dev] [all][stable][ptls] Tagging liberty as EOL

Andreas Jaeger aj at suse.com
Tue Nov 22 18:08:41 UTC 2016


Team,

do we need/want to do any special end-of-life set up of liberty?

Now is the time to do it...

Andreas


-------- Forwarded Message --------
Subject: [openstack-dev] [all][stable][ptls] Tagging liberty as EOL
Date: Tue, 22 Nov 2016 13:35:48 +1100
From: Tony Breeds <tony at bakeyournoodle.com>
Reply-To: OpenStack Development Mailing List (not for usage questions)
<openstack-dev at lists.openstack.org>
To: OpenStack Development Mailing List <openstack-dev at lists.openstack.org>

Hi all,
    I'm late in sending this announement, but I'm glad to see several
projects
have already requested EOL releases to make it trivial and obvious where to
apply the tag.

I'm proposing to EOL all projects that meet one or more of the following
criteria:

- The project is openstack-dev/devstack, openstack-dev/grenade or
  openstack/requirements
- The project has the 'check-requirements' job listed as a template in
  project-config:zuul/layout.yaml
- The project gates with either devstack or grenade jobs
- The project is listed in governance:reference/projects.yaml and is tagged
  with 'stable:follows-policy'.


Some statistics:
All Repos                      : 1493 (covered in zuul/layout.yaml)
Checked Repos                  :  406 (match one or more of the above
criteria)
Repos with liberty branches    :  305
EOL Repos                      :  171 (repos that match the criteria
*and* have
                                       a liberty branch) [1]
NOT EOL Repos                  :  134 (repos with a liberty branch but
                                       otherwise do not match) [2]
DSVM Repos (staying)           :   68 (repos that use dsvm but don't have
                                       liberty branches)
Open Reviews                   :   94 (reviews to close)


Please look over both lists by 2016-11-27 00:00 UTC and let me know if:
- A project is in list 1 and *really* *really* wants to opt *OUT* of
EOLing and
  why.  Note doing this will amost certainly reduce the testing coverage you
  have in the gate.
- A project is in list 2 that would like to opt *IN* to tagging/EOLing

Any projects that will be EOL'd will need all open reviews abandoned
before it
can be processed.  I'm very happy to do this, or if I don't have
permissios to
do it ask a gerrit admin to do it.

I'll batch the removal of the stable/liberty branches between Nov 28th
and Dec
3rd (UTC+1100).  Then during Decemeber I'll attempt to cleanup
zuul/layout.yaml
to remove liberty exclusions and jobs.

Yours Tony.

[1]
https://gist.github.com/tbreeds/93cd346c37aa46269456f56649f0a4ac#file-liberty_eol_data-txt-L1
[2]
https://gist.github.com/tbreeds/93cd346c37aa46269456f56649f0a4ac#file-liberty_eol_data-txt-L181

-------------- next part --------------
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



More information about the OpenStack-docs mailing list