-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi list,
I agree with what Christoph and brother said and just wanted to add my 2 cents regarding a release process. When you think you are ready for a release freeze the code (accept only bug fixes/translation fixes) and release a release candidate as tar so that packagers can get a heads up and can start preparing and testing for the upcoming release. After a week or so of freeze time release (let the release team release) the final tar ball which by then should be guaranteed to build without errors. I think with the above (rather simple) procedure the quality of the releases can be improved and packages can be added to the major distributions faster. (Sure in some cases a more complicated approach is needed but I will leave that to the release team ;) ) Regards, Nikolas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAku7SX4ACgkQecnFg9AIQHL7EgCgjFxKoix26sP8YnY4dXQ5TZRR ATQAni0JcrJj6+N10LYHKcCYsGHyPjJs =EQVf -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ 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
