Re: Pardon me for being the n00b here...
Amos Hayes <[email protected]> Mon, 15 Oct 2001 22:17:38 -0400 (EDT)
| Newsgroups | gmane.music.equipment.slimp3.dev |
|---|---|
| Message-ID | <[email protected]> |
On Mon, 15 Oct 2001, Mark C . Langston wrote: > I think the rash of multi-version patches is really more an issue of > confusion at this point than anything else. As such, it's manageable > through communication. Agreed. Perhaps those in the know could write up a "SliMP3 Developer HOWTO" for new folks getting involved. It's a bit much to assume that every new recruit is going to go through the entire archive to figure out what to do to submit changes properly. Non-exhaustive list of items to include: 1) How to grab the source: cvs -d:pserver:anonymous-d6Wnq0YjlhfDbRF6Jby/[email protected]:/cvsroot/slimp3 login cvs -z3 -d:pserver:anonymous-d6Wnq0YjlhfDbRF6Jby/[email protected]:/cvsroot/slimp3 co slimp3 2) How to see what needs doing: Visit http://sourceforge.net/projects/slimp3/ and check the bugs/features list. Add something to the list if you so desire. Indicate your willingness to work on it. 3) While your working on your changes, be sure to update your source often, especially just before generating your diff. cvs update (help here please) 4) After you've made you changes, how to submit them. cvf diff -upB (did I get that right?) Mail the diff output to [email protected] Someone will review what you sent and merge it into CVS. I'm also in agreement about the stable vs. current branches. Since I don't yet have a SliMP3 in my posession, I'm inclined to run around fixing up little problems and usability issues rather than blast away on features that I can't test. Let's make use of the sourceforge tools and decide what features to have in a release, get the features into the "current" branch (we call it main/latest at work), and then branch it off to fix the bugs without adding any more feature code. Development can continue on the main branch while the release is brought up to snuff. The yahoo groups are great for being an email list as well, but if we aren't going to use the sourceforge forums, we might want to put a link in to the yahoo groups so people can get at everything from one spot. -- Amos Hayes [email protected] ------------------------ Yahoo! Groups Sponsor ---------------------~--> Get your FREE VeriSign guide to security solutions for your web site: encrypting transactions, securing intranets, and more! http://us.click.yahoo.com/UnN2wB/m5_CAA/yigFAA/rIp0lB/TM ---------------------------------------------------------------------~-> To unsubscribe from this group, send an email to: [email protected] Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/