New release cycle proposal (was Rolling release model philosophy (was ...))

[Reindl Harald]

Am 06.11.2012 19:48, schrieb Peter Lemenkov:
> Hello All.
> 
> 2012/11/6 Matthieu Gautier <mgautier at fedoraproject.org>:
>> For example, if we start from Fedora20 at beginning of 2014:
>> - Fedora20(jan 2014) is a stable release. (Fedora18 eol, actual way of
>> doing)
>> - Fedora21Preview(jul 2014) is an "unstable" release. (Fedora 19 eol)
>> - Fedora21(jan 2015) is a stable release. (Fedora21Preview eol, new way
>> of doing)
>> - Fedora22Preview(jul 2015)
>> - Fedora22(jan 2016) (Fedora22Preview and Fedora20 eol)
>> - Fedora23Preview(jul 2016)
>> - Fedora23(jan 2017) (Fedora23Preview and Fedora21 eol)
> 
> So you not a maintainer but you still suggesting that we, maintainers,
> should do 2 times more job by supporting several simultaneous Fedora
> versions instead of 3 right now for more than two years. And that's
> all just because you think it's a good idea to spend my personal time
> on the rreleases I'm not using anymore

it would be enough to push LARGE changes like UsrMove / systemd / grub2
only every SECOND release as we current have and the following release
should bring only smaller changes and PLOISH the features of the last
release

this way you would even have LESS work and pressure and the distribution
would become more stable and bugfree at all becasue currently sometimes
people do simply now know where to start and how to finish because the
next BIG change is starting and a half year is very short

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 259 bytes
Desc: OpenPGP digital signature
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20121106/2e28596b/attachment.sig>