Re: [Mav-user] Re: [Mav-cvs] maverick CHANGES.txt,1.34,1.35
Schnitzer, Jeff wrote: I like the versioning scheme you described, which is what Orion has been using for aeons now. Releases always have increasing version numbers, but new ones are labeled experimental and after-the-fact some are labeled stable. I'm not sure how well sourceforge's system supports that model, can we just rename releases with -experimental or -stable? Yes, it looks like that we can. I've some fixes to make on the opt-formproc CVS, then I'll cut an alpha release and test changing then name. I don't think this will change the name of the archive, but it should change the label on the website. -Ted. --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php [INVALID FOOTER]
Re: [Mav-user] Re: [Mav-cvs] maverick CHANGES.txt,1.34,1.35
Mike Moulton wrote: Regarding changes to the mav core, I have some pending changes to XSLTransform that I talked about earlier. I have yet to commit them as I believe Ted wanted to get the cvs list up and running first. I will commit my changes shortly, unless there is some reason I shouldn't. Ted / Jeff? I'd say that anyone with some outstanding changes commit should go ahead and do so. We could then cut a 2.2.1 with these changes. Once this goes from experimental to stable, we could then cut a 2.3 with just the package change. -Ted. --- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php [INVALID FOOTER]
