[openstack-dev] [all] Re-evaluating the suitability of the 6 month release cycle

Flavio Percoco flavio at redhat.com
Tue Feb 24 12:48:46 UTC 2015


On 24/02/15 11:02 +0000, Daniel P. Berrange wrote:
>On Tue, Feb 24, 2015 at 10:44:57AM +0000, Chris Dent wrote:
>> On Tue, 24 Feb 2015, Daniel P. Berrange wrote:
>>
>> >I was writing this mail for the past few days, but the nova thread
>> >today prompted me to finish it off & send it :-)
>>
>> Thanks for doing this. I think you're probably right that the current
>> release cycle has many negative impacts on the development process and
>> deserve at least some critical thinking if not outright changing.
>>
>> Thanks especially for listing some expected questions (with answers).
>>
>> One additional question I'd like to see answered in some depth is:
>> Why have unified release schedules? That is, why should Nova and Glance
>> or anything else release on the same schedule as any other
>> OpenStack-related project?
>>
>> Disentangling the release cycles might lead to stronger encapsulation
>> of, and stronger contracts between, the projects. It might also lead to
>> a total mess.
>
>For peripheral projects I don't think co-ordinate release cycle is needed,
>but for the core projects I think it is helpful in general to have some
>co-ordination of releases. It allows marketing to more effectively promote
>the new project releases, it helps when landing features that span across
>projects to know they'll be available to users at the same time in general
>and minimize burden on devs & users to remember many different dates. It
>is hard enough remembering the dates for our coordinated release cycle,
>let alone dates for 30 different project cycles. IME predictable dates is
>a really important & useful thing to have for a planning POV. This is why
>I suggested, we do a 2 month cycle, with a strict date of 1st of the month
>in Feb, Apr, Jun, Aug, Oct, Dec.

To this I'd also add that bug fixing is way easier when you have
aligned releases for projects that are expected to be deployed
together. It's easier to know what the impact of a change/bug is
throughout the infrastructure.

Flavio

>
>Regards,
>Daniel
>-- 
>|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
>|: http://libvirt.org              -o-             http://virt-manager.org :|
>|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
>|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|
>
>__________________________________________________________________________
>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

-- 
@flaper87
Flavio Percoco
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150224/059a41ff/attachment.pgp>


More information about the OpenStack-dev mailing list