On Thu, 28 Apr 2016 14:59, Tomas Chvatal wrote:

Hello everyone,

With the upcoming Leap release the Board is working to help Ludwig produce the best release ever, or to be honest just better than the previous one.

... snip ...

* QA

Apropos testing: What kind of "zypper dup" upgrade will be offically allowed? Beyond Leap 42.1 -> 42.2 , would a openSUSE 13.2 -> Leap42.2 be tested as 'upgrade path' ? IMHO it should be tested at least once to give a offical statement (e.g. impossible / possible but... / works if no extra repo) Thank you for your consideration. - Yamaban. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

El 28/04/16 a las 14:59, Tomas Chvatal escribió:

Hello everyone,

With the upcoming Leap release the Board is working to help Ludwig produce the best release ever, or to be honest just better than the previous one.

We have an established task list of items that needed to be done prior release of distribution, like Leap 42.1 is here [1]. In the past, these tasks were then distributed among the SUSE employed openSUSE team which tried to incorporate community and in the end make sure that everything gets done.

Now things are different. We would like the community to be directly responsible for ensuring these tasks get carried out. To accomplish this we intend to create a full team of people taking care about what needs to be done for the release. We expect the people in this "Community Release Team" to be the ones responsible for the tasks in their respective areas of responsibility. We are not necessarily expecting these people to directly do all the tasks, but it will be their responsibility that they get done. They should work towards encouraging more contributors to work with them on these tasks, if necessary lifting a pitchfork and prod people to ensure all the tasks are done, or stepping up and doing the tasks alone as a last resort.

The tasks can generally be split in following areas: * Marketing * Design * Infrastructure * Documentation * Translations * QA

To avoid expanding this mail too much brainstorming/descriptions are attached in rst formatted file. It is not complete listing of the tasks, those are mostly in the progress [1] and if anything else happen to be needed/invented by the guys volunteering to do this it will be expanded.

If you are interested on taking the lead on any of these areas and joining this new "Community Release Team" please let Ludwig and the board know.

Cheers

Tom + Rest of the board

[1] http://tinyurl.com/grg5szf

Hi! I'm not a developer, but I would like to help in some areas... I'm thinking something like translations, or marketing (I'll keep continue helping in other areas like spanish forum, "spam" in my blog, or spreading the word in free social media) 've phun! -- ------------------- GPG Key: 0xC9B7E22A Aprende a proteger la privacidad de tu correo: https://emailselfdefense.fsf.org/es/