I'm hoping to get the chance to contribute some development time to Maven2 in future, so here is my 2c - maybe it only counts for 1c right now! :-)
On 10/15/05, Brett Porter <[EMAIL PROTECTED]> wrote: > Now that 2.0 is getting close to rolling out, I wanted to open the floor > for discussion about how we will manage the code going forward. We have > a lot more freedom to do things better now that we're no longer > bootstrapping ourselves. > > Here are some areas to think about: > - having a 2.1 trunk and 2.0.1 branch (or vice versa, or neither) I like the way the subverison devs do this for subversion itself. They would have a 2.0.x (literally named "2.0.x") branch, keeping the trunk for 2.1, and then tag 2.0.1, 2.0.2 etc along the way. Later, a 2.1.x branch can be created to use trunk for 2.2, and so on. What would the rule be for backporting fixes? > - whether to mark versions as -alpha, -beta along the way, or only label > releases at those points (for 2.1 only on this) Do you need to deliver early 2.1 releases so that plugin developers can try out new APIs and provide feedback before those APIs get locked down? > - ensuring plugins remain compatible with 2.0. When a new feature is added to 2.1 that a plugin would like to use, it should be able to do so, perhaps by branching their 2.0-compatible version and updating the minimum m2 version requirement for the new plugin version? > - segregation of the SVN tree to mirror our release process (some > thoughts in jira on this - essentially making archetypes, plugins and > the sandbox separate to to the main tree) Segregating the sources like this is a good idea. > - how to manage versioning of plugins in JIRA Do they need to be separately versioned JIRA projects so that milestones can be set accordingly for bug fixes and feature enhancements? If so, how to do those plugin versions compare with plugin versions used by Maven-1 plugins? If there is a collision here, perhaps the new plugins can be called maven2-xxx-plugin in JIRA? > Ok, not going to include much content here. I have a few thoughts, but I > was hoping to get a varierty of opinions from devs and potential > contributors about what would work best for them. Kind Regards, John Fallows. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
