qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robbie Gemmell (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (QPID-3469) JIRA clean up for Java client/broker
Date Sat, 03 Mar 2012 14:47:57 GMT

     [ https://issues.apache.org/jira/browse/QPID-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Robbie Gemmell updated QPID-3469:

    Labels: derbystore  (was: )
> JIRA clean up for Java client/broker
> ------------------------------------
>                 Key: QPID-3469
>                 URL: https://issues.apache.org/jira/browse/QPID-3469
>             Project: Qpid
>          Issue Type: Task
>          Components: Java Broker, Java Broker Derby Store, Java Client
>    Affects Versions: M1, M2, M2.1, M3, M4, 0.5, 0.6, 0.7, 0.8, 0.9, 0.11, 0.12
>            Reporter: Robbie Gemmell
>            Assignee: Robbie Gemmell
>              Labels: derbystore
>             Fix For: 0.13
>         Attachments: JavaJIRAsToClose.pdf
> Previous email to the dev list on the subject:
> date	26 August 2011 18:20
> subject	JIRA clean up for Java components
> Hi all,
> We have an enormous amount of outstanding JIRAs, with around 700 open,
> and close to 400 of these are for the Java client and broker. Many of
> these issues will have been fixed and the JIRA just not updated
> (duplicated?), many will no longer be relevant at all due to years of
> subsequent change, and many could be valid but will never be fixed.
> Regardless, having so many outstanding issues makes it hard to
> actually keep JIRA in check and know what the important issues to look
> at are, or what work is being done in general. We need to seriously
> tidy things up and then keep it tidy going forward.
> To that end, Rob Godfrey and I have both looked through the entire
> list of outstanding issues for the Java client and broker and picked
> out some issues we thought should be retained, leaving some 260 issues
> remaining as things that either appeared to be resolved already or
> should just be closed because it is probable no one will ever look at
> them again. You can find the reduced list at: <see attachments>
> We intend to close these JIRAs out at the end of next week, marking
> them with a new fix-for or tag that will allow them to be found in
> future and restored if need be. I would ask that people look at the
> list and suggest if there is anything you think ought to be retained
> in its current state instead.
> Robbie

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org

View raw message