On 18 December 2013 09:55, Jos Poortvliet <jos@opensuse.org> wrote:
On Wednesday 18 December 2013 07:09:13 Stephan Kulow wrote:
Am 17.12.2013 23:46, schrieb Simon:
I guess looking at it from the outside could you change the releasen cycle for the next 2 releases to yearly, that would in theory give the team 8 month's (2 lots of 4) to focus on non release work before starting the release process. From a user perspective waiting a year instead of 8 months seems better then skipping a release. If we skip a release we also miss out on all the publicity generated by a release and a release half way through would give a chance to test some of the stuff that had already been done. If it worked for the next 2 releases maybe it cold be kept long term so the tea can keep improving openSUSE. This is something I considered proposing too, so I support it. The last release in July (12.2) was not our strongest one - you have trouble starting into the new year, then there is the openSUSE conference and suddenly you find yourself in July with a not so great release that no one actually cares for because the journalists are already in summer vacation mode.
So with the additional risks involved with others taking over the tasks the openSUSE team did for the last releases, it's not too unlikely the same slip might happen again - so why not plan with it and always release in October? Sounds very good to me, too - a October (or November) release is better from a whole bunch of reasons ;-)
So, +1
I've lost count of the times I've suggested a yearly cycle for releases, and Oct/Nov releases always seem to go smoother for us, so +1 for me for 13.2 coming out in October with an expectation that 13.3 would come out October 2015 Hi all, I meant to hit send on this last night but i didn't so apologies i see
On 12/18/2013 08:10 PM, Richard Brown wrote: there was another proposal for a respin since. Another thought i just had that i don't really care about either way. If we were to go to a yearly release why not incorporate 1 or 2 "tumbleweed snapshots". The release schedule could look something like. October openSUSE 14.0 - openSUSE release March openSUSE 14.1 - tumbleweed snapshot 1 July openSUSE 14.2 - tumbleweed snapshot 2 Or alternatively October openSUSE 13.2 - openSUSE release March openSUSE 13.2 sp 1 - tumbleweed snapshot 1 July openSUSE 13.2 sp 2 - tumbleweed snapshot 2 14.0 could also be 14.1 but that doesn't really matter there could equally just be one snapshot. The tumbleweed snapshots would basically be the previous release + tumbleweed to that point on a DVD, the tumbleweed policies would apply as would branding marketing etc. As tumbleweed is used by a large number of people testing shouldn't theoretically be much of a issue. If nothing else it would make life easier for tumbleweed users as hopefully we would be able to get updated video drivers etc, and they wouldn't need to download a DVD install then re download half there system. Cheers Simon -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org