Hi Mario, I haven't got a login to the blog system yet.
-Andrew Mario Behling wrote: > It would also be good, if we could announce new releases in the blog > generally. If anybody of the release team has not got a login to the > blog yet, please let me know. > > Any blog entry is also broadcasted on twitter now. > > Let's also see if we can have a newsletter for the release category. > > - Mario > > > On Tue, Apr 6, 2010 at 11:39 PM, Mario Behling <[email protected]> wrote: >> Hi brother, >> >> I put up a wiki page here: http://wiki.lxde.org/en/Category:Releases >> >> Please correct it and adapt it so it suits the process. >> >> Questions to consider: >> * Do we want to keep release notes in the wiki as well? >> * Would it be a good idea to decide on a release manager for single >> (major) components, who is the main responsible and follows up in case >> the process slows down or so? Previously there did not seem to be a >> need though. >> >> I also set up a wiki page to keep a list of releases of components. >> Reckoned it would be a good idea: >> http://wiki.lxde.org/en/LXDE_Releases >> >> Best, >> >> Mario >> >> >> On Tue, Apr 6, 2010 at 9:26 PM, Martin Bagge / brother <[email protected]> >> wrote: >>> On Tue, 6 Apr 2010, Christoph Wickert wrote: >>> >>>> I think we agreed to use a proper release process recently. This means >>>> that releases should be announced to give translators and testers a >>>> chance to look over them. >>>> >>>> Please don't release anything without testing it properly. Broken >>>> releases are a damage to the whole LXDE project. >>> We have gained alot of speed the last six month or so and I think the >>> future looks bright but the lack of a proper process of things is >>> disturbing and might jeopardize things. >>> >>> We have discussed this before and a good proposal was made with people >>> agreeing to stick to it. We haven't really used it but I think we should >>> give it another try. A proper release team and release process will ensure >>> quality in our products and avoid shitty releases that influx on other of >>> our products that has and will be great. >>> >>> A release team with a clear and _easy_ process. >>> Using freeze periods. >>> Release dependent components together - without long waiting. >>> >>> Christoph and I have already told before that we are willing to work with >>> this process. >>> Some of the other packagers I seem to recall in this is Andrea and Andrew, >>> and at IRC there have been more voices raised for this. >>> As far as I can see we can cover the major distributions package managers >>> as front line testers and I can handle the translation errors and call for >>> updates. As long as developers just producs code and tell us when to start >>> the process it will float and if you don't want to engage in the release >>> process you don't have to. >>> >>> When do we start? Can we have a wiki page with all the relevant steps and >>> procedures? >>> >>> -- >>> brother > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Lxde-list mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/lxde-list ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Lxde-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lxde-list
