Re: Source packages / Switch to Subversion

* Andy Lester wrote:
>Is there a reason there are NOT any formal releases?  As it stands  
>now, I'm having to fake up a formal release process for my Perl  
>wrapper module.

That depends a bit on what you consider a formal release. The normal
SourceForge file release mechanism that would offer downloadables via
the project page is rather involved and I don't know of a tool that
would automate it wholesale, I doubt anyone would want to go through
it for every checkin.

Below that you'd essentially just have the issues of bundling up some
package and perhaps giving it some version label. Historically we've
never come up with a versioning scheme, and package bundling happened
automatically for every checkin. Switching to SVN would restore the
automatic bundling, and we sorta have version numbers, either via the
date string that is occasionally updated in the source, or the SVN
revision number, or bundling date.

That we actually accumulate patches for some time and then eventually
decide some new version is good to go and package that up as a release
is unlikely to happen, for lack of resources and because we're pretty
much only doing occasional bugfixes at the moment.
-- 
Björn Höhrmann · mailto:[email protected] · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 

------------------------------------------------------------------------------