Stephane Nicoll wrote:
If you guys can afford one projet per plugin, I would suggest to go
that way.
I don't think we can afford to add any more, but we could probably reuse
the m1 plugins with new version identifiers... I'd just find that very
confusing as they are completely different, for the most part.
Maybe, we can give differents rights to different people
(e.g. one project manager per plugin).
This doesn't happen in practice (different leads - perhaps, but you can
have component leads).
Have you thinked of Fix For Version? I agree with Vincent when he says
that plugins do not share the same dev/release lifecycle.
That was the downside I mentioned.
Maybe you can create a 'maven2 plugins' category in Jira?
The problems I'm seeing with the multiple plugins in JIRA are:
- version management not always done when releases are, especially when
a batch are done together as it takes a lot of time to do. Free text
would allow users to specify what they are actually using
- can't query across a group of plugins without querying across every
project in JIRA (it's concept of a project group is essentially
useless). This is a pain for developers, but even more so for users.
Because plugins are generally not getting a lot of bugs filed, and
releases rarely fix more than 5-10 issues, I don't think we're seeing
the benefits of having them separate.
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
