If you guys can afford one projet per plugin, I would suggest to go that way. Maybe, we can give differents rights to different people (e.g. one project manager per plugin).
Have you thinked of Fix For Version? I agree with Vincent when he says that plugins do not share the same dev/release lifecycle. Maybe you can create a 'maven2 plugins' category in Jira? Cheers, St�phane On 5/26/05, Brett Porter <[EMAIL PROTECTED]> wrote: > Hi, > > Given the resounding mess that resulted from giving each plugin its own > project in JIRA for m1, I'd like to propose the following for m2: > > - create a maven-plugins project > - add new plugins as components > - add a "component version" field that is free text. > > Upside: > - more manageable > - can still query per plugin/per version as long as the text is well formed > > Downside: > - can't use roadmap etc > - can't bulk change version for scheduling > > In general, I don't think this is a problem - I think that plugins tend > to have very few bugs assigned to them at any given time if they are > being looked after (xdoc is an exception as it is basically a product > unto itself in m1). > > Thoughts? Should we move towards this in m1 too, or just let them wind > down over time? > > - Brett > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- .::You're welcome ::. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
