I don't think I have a weight in the decision but my preference goes to Bugzilla. JIRA looks nice but I don't see the need for a migration, Bugzilla has all the features we need (and it could be upgraded to the latest version to benefit from the improvements especially in the management of attachments).

What is the motivation for this migration exactly ?

Emmanuel Bourg


Noel J. Bergman wrote:


Guys,

There are separate requests on the table to move BETWIXT, CLI, CODEC, JEXL
and CONFIGURATION from Bugzilla to JIRA.  JELLY is already there.

Are there any other Jakarta Commons projects that want to migrate?  Are
there any that do NOT want to leave bugzilla?

Right now, each "project" is a component of Commons.  If we move to JIRA, I
would propose that we create a Project Category for Jakarta Commons, and
make each component a project, so that each one can be released separately
with its own versioning, etc.  We could use a common scheme for permissions,
notifications, etc..  Jelly has a dedicate scheme, but I think we could use
a single scheme for all of Jakarta Commons.

A bugzilla import will create a single Commons project, but we can then move
the issues from the imported project into a new project for each of our real
projects.

For each TLP, we should probably have a single permission scheme, but I'm
not going to get into that argument today.  We can create
jakarta-administrator and jakarta-commons-developer groups.

--- Noel


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]




--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to