OK, Sorry for the recent degradation in quality assurance. I'm just too busy recently. After working for more than 12 hours a day in the hospital, I'm quite exhausted and don't have much time to do all the hacking and testing. Can we set up a QA team to handle the release management? I mean, when some new features are completed, developers send message in the mailing list. Then, the QA team do the testing and fix build issues. If things are OK, they release the tarballs. Besides, when translation coordinator find most translations are completed, he can call the QA team to check package integrity. If no problems are found, new release can be made by QA team for translation updates.
So, for me, I only push things I developed into svn continuously, and I don't make release myself. The QA people just do QA, and do the release management. Is this model possible? On Sat, Dec 12, 2009 at 6:00 AM, Julien Lavergne <[email protected]> wrote: > Le vendredi 11 décembre 2009 à 20:33 +0100, Christoph Wickert a écrit : >> * lxpanel-0.5.4 wont build because configure breaks due to the >> missing cpufreq plugin. Was the plugin supposed to be in the >> tarball or was configure not updated before doing the release? >> Was it tested at all? > One test that can be made is the "make dist check". Fixing all errors is > painful, but that prevent most of problems for the tarball side. Also, > it's not too late to do a 0.5.4.1 release with the fixes. Mistakes > happens :) > > Regards, > Julien Lavergne > > > ------------------------------------------------------------------------------ > Return on Information: > Google Enterprise Search pays you back > Get the facts. > http://p.sf.net/sfu/google-dev2dev > _______________________________________________ > Lxde-list mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/lxde-list > ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ Lxde-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lxde-list
