On Wed, 7 Apr 2010, PCMan wrote: > Maybe we should create a set of lxde-devel tools and make this a > standard develop-time or build-time dependency of lxde components. It > can contains;
[...] > Then, make all of these tools included in one lxde-devel package.Then > developers can get it installed for use in lxde development. I do not think you should mix devel tasks and QA tasks. And as I have told you before, when developers touch the po files I find myself tied in merge hell for hours and I can not encourage that at all - please, never touch the po files. AT ALL. Tell me (the list, what ever) that there are strings added/updated and I'll manage the process from there. > Regarding to release process, I agree with all of you for setting up a > release team. For alpha or beta release I think there shouldn't be > restrictions since the purpose of alpha or beta release is for helping > development. However stable release must be made by release team after > QA only. Developers drop mails in the mailing list when new release is > suitable and release/QA team make the release after proper testing. Something like that sounds reasonable enough. -- 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
