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]
RE: [Mav-user] Re: [Mav-cvs] maverick CHANGES.txt,1.34,1.35
From: Ted Husted [mailto:[EMAIL PROTECTED] Does anyone have any strong negative feelings toward Maven? http://maven.apache.org It's been spreading like Borg lately. I haven't had to use it much myself yet, but the handwriting is on the wall, and so I'm reconciling myself to the inevitable. :) If there weren't any objections, I thought I might try setting up the appropriate configuration files. This would not disturb anything we have now, only provide an alternative build/documentation mechanism. If we like it, we could then keep it and use it for 2.2.1/2.3. Otherwise, I'll retract it. Woo hoo, someone that wants to put together a real release process and build system! You're my hero :-) I like the maven concept, I just haven't had the time or inclination to climb its learning curve. If you're up for it, I'm +1. My only requirement is that users must be able to check out the project and build it without any extra configuration. Of course, Maven is supposed to help with this. BTW, you mentioned releasing a 2.2.1... but I don't believe there have been any commits (to the core) since 2.2.0. Not much point :-) 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? Jeff Schnitzer [EMAIL PROTECTED] --- 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
On Saturday, October 11, 2003, at 10:47 AM, Schnitzer, Jeff wrote: Woo hoo, someone that wants to put together a real release process and build system! You're my hero :-) I like the maven concept, I just haven't had the time or inclination to climb its learning curve. If you're up for it, I'm +1. I'm in the same boat, I have been much to preoccupied to really dig into maven. I don't think it's a bad thing to offer both build environments. Plus it will somewhat force me, Jeff and the like to finally get our hands wet with maven. My only requirement is that users must be able to check out the project and build it without any extra configuration. Of course, Maven is supposed to help with this. BTW, you mentioned releasing a 2.2.1... but I don't believe there have been any commits (to the core) since 2.2.0. Not much point :-) 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? --- 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]
