I'm confused. My understanding is: - So RC1_STABLE is the branch people should be using if they want to build and use latest maven and do bits and pieces development - HEAD will be full of upheaval like renaming all of the properties in plugins and likely be unstable until RC1 - for RC1, all fixes on the branch will be merged down to HEAD
Not that it matters to me as I'm not a committer :) I'm just wondering where to dev my patches. Seems like branch is the place to be. Is it possible a rough wiki page could be put up to explain this and linked from the CVS instructions on the site? I can do that if what I've said is right. Also, I'd like to get a rough list of stuff that should be avoided on the branch as it is changing on HEAD. From what I understand that would be things like: - don't use '.' in plugin property names for new properties. Follow the convention of [a-z][A-Z_0-9]+ (eg someVariable) - cross plugin property fetching will change - keep it to a minimum (ie if you need it - do one <j:set/> to get the var into the context, then use that one - avoid using the <classloader/> property on a dependency. Are these correct? Anything else to add? Cheers, Brett > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Friday, 8 August 2003 3:12 AM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: MAVEN_RC1_STABLE branch > > > As you may have noticed, the MAVEN_RC1_STABLE branch is now open for > business. > > I've backported the fixes post the RC1 refactor tag, so it > should all be > up to date. > > The goal is to keep this a functioning set of code and apply > fixes to it > until the refactor is ready to be dropped in. As such, all > non-core work > should happen in this branch. > > -- > dIon Gillard, Multitask Consulting > Blog: http://blogs.codehaus.org/people/dion/ >
