As a general rule, I don't think we should be removing attachments (of
code) on JIRA issues.
- it represents a loss of code... it's not like subversion where you
can go back in time. earlier patches can also sometimes be simpler in
places, or can take a different approach, and there can be value
And another reason I just thought of... it provides better tracking of IP.
Once something goes in JIRA, multiple people might start contributing
ideas. If you remove all previous versions, there is no record of the
original submission, or who contributed what to the final.
-Yonik
On 2/21/07, Yo
+1 We should not generally remove obsolete attachments in Jira.
Doug
Yonik Seeley wrote:
As a general rule, I don't think we should be removing attachments (of
code) on JIRA issues.
- it represents a loss of code... it's not like subversion where you
can go back in time. earlier patches can a
On Wed, 21 Feb 2007 15:04:01 -0500, "Yonik Seeley" <[EMAIL PROTECTED]>
said:
> As a general rule, I don't think we should be removing attachments (of
> code) on JIRA issues.
+1
I've been hit by this in the past when I had wanted to diff the original
patch against the new one to see details on wh
Michael McCandless wrote:
Is this (ability to delete patches) something we can disable in Jira?
Yes. It is controlled by the "Delete Issues" permission: "Ability to
delete issues, comments and attachments." Lucene Java uses Jira's
Standard Permissions, and under those, the Contributor role
On 2/21/07, Doug Cutting <[EMAIL PROTECTED]> wrote:
Michael McCandless wrote:
> Is this (ability to delete patches) something we can disable in Jira?
Yes. It is controlled by the "Delete Issues" permission: "Ability to
delete issues, comments and attachments." Lucene Java uses Jira's
Standard
Yonik Seeley wrote:
I don't think most of us can see JIRA roles, so I don't know how they
map to the groups like lucene-developer, but I think committers (or
the lucene-developers JIRA group) still need removal privs (to remove
spam, IP issues, *real* removal requests, etc).
Sorry. For Lucene
: Yes. It is controlled by the "Delete Issues" permission: "Ability to
: delete issues, comments and attachments." Lucene Java uses Jira's
: Standard Permissions, and under those, the Contributor role has this
: permission. We can switch Lucene Java to use a clone of Standard
: Permissions call
Chris Hostetter wrote:
... if because of jira settings we are forced to choose between:
1) deletes are completely impossible
2) only members of "lucene-developers" jira group can delete
3) people can delete their own attachments
...i would choose #1 for safety (better to have a ton of c
