As many of our developers are not professional developers, I'd suggest creating some guidelines to help new comers instead of just blaming them. Most of us are still learning how to run such a project. So if from your experience in your professional career you have some ideas to share with us, please do it.
On Mon, Apr 12, 2010 at 6:14 PM, Marty Jack <[email protected]> wrote: > I have re-released LXTask to correct the build failure. > > I do not intend to make a habit of cleaning up after other people's messes in > the future. It is totally unacceptable that this happened and that it was > allowed to persist for seven days after being known. It makes the whole > project look dumb. If this were my project the responsible developer would > lose file release privileges until having demonstrated that they know how to > do it properly. > > Another little item that wasn't done is to tag the release. > > ------------------------------------------------------------------------------ > 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
