On 09/12/2012 14:30, Ioan Eugen Stan wrote:
I've analyzed the situation a bit. Here's a summary.
Total number of issues per project - total issues (including open) /
open issues.
James Basic Mailet Toolkit - MAILETBASE 7 Issues / 0 open
James Crytography Mailets - MAILETCRYPTO 9 Issues / 0 open
James Mailet - MAILET 46 Issues -- not applicable
James Mailets Standard - MAILETSTANDARD 13 Issues / 5 open
James MailetDocs Maven Plugin - MAILETDOCS 7 Issues / 3 open
James Ai Mailets - JAMESMAILAI 2 issues / 1 open
We have a total of 9 open issues. spread over the 5 projects we wish
to close. We would make history confusing for 38-9= 29 issues if we
move + delete jira projects. I personally think it's reasonable for
people to do a bit of extra work if they wish to find out more about
the issues related to each commit. Another argument is that those
issues are not that important so people will probably never search/get
to them.
Considering this, my recommendation is to Move+Archive ('Hiding'). I
believe keeping all those projects will be more confusing than useful
on the long turn.
I tried to make Basic Mailets Read-only following [2] but I don't have
enough rights to change the Permissions. Eric do you have permissions
to make the project Read-Only/ Archive them?
I also read this morning [2] (which is not an apache page) but I also
had not the rights to do anything. I think those settings are in the
hands of apache infra and the goal is not to give delegation to the
projects on that level.
Closing a jira project is just like opening one: it's infra
responsibility I think.
But once again, I simply don't like the idea of losing any historical
information and I expect infra will ask you why you want to do this.
Even retired projects (in the attic) are still accessible on JIRA.
I favor the readonly mode, recreating the 9 open one in the new JIRA
project (with a comment on the old ones to redirect to the new ones).
But unless someone pops-up here, it's all in your hand.
To make this information available, please simply announce it in a
separate mail on the james dev + mailet lists with a notice of 3 days so
everyone is well informed on what's going on.
Thx, Eric
I think simple is better. What do you think?
[1] https://confluence.atlassian.com/display/JIRA/Moving+an+Issue
[2]
https://confluence.atlassian.com/display/JIRA/Archiving+a+Project#ArchivingaProject-'Hiding'aproject
Thx, Eric
[1] https://issues.apache.org/jira/browse/MAILET-41
[2] http://wiki.apache.org/general/Jenkins
[3] https://issues.apache.org/jira/browse/MAILET-44
---------------------------------------------------------------------
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]
