lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley" <yo...@apache.org>
Subject removal of JIRA attachments
Date Wed, 21 Feb 2007 20:04:01 GMT
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 in
keeping them around.
- it makes earlier comments in a JIRA issue harder to follow (the
comments now refer to something that is no longer accessible)
- If people submit single patches for an issue, it's easy to tell
which is the latest... no need to remove earlier ones.  Even if they
are named differently, it's still relatively easy to tell what was
added latest.  Confusion happens because people add multiple separate
files.

When a user requests that all patches except the latest be removed
(just for the purpose of clarity), we should educate them.  If they
have multiple versions of multiple files, we should ask them to submit
a single patch for clarity rather than removing outdated stuff for
clarity.

Thoughts?

-Yonik

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message