Open Stack

On Mon, Apr 24, 2017 at 10:43 PM, Emilien Macchi <emilien at redhat.com> wrote:
> On Mon, Apr 17, 2017 at 1:03 PM, Emilien Macchi <emilien at redhat.com> wrote:
>> On Wed, Apr 12, 2017 at 2:47 AM, Tony Breeds <tony at bakeyournoodle.com> wrote:
>>> 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                      : 1584 (covered in zuul/layout.yaml)
>>> Checked Repos                  :  416 (match one or more of the above criteria)
>>> Repos with mitaka branches     :  409
>>> EOL Repos                      :  199 (repos that match the criteria *and* have
>>>                                        a mitaka branch) [1]
>>> NOT EOL Repos                  :  210 (repos with a mitaka branch but
>>>                                        otherwise do not match) [2]
>>> DSVM Repos (staying)           :   68 (repos that use dsvm but don't have
>>>                                        mitaka branches)
>>> Tagged Repos                   :    0
>>> Open Reviews                   :  159 (reviews to close)
>>>
>>> Please look over both lists by 2017-04-17 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.
>>
>> Please EOL stable/mitaka for:
>> - instack-undercloud (and featureV2/juno/kilo old branches)
>> - tripleo-heat-templates (and icehouse)
>> - tripleo-puppet-elements
>> - puppet-tripleo
>> - tripleo-image-elements (just featureV2)
>> - python-tripleoclient
>> - tripleo-common
>
> I'll take care of EOLing them, after reading latest email from Tony.
> I would need some help from infra to remove the branches I mentioned ^
> please (featureV2, juno, kilo, icehouse).
>
> I'll keep you posted on my progress.

EOLing for TripleO has been processed.
Big thanks to fungi & Ajaeger for their precious help here.

>> Thanks,
>>
>>> Yours Tony.
>>>
>>> [1] https://gist.github.com/tbreeds/c99e62bf8da19380e4eb130be8783be7#file-mitaka_eol_data-txt-L1
>>> [2] https://gist.github.com/tbreeds/c99e62bf8da19380e4eb130be8783be7#file-mitaka_eol_data-txt-L209
>>>
>>> __________________________________________________________________________
>>> 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
>>>
>>
>>
>>
>> --
>> Emilien Macchi
>
>
>
> --
> Emilien Macchi



-- 
Emilien Macchi