[openstack-dev] [puppet] (officially) deprecate stable/{grizzly, havana} branches
Clayton O'Neill
clayton at oneill.net
Fri Jun 19 22:41:40 UTC 2015
I'd vote for stable -2. I think a number of people do an upgrade maybe
once a year. I believe CERN just upgraded to juno recently.
On Tue, Jun 16, 2015 at 1:36 PM, Richard Raseley <richard at raseley.com>
wrote:
> Matt Fischer wrote:
>
>> +1 from me for deprecation.
>>
>> I'd also like to know or have an official policy for future
>> deprecations, such as when will we deprecate Icehouse?
>>
>> On Tue, Jun 16, 2015 at 9:50 AM, Emilien Macchi <emilien at redhat.com
>> <mailto:emilien at redhat.com>> wrote:
>>
>> Hi,
>>
>> Some of our modules have stable/grizzly and stable/havana branches.
>> Some
>> of them have the CI broken due to rspec issues that would require some
>> investigation and time if we wanted to fix it.
>>
>> We would like to know who plan to backport some patches in these
>> branches?
>>
>> If nobody plans to do that, we will let the branches as they are now
>> but
>> won't officially support them.
>>
>> By support I mean maintaining the CI jobs green (rspec, syntax, etc),
>> fixing bugs and adding new features.
>>
>> Any feedback is welcome!
>>
>> Regards,
>> --
>> Emilien Macchi
>>
>>
> I echo your +1.
>
> Perhaps most current stable supported, -1 stable version?
>
> In that example, once the Liberty release of modules (or a particular
> module) is cut we would support Liberty and Kilo. When the same happens for
> M, we would deprecate Kilo and support M and Liberty.
>
> Stable -2 also seems sane - I don't have a good sense of how far people
> are generally behind.
>
>
> __________________________________________________________________________
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150619/0a2aea74/attachment.html>
More information about the OpenStack-dev
mailing list