first of all I would add more lists:
very low volume announce (like dev-cpp-announce) just for admins to announce new releases and development milestones. I think a very high volume dev-cpp-cvs would be nice - it would contain auto generated messages about cvs commits.
I could use a cvs snapshot changing daily (or if possible whenever any change is made).
Also I would setup a link for "patches" for example like this project has: http://sf.net/projects/fuse-emulator . Anyone can upload a diff and specify what is it for. The difference between this and personal email is that it could be discussed within a wider group of people.
The project definitely needs to have some FAQ regarding submiting bug reports: the tested version must be either latest stable release or the latest alpha/beta build, OS must be specified, point by point walkthrough how to achieve the problemous moment, description what happens and what should happen. I found bugzilla requirements very helpful when submiting bug report - so it could serve as an example.
just my $.02 :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I created the dev-cpp-announce maling list. About the one for CVS, i'm not sure sourceforge can handle that (automatic sending of cvs changes)
The Patches tracker should be now visible to everybody, and registered sf users can submit their patches.
Surely the Dev-C++ FAQ needs to be updated, and a section on sending bug reports can be added.
Greetings,
Colin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
first of all I would add more lists:
very low volume announce (like dev-cpp-announce) just for admins to announce new releases and development milestones. I think a very high volume dev-cpp-cvs would be nice - it would contain auto generated messages about cvs commits.
I could use a cvs snapshot changing daily (or if possible whenever any change is made).
Also I think it would be ok with everybody if the project started accepting donations through sf page (similar to other projects http://sourceforge.net/donate/index.php?group_id=84122 )
Also I would setup a link for "patches" for example like this project has: http://sf.net/projects/fuse-emulator . Anyone can upload a diff and specify what is it for. The difference between this and personal email is that it could be discussed within a wider group of people.
The project definitely needs to have some FAQ regarding submiting bug reports: the tested version must be either latest stable release or the latest alpha/beta build, OS must be specified, point by point walkthrough how to achieve the problemous moment, description what happens and what should happen. I found bugzilla requirements very helpful when submiting bug report - so it could serve as an example.
just my $.02 :)
Hi,
I created the dev-cpp-announce maling list. About the one for CVS, i'm not sure sourceforge can handle that (automatic sending of cvs changes)
The Patches tracker should be now visible to everybody, and registered sf users can submit their patches.
Surely the Dev-C++ FAQ needs to be updated, and a section on sending bug reports can be added.
Greetings,
Colin
if you could please setup the dev-cpp-cvs (or -commits) list, I will setup cvs to mail that list. Documentation for that is here: http://sourceforge.net/docman/display_doc.php?docid=772&group_id=1#scriptsyncmail
I took the liberty to setup (well, mainly for test) notifications just for myself, that is until the new mailing list is created...
Good idea, the list dev-cpp-cvs has been created.
Colin