Outstanding open JIRAs for 0.19/0.20
Hi everyone, I just took a look through the outstanding JIRAs assigned to 0.19/0.20 and cleaned up a bunch of them. There are now only 4 remaining. Could people take a look and update them appropriately, so that we could ship a release without any open JIRAs being assigned to it for once :) See: http://s.apache.org/MXJ9 Robbie
Re: Outstanding open JIRAs
There now remains 5 JIRAs open against released versions. Can the following please have their status updated, either by the assignee or just someone who actually knows their status: Ken: https://issues.apache.org/jira/browse/QPID-3690 Ted: https://issues.apache.org/jira/browse/QPID-3653 Mick: https://issues.apache.org/jira/browse/QPID-3398 Kim: https://issues.apache.org/jira/browse/QPID-3619 Cliff: https://issues.apache.org/jira/browse/QPID-4071 On 12 September 2012 22:55, Robbie Gemmell robbie.gemm...@gmail.com wrote: Thanks to those who updated their JIRAs. Given there were still around 30 sitting open against released versions I have just gone through them all myself and either updated the fix-for or resolved them based on any apparent work done after checking the commit logs (which obviously works best when commits reference the JIRA). There are still a bunch for which the status wasnt clear to me, so can the assignees please look at them and update them accordingly: Ken: https://issues.apache.org/jira/browse/QPID-3690 Ted: https://issues.apache.org/jira/browse/QPID-3653 Mick: https://issues.apache.org/jira/browse/QPID-3398 Kim: https://issues.apache.org/jira/browse/QPID-3619 Andrew: https://issues.apache.org/jira/browse/QPID-3618 Rajith: https://issues.apache.org/jira/browse/QPID-3602 https://issues.apache.org/jira/browse/QPID-3612 https://issues.apache.org/jira/browse/QPID-3613 https://issues.apache.org/jira/browse/QPID-3462 Weston: https://issues.apache.org/jira/browse/QPID-3991 Cliff: https://issues.apache.org/jira/browse/QPID-4071 On 2 September 2012 21:10, Robbie Gemmell robbie.gemm...@gmail.comwrote: So, 6 months and a couple of releases later, we now have 45 open JIRAs assigned to released versions. Can everyone please take a look at JIRAs they have in 0.15 and 0.17 and either resolve them or update the fix-for to remove them from the old versions? Thanks, Robbie On 19 February 2012 23:59, Robbie Gemmell robbie.gemm...@gmail.comwrote: Hi everyone, As you may or may not have noticed from the hundreds of emails I have no doubt generated (I kept some of the traffic off the dev list with bulk changes, but you cant fix some things in bulk without losing data), I have been on some JIRA cleanup sprees both recently and in spots over the last several months. This included resolving completed and/or redundant JIRAs as well as moving obviously incomplete ones to different fix-for versions, archiving some of our ancient versions, and removing a few Components that were either duplicates, obviously-defunct, or the contents of which seemed far better served by identification though use of Labels. One of the things I was aiming to do was clear the released versions of outstanding JIRAs so they dont show up on the front pages as being incomplete, as it was a little ridiculous that we still had things open for released versions going back to 2008. I have now got that number down to a grand total of 2 which I'm not too sure whether to resolve or bump forward, so can their respective owners noted below (or anyone else with a clue) please do so: https://issues.apache.org/jira/browse/QPID-3369 (Alan) https://issues.apache.org/jira/browse/QPID-3079 (Ken) I am sure there is still a vast amount of cruft in JIRA that we can tidy up, there are still almost 500 open issues which seems more a bit much. I dont have anywhere near enough knowledge about many of the non-Java components to judge whether a lot of issues can be closed or not (short of them basically saying 'we will never do this' or 'this is done' and having commits..which, surprisingly, several actually did), so it would be good id those who do could take a look. This sort of thing would be *so* much easier to do if we could get things into a managable state and then keep it there with mere minutes of attention now and then. I'm not done looking at the Java stuff, I'm sure there are still duplicates and invalid things that can be closed and I know there are still several open JIRAs for the Java client that have work done on them that it should be possible to close (Rajith, I'm looking at you sitting with the most assigned open issues in the project :P). Robbie
Re: Outstanding open JIRAs
So, 6 months and a couple of releases later, we now have 45 open JIRAs assigned to released versions. Can everyone please take a look at JIRAs they have in 0.15 and 0.17 and either resolve them or update the fix-for to remove them from the old versions? Thanks, Robbie On 19 February 2012 23:59, Robbie Gemmell robbie.gemm...@gmail.com wrote: Hi everyone, As you may or may not have noticed from the hundreds of emails I have no doubt generated (I kept some of the traffic off the dev list with bulk changes, but you cant fix some things in bulk without losing data), I have been on some JIRA cleanup sprees both recently and in spots over the last several months. This included resolving completed and/or redundant JIRAs as well as moving obviously incomplete ones to different fix-for versions, archiving some of our ancient versions, and removing a few Components that were either duplicates, obviously-defunct, or the contents of which seemed far better served by identification though use of Labels. One of the things I was aiming to do was clear the released versions of outstanding JIRAs so they dont show up on the front pages as being incomplete, as it was a little ridiculous that we still had things open for released versions going back to 2008. I have now got that number down to a grand total of 2 which I'm not too sure whether to resolve or bump forward, so can their respective owners noted below (or anyone else with a clue) please do so: https://issues.apache.org/jira/browse/QPID-3369 (Alan) https://issues.apache.org/jira/browse/QPID-3079 (Ken) I am sure there is still a vast amount of cruft in JIRA that we can tidy up, there are still almost 500 open issues which seems more a bit much. I dont have anywhere near enough knowledge about many of the non-Java components to judge whether a lot of issues can be closed or not (short of them basically saying 'we will never do this' or 'this is done' and having commits..which, surprisingly, several actually did), so it would be good id those who do could take a look. This sort of thing would be *so* much easier to do if we could get things into a managable state and then keep it there with mere minutes of attention now and then. I'm not done looking at the Java stuff, I'm sure there are still duplicates and invalid things that can be closed and I know there are still several open JIRAs for the Java client that have work done on them that it should be possible to close (Rajith, I'm looking at you sitting with the most assigned open issues in the project :P). Robbie
Re: Outstanding open JIRAs
On Sun, Feb 19, 2012 at 6:59 PM, Robbie Gemmell robbie.gemm...@gmail.com wrote: Hi everyone, As you may or may not have noticed from the hundreds of emails I have no doubt generated (I kept some of the traffic off the dev list with bulk changes, but you cant fix some things in bulk without losing data), I have been on some JIRA cleanup sprees both recently and in spots over the last several months. This included resolving completed and/or redundant JIRAs as well as moving obviously incomplete ones to different fix-for versions, archiving some of our ancient versions, and removing a few Components that were either duplicates, obviously-defunct, or the contents of which seemed far better served by identification though use of Labels. One of the things I was aiming to do was clear the released versions of outstanding JIRAs so they dont show up on the front pages as being incomplete, as it was a little ridiculous that we still had things open for released versions going back to 2008. I have now got that number down to a grand total of 2 which I'm not too sure whether to resolve or bump forward, so can their respective owners noted below (or anyone else with a clue) please do so: https://issues.apache.org/jira/browse/QPID-3369 (Alan) https://issues.apache.org/jira/browse/QPID-3079 (Ken) I am sure there is still a vast amount of cruft in JIRA that we can tidy up, there are still almost 500 open issues which seems more a bit much. I dont have anywhere near enough knowledge about many of the non-Java components to judge whether a lot of issues can be closed or not (short of them basically saying 'we will never do this' or 'this is done' and having commits..which, surprisingly, several actually did), so it would be good id those who do could take a look. This sort of thing would be *so* much easier to do if we could get things into a managable state and then keep it there with mere minutes of attention now and then. I'm not done looking at the Java stuff, I'm sure there are still duplicates and invalid things that can be closed and I know there are still several open JIRAs for the Java client that have work done on them that it should be possible to close (Rajith, I'm looking at you sitting with the most assigned open issues in the project :P). That's quite a dubious honour :) Yesterday was a holiday, so trying to do a cleanup today. I've gone through some JIRA's and marked them resolved, will try to work out the rest by today. Rajith Robbie - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Outstanding open JIRAs
On Sun, 2012-02-19 at 23:59 +, Robbie Gemmell wrote: One of the things I was aiming to do was clear the released versions of outstanding JIRAs so they dont show up on the front pages as being incomplete, as it was a little ridiculous that we still had things open for released versions going back to 2008. I have now got that number down to a grand total of 2 which I'm not too sure whether to resolve or bump forward, so can their respective owners noted below (or anyone else with a clue) please do so: https://issues.apache.org/jira/browse/QPID-3369 (Alan) I've pushed that one to Future, it needs a little more investigation. Thanks Robbie for taking the time to clean this up a bit. Cheers, Alan. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Outstanding open JIRAs
Hi Robbie, Thanks for going through these JIRAs, and my apologies for not keeping this up to date. I've pushed this JIRA out to Future, as I believe this issue will be addressed in the upcoming 1.0 effort. -K - Original Message - Hi everyone, As you may or may not have noticed from the hundreds of emails I have no doubt generated (I kept some of the traffic off the dev list with bulk changes, but you cant fix some things in bulk without losing data), I have been on some JIRA cleanup sprees both recently and in spots over the last several months. This included resolving completed and/or redundant JIRAs as well as moving obviously incomplete ones to different fix-for versions, archiving some of our ancient versions, and removing a few Components that were either duplicates, obviously-defunct, or the contents of which seemed far better served by identification though use of Labels. One of the things I was aiming to do was clear the released versions of outstanding JIRAs so they dont show up on the front pages as being incomplete, as it was a little ridiculous that we still had things open for released versions going back to 2008. I have now got that number down to a grand total of 2 which I'm not too sure whether to resolve or bump forward, so can their respective owners noted below (or anyone else with a clue) please do so: https://issues.apache.org/jira/browse/QPID-3369 (Alan) https://issues.apache.org/jira/browse/QPID-3079 (Ken) I am sure there is still a vast amount of cruft in JIRA that we can tidy up, there are still almost 500 open issues which seems more a bit much. I dont have anywhere near enough knowledge about many of the non-Java components to judge whether a lot of issues can be closed or not (short of them basically saying 'we will never do this' or 'this is done' and having commits..which, surprisingly, several actually did), so it would be good id those who do could take a look. This sort of thing would be *so* much easier to do if we could get things into a managable state and then keep it there with mere minutes of attention now and then. I'm not done looking at the Java stuff, I'm sure there are still duplicates and invalid things that can be closed and I know there are still several open JIRAs for the Java client that have work done on them that it should be possible to close (Rajith, I'm looking at you sitting with the most assigned open issues in the project :P). Robbie - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Outstanding open JIRAs
Hi everyone, As you may or may not have noticed from the hundreds of emails I have no doubt generated (I kept some of the traffic off the dev list with bulk changes, but you cant fix some things in bulk without losing data), I have been on some JIRA cleanup sprees both recently and in spots over the last several months. This included resolving completed and/or redundant JIRAs as well as moving obviously incomplete ones to different fix-for versions, archiving some of our ancient versions, and removing a few Components that were either duplicates, obviously-defunct, or the contents of which seemed far better served by identification though use of Labels. One of the things I was aiming to do was clear the released versions of outstanding JIRAs so they dont show up on the front pages as being incomplete, as it was a little ridiculous that we still had things open for released versions going back to 2008. I have now got that number down to a grand total of 2 which I'm not too sure whether to resolve or bump forward, so can their respective owners noted below (or anyone else with a clue) please do so: https://issues.apache.org/jira/browse/QPID-3369 (Alan) https://issues.apache.org/jira/browse/QPID-3079 (Ken) I am sure there is still a vast amount of cruft in JIRA that we can tidy up, there are still almost 500 open issues which seems more a bit much. I dont have anywhere near enough knowledge about many of the non-Java components to judge whether a lot of issues can be closed or not (short of them basically saying 'we will never do this' or 'this is done' and having commits..which, surprisingly, several actually did), so it would be good id those who do could take a look. This sort of thing would be *so* much easier to do if we could get things into a managable state and then keep it there with mere minutes of attention now and then. I'm not done looking at the Java stuff, I'm sure there are still duplicates and invalid things that can be closed and I know there are still several open JIRAs for the Java client that have work done on them that it should be possible to close (Rajith, I'm looking at you sitting with the most assigned open issues in the project :P). Robbie - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
