Main Stories
Slash Boxes

Slash Open Source Project

Slashcode Log In

Log In

[ Create a new account ]

Slash on SourceForge

posted by pudge on 04:18 PM May 22nd, 2000   Printer-friendly   Email story
We are using SourceForge a lot more these days, so those of you that want to keep up to date, submit patches and bug reports, etc. might want to get familiar with it, if you haven't already. We are using SourceForge for CVS and HTTP file repository, for bug reports, and for patches. We may use it for project management, too, if we feel like it.

We are going to be doing a lot more development using CVS from now on. We'll be tagging releases and revisions, so it is easy to fetch a specific version. The basic scheme is that for a given version (like 1.0.3), stick a "v" in front and change the dots to underscores, and add another number at the end. So the release version of 1.0.3 will be tagged as v1_0_3_x. We normally will shoot for that last number to be 0, but it could be something else, and will be noted in the README. In this case, the release of 1.0.3 is tagged as v1_0_3_1.

Revisions en route to version 1.0.4 will be tagged as v1_0_3_2, v1_0_3_3, etc. If there is an important revision on CVS that we don't want to release quite yet, we may announce it, and what tag it has on it.

And of course, important bug fixes can get a lot more quickly now, since we can just say "it's on CVS".

We also have a separate development branch. The current development branch is named "bender". There is a lot of stuff that is going to be in bender that is not going to be in the main branch, and if you want to play with the latest junk, or want to submit major feature patches, do it with the bender source. We may release bender tarballs occasionally, but we may not.

This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login
Loading... please wait.