Brett Porter <[EMAIL PROTECTED]> wrote on 08/08/2003 08:20:58 AM: > I'm confused. Bummer, I was trying to not confuse people.
> 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 Yes. > - HEAD will be full of upheaval like renaming all of the properties in > plugins and likely be unstable until RC1 Yes. > - for RC1, all fixes on the branch will be merged down to HEAD That depends on whether the fixes for RC1 will require what's in HEAD or not. > 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. Yep. > 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 Sure, start one up. > 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) Using '.' in property names is fine on the STABLE branch. This will need to be handled by a compatibility layer in HEAD. > - 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 I think we'll take the tag for that from HEAD and move it into STABLE. > - avoid using the <classloader/> property on a dependency. This is fine on the branch. > Are these correct? Anything else to add? Nope, but thanks for speaking up, it's good to know if things aren't clear. -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/
