As a patch / issue is superseded, we should mark it as a WONTFIX or DUPLICATE to avoid it cluttering up JIRA. Either a patch should be applied relatively quickly or otherwise deleted or deprioritized - if left they become stale and harder to integrate. Think live fast and die young with some chance of making an impact. Bugs on the other hand should have a longer lifetime.
On Feb 8, 2008 1:12 AM, Kevin Brown <[EMAIL PROTECTED]> wrote: > Fixed but open should probably be closed. > > The patch available thing might be useful, but a lot of the existing > patches > have been superseded with new changes. I try to evaulate the pending JIRA > issues once a week or so personally, but I haven't done it since last > Saturday. > > On Feb 7, 2008 11:43 PM, Luciano Resende <[EMAIL PROTECTED]> wrote: > > > I was looking into the open JIRAs to identify areas where I could > > help, and realize that various JIRAs have patches available, and some > > have already been commented as fixed, but are still open. Some > > projects [1] are using a "patch available" field in the JIRAs to > > identify when a patch is available, and this make it easier for > > committers to identify witch are the pending patches to apply. If you > > guys think this is a good addition, I can raise a Infrastructure JIRA > > to apply the same configuration for the Shindig Jira. > > > > Thoughts ? > > > > > > [1] > > > https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=12310210&fixfor=12312358 > > > > -- > > Luciano Resende > > Apache Tuscany Committer > > http://people.apache.org/~lresende<http://people.apache.org/%7Elresende>< > http://people.apache.org/%7Elresende> > > http://lresende.blogspot.com/ > > >
