-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05/05/2015 05:11 PM, Richard Brown wrote:
On 5 May 2015 at 21:40, Martin Schlander <martin.schlander@gmail.com> wrote:
It was also the first release based on the "new" factory/tumbleweed, with a very short testing phase (two devel releases with 2-3 weeks between) and iirc the roadmap itself was published very late.
Secondly, openSUSE releases shouldn't need as many testers/much testing as before, with Tumbleweed already being fairly well tested by a decent number of people running it full-time. At least I thought that was the idea.
The whole process of Tumbleweed based stable releases just needs a few small adjustments, to work well imo. (A roadmap, a slightly longer window to test things, a fixed 12 month release cycle, 26 months of lifetime (2 releases+2 months) would be a very good start).
I understand where you're coming from, but I think there are a few things I'd like you to consider
The 13.2 release required a large amount of work from a small number of people to make it a success. From an Engineering perspective it was 'just' a Tumbleweed snapshot, but from a Marketing, Branding, 'actually getting a release out of the door' perspective, it required as much work as any other software release. For 13.2 this fell on the shoulders of a tiny handful of people. The reality is that Tumbleweed has captured the excitement of a huge portion of our current contributing community, and grown it greatly, and that's great, but it does have the side effect of leaving less enthusiasm and less people to work on the Regular Release. As was discussed at the Project Meeting at oSC 15, the 'Tumbleweed-Snapshot-based-Release' model also has an interesting side effect when it comes to this part of getting a release published and marketed. Just as they share development models, both Tumbleweed and snapshot-based-releases have very similar core messages - "The latest of everything, each release". The major differences are the gap between releases and the method of maintenance after release. On each Release Day for the Regular Release, this ends up leaving us with relatively little exciting to talk about (Everything is already in Tumbleweed) and at the same time, way too much to talk about (the Changelog of 13.1 to 13.2 is insanely long and hard to filter down into exciting things to include in Release announcements) If snapshot-based-releases were to continue, we'd need to find a way to tackle that, and get people excited, talking about, and helping put together the release and it's marketing, something which is basically just the same as what we do every week, but maintained differently.
Correct, we need a better approach to the marketing of the snapshot based releases and we need more people contributing to the snapshot based releases.
But this is where my proposal for a Regular Release based on the SLE Sources comes into play. ( Video available at https://www.youtube.com/watch?v=BH99TSrfvq0 )
Switching the base of the regular release is not a solution to either of our most pressing problems (mentioned above), better marketing for regular releases and more people involvement in the creation of the regular releases. Re-basing the regular release serves a different purpose and thus without addressing the actual issues we face concerning regular releases we will inevitably end up in the same place whether the release is based on SLE sources or on snapshots. The idea of "base it in something new and they will come" is a fallacy. What we really ought to figure out is how to solve the other problems fist. Then consider if re-basing is what we want to do or if we even want a third release with the distro based on SLE sources replacing Evergreen. I don't know. What I do know is that the actual issues surrounding the regular release (a quote from your message): "The 13.2 release required a large amount of work from a small number of people to make it a success." will not be resolved just because we pick a different base. Later, Robert - -- Robert Schweikert MAY THE SOURCE BE WITH YOU Public Cloud Architect LINUX rjschwei@suse.com IRC: robjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJVSlUKAAoJEE4FgL32d2UkRvcH/Rv581fMb+M7pR0uaZzfmiSM E7WYmnFMQb65S67/PAupzr79U/fRQQaWU8ORvSI6tkR06Dvz9z1QpiQC5408Ha9+ C1Lg54VU84SO6l73e8uMpbk7NwcOj0ExCsocgc3oSaAGvp+mXTDBdNP7Z86STby+ 1mSmK8OzC7ZTb2fRDFs2YLppKJgOXOLWtbYQ3ri7pU2pwLnc94NMZ6QpTCkwpcKv Dc/q7Ar4Kv4mkuPiUWW8kHoj4vZYcDebo5uuSUZbRaKh3xpZ7YUnVUallyQJKgfB 98FdqDqMrUjlOmHoSGgAB1LhWE9JLnbVziCz9/cfR6zVjXSbd6V3Md/MHpvgJJA= =h52R -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org