Hello everyone,With the upcoming Leap release the Board is working to help Ludwigproduce the best release ever, or to be honest just better than theprevious one.We have an established task list of items that needed to be done priorrelease of distribution, like Leap 42.1 is here [1].In the past, these tasks were then distributed among the SUSE employedopenSUSE team which tried to incorporate community and in the end makesure that everything gets done.Now things are different. We would like the community to be directlyresponsible for ensuring these tasks get carried out. To accomplishthis we intend to create a full team of people taking care about whatneeds to be done for the release.We expect the people in this "Community Release Team" to be the onesresponsible for the tasks in their respective areas of responsibility.We are not necessarily expecting these people to directly do all thetasks, but it will be their responsibility that they get done.They should work towards encouraging more contributors to work withthem on these tasks, if necessary lifting a pitchfork and prod peopleto ensure all the tasks are done, or stepping up and doing the tasksalone as a last resort.The tasks can generally be split in following areas:* Marketing* Design* Infrastructure* Documentation* Translations* QATo avoid expanding this mail too much brainstorming/descriptions areattached in rst formatted file. It is not complete listing of thetasks, those are mostly in the progress [1] and if anything else happento be needed/invented by the guys volunteering to do this it will beexpanded.If you are interested on taking the lead on any of these areas andjoining this new "Community Release Team" please let Ludwig and theboard know.CheersTom + Rest of the board[1] http://tinyurl.com/grg5szf = openSUSE release teamsImportant teams external to direct release engineering== Marketing- Creating and following a marketing plan. The old plan focussed onnew features while Leap is more about stability. Marketing contentis usually found in the wiki.- Taking care of social media- Collecting statistics to measure success- Creating a press release document== Design- Making sure all Desktops are consistently branded, Fonts arecorrect on all desktops, etc.- Optional: Making sure look&feel of infrastructure related to therelease is consistent.== InfrastructureMaking sure criticial infrastructure works as designed and containsthe right data in the crucial phases:- beans.o.o- build.o.o- countdown.o.o- download.o.o- mirroring system- news.o.o- shop.o.o- software.o.o- wiki- www.o.o== Documentation- Keeping release notes, wiki articles, web site content etc relatedto the release up to date.== Translations- Communicating items to translate to language coordinators. Makingsure important pieces are translated to the main languages.- Coordinating translations between software translations and wiki(uses different processes and potentially different teams)== QA- Creating a test plan for each milestone and making sure crucialareas are covered.- Monitoring bugzilla and escalating important regressions to therelease manager- Monitoring openQA and fixing issues caused by broken test cases orengine failures