Thierry Carrez wrote: > TL;DR: > - We propose to stop tagging coordinated point releases (like 2015.1.1) > - We continue maintaining stable branches as a trusted source of stable > updates for all projects though
Thanks everyone for the constructive discussion on this. Lots of good stuff. Let me summarize the objections so far: 1. we'd lose the focus rhythm Point releases triggered some attention to stable branches: the necessity to fix the CI there when it's broken, and a surge in backports activity. 2. it would be difficult to get proper release notes If we don't have point releases anymore, we don't have release notes anymore. Release notes contain various types of information: the list of security fixes, the occasional upgrade warning, and the list of bugfixes. 3. we'd lose reference points Tagged versions made great common reference points to share information between various distros/deployments. If a distro packaged 2014.2.2, you could take the same tag and package it and assume it was the same thing. They also served as "fixed in version X" information on OSSAs. 4. we'd lose the "works well together" piece of information The various pieces tagged with the same version number could be assumed to work well together. Recovering that would have to be pieced back together from commit dates and/or openstack/openstack stable branches. Missed anything ? Please see my following email as I try to address each of those. -- Thierry Carrez (ttx) __________________________________________________________________________ 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
