You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Jason van Zyl <ja...@takari.io> on 2014/01/20 18:23:15 UTC
JIRA Cleanup
Really, it's more about dropping a nuclear bomb on JIRA. While trying to sift through it this weekend it's clear to me it's less than ideal in there.
There are issues that are 12 years old and while there might be some useful information in there that we hand select, I think anything that is older than 5 years we should just close as incomplete because with the great deal of change that's happened with 3.x most of it isn't relevant and if it is, and someone cares that much then it can be reopened with a stand-alone working example of the problem.
Now, as to the requirements for a stand-alone working example I think we should enforce this because personally I'm not going to check out someone's project, figure out how to interpret it in relation to the actual problem in Maven and then create a project I can turn into an IT. I'm just not going to do it generally. There might be exceptions but I don't want to read a textual examples or try to figure out snippets of a production project that can't be shared. In m2e we require a working example project to even look at a problem and if the issue sits there for a year with a working sample project we close it.
Having an issue tracking system with 700 open issues is useless, so I would like to do a mass purge. It shouldn't really get beyond 50 open issues or it's just impossible to manage effectively.
Not sure what anyone else thinks but our JIRA situation is just not effective. I'm thinking anything over 5 years old that isn't assigned to a core developer we just close as incomplete and then see what we're left with. If anyone complains then we point them at doco (I'll write it) about creating a stand-alone project because otherwise it become impossible. I spent 8 hours over the weekend looking at issues trying to interpret what someone was trying to say and I don't want to guess. If the user cares enough they can make an example project.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...
-- Thoreau
Re: JIRA Cleanup
Posted by Daniel Kulp <dk...@apache.org>.
On Jan 20, 2014, at 12:32 PM, Stephen Connolly <st...@gmail.com> wrote:
> If we are going wholesale dumping issues (and I am not against that), I
> have a more radical suggestion... let's just move core to the ASF JIRA...
> with next to no issues needing migration it would be easy ;-)
+1
Good idea.
Dan
>
>
> On 20 January 2014 17:23, Jason van Zyl <ja...@takari.io> wrote:
>
>> Really, it's more about dropping a nuclear bomb on JIRA. While trying to
>> sift through it this weekend it's clear to me it's less than ideal in there.
>>
>> There are issues that are 12 years old and while there might be some
>> useful information in there that we hand select, I think anything that is
>> older than 5 years we should just close as incomplete because with the
>> great deal of change that's happened with 3.x most of it isn't relevant and
>> if it is, and someone cares that much then it can be reopened with a
>> stand-alone working example of the problem.
>>
>> Now, as to the requirements for a stand-alone working example I think we
>> should enforce this because personally I'm not going to check out someone's
>> project, figure out how to interpret it in relation to the actual problem
>> in Maven and then create a project I can turn into an IT. I'm just not
>> going to do it generally. There might be exceptions but I don't want to
>> read a textual examples or try to figure out snippets of a production
>> project that can't be shared. In m2e we require a working example project
>> to even look at a problem and if the issue sits there for a year with a
>> working sample project we close it.
>>
>> Having an issue tracking system with 700 open issues is useless, so I
>> would like to do a mass purge. It shouldn't really get beyond 50 open
>> issues or it's just impossible to manage effectively.
>>
>> Not sure what anyone else thinks but our JIRA situation is just not
>> effective. I'm thinking anything over 5 years old that isn't assigned to a
>> core developer we just close as incomplete and then see what we're left
>> with. If anyone complains then we point them at doco (I'll write it) about
>> creating a stand-alone project because otherwise it become impossible. I
>> spent 8 hours over the weekend looking at issues trying to interpret what
>> someone was trying to say and I don't want to guess. If the user cares
>> enough they can make an example project.
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder, Apache Maven
>> http://twitter.com/jvanzyl
>> ---------------------------------------------------------
>>
>> happiness is like a butterfly: the more you chase it, the more it will
>> elude you, but if you turn your attention to other things, it will come
>> and sit softly on your shoulder ...
>>
>> -- Thoreau
>>
>>
>>
>>
>>
>>
>>
>>
>>
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: JIRA Cleanup
Posted by Michael-O <19...@gmx.net>.
Am 2014-01-20 18:32, schrieb Stephen Connolly:
> If we are going wholesale dumping issues (and I am not against that), I
> have a more radical suggestion... let's just move core to the ASF JIRA...
> with next to no issues needing migration it would be easy ;-)
+1
I head this idea in mind for several months. Make a clean cut. Read
only. Period. New issues in ASF JIRA only. If someone has found an issue
which is already in Codehaus JIRA that should be migrated of course.
> On 20 January 2014 17:23, Jason van Zyl <ja...@takari.io> wrote:
>
>> Really, it's more about dropping a nuclear bomb on JIRA. While trying to
>> sift through it this weekend it's clear to me it's less than ideal in there.
>>
>> There are issues that are 12 years old and while there might be some
>> useful information in there that we hand select, I think anything that is
>> older than 5 years we should just close as incomplete because with the
>> great deal of change that's happened with 3.x most of it isn't relevant and
>> if it is, and someone cares that much then it can be reopened with a
>> stand-alone working example of the problem.
>>
>> Now, as to the requirements for a stand-alone working example I think we
>> should enforce this because personally I'm not going to check out someone's
>> project, figure out how to interpret it in relation to the actual problem
>> in Maven and then create a project I can turn into an IT. I'm just not
>> going to do it generally. There might be exceptions but I don't want to
>> read a textual examples or try to figure out snippets of a production
>> project that can't be shared. In m2e we require a working example project
>> to even look at a problem and if the issue sits there for a year with a
>> working sample project we close it.
>>
>> Having an issue tracking system with 700 open issues is useless, so I
>> would like to do a mass purge. It shouldn't really get beyond 50 open
>> issues or it's just impossible to manage effectively.
>>
>> Not sure what anyone else thinks but our JIRA situation is just not
>> effective. I'm thinking anything over 5 years old that isn't assigned to a
>> core developer we just close as incomplete and then see what we're left
>> with. If anyone complains then we point them at doco (I'll write it) about
>> creating a stand-alone project because otherwise it become impossible. I
>> spent 8 hours over the weekend looking at issues trying to interpret what
>> someone was trying to say and I don't want to guess. If the user cares
>> enough they can make an example project.
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder, Apache Maven
>> http://twitter.com/jvanzyl
>> ---------------------------------------------------------
>>
>> happiness is like a butterfly: the more you chase it, the more it will
>> elude you, but if you turn your attention to other things, it will come
>> and sit softly on your shoulder ...
>>
>> -- Thoreau
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: JIRA Cleanup
Posted by Michael Osipov <mi...@apache.org>.
Am 2014-01-20 18:32, schrieb Stephen Connolly:
> If we are going wholesale dumping issues (and I am not against that), I
> have a more radical suggestion... let's just move core to the ASF JIRA...
> with next to no issues needing migration it would be easy ;-)
+1
I head this idea in mind for several months. Make a clean cut. Read
only. Period. New issues in ASF JIRA only. If someone has found an issue
which is already in Codehaus JIRA that should be migrated of course.
> On 20 January 2014 17:23, Jason van Zyl <ja...@takari.io> wrote:
>
>> Really, it's more about dropping a nuclear bomb on JIRA. While trying to
>> sift through it this weekend it's clear to me it's less than ideal in there.
>>
>> There are issues that are 12 years old and while there might be some
>> useful information in there that we hand select, I think anything that is
>> older than 5 years we should just close as incomplete because with the
>> great deal of change that's happened with 3.x most of it isn't relevant and
>> if it is, and someone cares that much then it can be reopened with a
>> stand-alone working example of the problem.
>>
>> Now, as to the requirements for a stand-alone working example I think we
>> should enforce this because personally I'm not going to check out someone's
>> project, figure out how to interpret it in relation to the actual problem
>> in Maven and then create a project I can turn into an IT. I'm just not
>> going to do it generally. There might be exceptions but I don't want to
>> read a textual examples or try to figure out snippets of a production
>> project that can't be shared. In m2e we require a working example project
>> to even look at a problem and if the issue sits there for a year with a
>> working sample project we close it.
>>
>> Having an issue tracking system with 700 open issues is useless, so I
>> would like to do a mass purge. It shouldn't really get beyond 50 open
>> issues or it's just impossible to manage effectively.
>>
>> Not sure what anyone else thinks but our JIRA situation is just not
>> effective. I'm thinking anything over 5 years old that isn't assigned to a
>> core developer we just close as incomplete and then see what we're left
>> with. If anyone complains then we point them at doco (I'll write it) about
>> creating a stand-alone project because otherwise it become impossible. I
>> spent 8 hours over the weekend looking at issues trying to interpret what
>> someone was trying to say and I don't want to guess. If the user cares
>> enough they can make an example project.
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder, Apache Maven
>> http://twitter.com/jvanzyl
>> ---------------------------------------------------------
>>
>> happiness is like a butterfly: the more you chase it, the more it will
>> elude you, but if you turn your attention to other things, it will come
>> and sit softly on your shoulder ...
>>
>> -- Thoreau
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: JIRA Cleanup
Posted by Jason van Zyl <ja...@takari.io>.
Thanks, I think it's the only sane way to try and help people.
On Jan 23, 2014, at 5:43 PM, Mirko Friedenhagen <mf...@gmail.com> wrote:
> Jason,
>
> the wiki page is a really good writeup and I like the strategy to force
> reporters to create a simple project which will reproduce their issue.
>
> Regards
> Mirko
> --
> Sent from my mobile
> On Jan 23, 2014 3:33 AM, "Jason van Zyl" <ja...@takari.io> wrote:
>
>> I changed the strategy slightly as I thought it might be crappy if the
>> issue was created 5 years ago, but the person updated it 2 months ago. So I
>> took all the issues that have not been updated in the last year and
>> unassigned and closed those out. Got to about the same number and thought
>> this more fair.
>>
>> I referred anyone looking at the comment to
>> https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
>>
>> I'll start sifting through what remains tomorrow.
>>
>> On Jan 22, 2014, at 1:02 PM, Jason van Zyl <ja...@takari.io> wrote:
>>
>>> Yup, it's very straight forward to add a comment to each of the issues
>> that will be closed. When I publish the accompanying documentation I can
>> point the comment at the documentation. Good call.
>>>
>>> On Jan 22, 2014, at 12:16 PM, Jason van Zyl <ja...@takari.io> wrote:
>>>
>>>> Sure, good idea. I assume there's a relatively straight forward way to
>> do that with a bulk operation.
>>>>
>>>> On Jan 22, 2014, at 12:09 PM, Paul Benedict <pb...@apache.org>
>> wrote:
>>>>
>>>>> I advise that we add a comment in each closing issue explaining that
>> it was
>>>>> closed specifically because it's more than 2 years old and to re-open
>> it
>>>>> only if it is still valid. Otherwise, it will look very rude to close a
>>>>> ticket without an explanation.
>>>>>
>>>>> BTW, what I just recommended was done by JBoss Hibernate and Spring
>>>>> Framework when they cleared out their old tickets. It was great to know
>>>>> their reasoning.
>>>>>
>>>>>
>>>>> On Wed, Jan 22, 2014 at 10:59 AM, Jason van Zyl <ja...@takari.io>
>> wrote:
>>>>>
>>>>>> Ok, I'm going to pull the ripcord tonight (8 hours from now).
>>>>>>
>>>>>> On Jan 21, 2014, at 9:19 PM, Jason van Zyl <ja...@takari.io> wrote:
>>>>>>
>>>>>>> So after looking at the issues more closely even at the 5 year-old
>> mark
>>>>>> there are still too many. At the 2 year-old mark it's a bit more
>>>>>> reasonable. If I close all issues older than 2 years-old which are not
>>>>>> assigned thats 415 so we would be left with 220 open issues which
>> after a
>>>>>> week or two I can probably get through, faster with some help. But
>> that's
>>>>>> probably reasonable as more recent issues are pertinent to 3.x as I
>> myself
>>>>>> am probably not going to dig back into 2.x issues and fix them.
>>>>>>>
>>>>>>> So I propose sending a note to the dev and user list stating that
>> we're
>>>>>> trying to get the JIRA issue under control. We're closing all
>> unassigned
>>>>>> issues older than 2 years but people are free to reopen issues for
>> bugs if
>>>>>> they follow a process of providing a working stand-alone example of
>> the
>>>>>> problem.
>>>>>>>
>>>>>>> This will at least start the cleanup process.
>>>>>>>
>>>>>>> How's that sound?
>>>>>>>
>>>>>>> On Jan 20, 2014, at 4:53 PM, Jason van Zyl <ja...@takari.io> wrote:
>>>>>>>
>>>>>>>> Ok, I'll write something up and send it to the user and dev list.
>>>>>>>>
>>>>>>>> On Jan 20, 2014, at 2:17 PM, Benson Margulies <
>> bimargulies@gmail.com>
>>>>>> wrote:
>>>>>>>>
>>>>>>>>> +1 here.
>>>>>>>>>
>>>>>>>>> On Mon, Jan 20, 2014 at 1:12 PM, Anders Hammar <an...@hammar.net>
>>>>>> wrote:
>>>>>>>>>> +1 on clean up if we communicate this (and explain why).
>>>>>>>>>> 0 on move
>>>>>>>>>>
>>>>>>>>>> /Anders
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Mon, Jan 20, 2014 at 6:53 PM, Dominik Bartholdi <
>> domi@fortysix.ch>
>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> +1 cleanup is a really good idea!
>>>>>>>>>>>
>>>>>>>>>>> On 20.01.2014, at 18:50, Arnaud Héritier <ah...@gmail.com>
>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> +1 with a jira cleanup (but documented and announced to users to
>>>>>> let them
>>>>>>>>>>>> understand what we do and why)
>>>>>>>>>>>> +1 to move to ASF
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, Jan 20, 2014 at 6:48 PM, Jason van Zyl <jason@takari.io
>>>
>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Works for me to just start over on the ASF JIRA. There are a
>> couple
>>>>>>>>>>> issues
>>>>>>>>>>>>> I'd move but we can migrate a issues easily. What can't
>> continue
>>>>>> is the
>>>>>>>>>>>>> complete, incomprehensible mess that is there now.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Jan 20, 2014, at 12:32 PM, Stephen Connolly <
>>>>>>>>>>>>> stephen.alan.connolly@gmail.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> If we are going wholesale dumping issues (and I am not against
>>>>>> that), I
>>>>>>>>>>>>>> have a more radical suggestion... let's just move core to the
>> ASF
>>>>>>>>>>> JIRA...
>>>>>>>>>>>>>> with next to no issues needing migration it would be easy ;-)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On 20 January 2014 17:23, Jason van Zyl <ja...@takari.io>
>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Really, it's more about dropping a nuclear bomb on JIRA.
>> While
>>>>>> trying
>>>>>>>>>>> to
>>>>>>>>>>>>>>> sift through it this weekend it's clear to me it's less than
>>>>>> ideal in
>>>>>>>>>>>>> there.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> There are issues that are 12 years old and while there might
>> be
>>>>>> some
>>>>>>>>>>>>>>> useful information in there that we hand select, I think
>>>>>> anything that
>>>>>>>>>>>>> is
>>>>>>>>>>>>>>> older than 5 years we should just close as incomplete because
>>>>>> with the
>>>>>>>>>>>>>>> great deal of change that's happened with 3.x most of it
>> isn't
>>>>>>>>>>> relevant
>>>>>>>>>>>>> and
>>>>>>>>>>>>>>> if it is, and someone cares that much then it can be reopened
>>>>>> with a
>>>>>>>>>>>>>>> stand-alone working example of the problem.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Now, as to the requirements for a stand-alone working
>> example I
>>>>>> think
>>>>>>>>>>> we
>>>>>>>>>>>>>>> should enforce this because personally I'm not going to
>> check out
>>>>>>>>>>>>> someone's
>>>>>>>>>>>>>>> project, figure out how to interpret it in relation to the
>> actual
>>>>>>>>>>>>> problem
>>>>>>>>>>>>>>> in Maven and then create a project I can turn into an IT. I'm
>>>>>> just not
>>>>>>>>>>>>>>> going to do it generally. There might be exceptions but I
>> don't
>>>>>> want
>>>>>>>>>>> to
>>>>>>>>>>>>>>> read a textual examples or try to figure out snippets of a
>>>>>> production
>>>>>>>>>>>>>>> project that can't be shared. In m2e we require a working
>> example
>>>>>>>>>>>>> project
>>>>>>>>>>>>>>> to even look at a problem and if the issue sits there for a
>> year
>>>>>> with
>>>>>>>>>>> a
>>>>>>>>>>>>>>> working sample project we close it.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Having an issue tracking system with 700 open issues is
>> useless,
>>>>>> so I
>>>>>>>>>>>>>>> would like to do a mass purge. It shouldn't really get
>> beyond 50
>>>>>> open
>>>>>>>>>>>>>>> issues or it's just impossible to manage effectively.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Not sure what anyone else thinks but our JIRA situation is
>> just
>>>>>> not
>>>>>>>>>>>>>>> effective. I'm thinking anything over 5 years old that isn't
>>>>>> assigned
>>>>>>>>>>>>> to a
>>>>>>>>>>>>>>> core developer we just close as incomplete and then see what
>>>>>> we're
>>>>>>>>>>> left
>>>>>>>>>>>>>>> with. If anyone complains then we point them at doco (I'll
>> write
>>>>>> it)
>>>>>>>>>>>>> about
>>>>>>>>>>>>>>> creating a stand-alone project because otherwise it become
>>>>>>>>>>> impossible. I
>>>>>>>>>>>>>>> spent 8 hours over the weekend looking at issues trying to
>>>>>> interpret
>>>>>>>>>>>>> what
>>>>>>>>>>>>>>> someone was trying to say and I don't want to guess. If the
>> user
>>>>>> cares
>>>>>>>>>>>>>>> enough they can make an example project.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Jason
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> ----------------------------------------------------------
>>>>>>>>>>>>>>> Jason van Zyl
>>>>>>>>>>>>>>> Founder, Apache Maven
>>>>>>>>>>>>>>> http://twitter.com/jvanzyl
>>>>>>>>>>>>>>> ---------------------------------------------------------
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> happiness is like a butterfly: the more you chase it, the
>> more
>>>>>> it will
>>>>>>>>>>>>>>> elude you, but if you turn your attention to other things, it
>>>>>> will
>>>>>>>>>>> come
>>>>>>>>>>>>>>> and sit softly on your shoulder ...
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> -- Thoreau
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Jason
>>>>>>>>>>>>>
>>>>>>>>>>>>> ----------------------------------------------------------
>>>>>>>>>>>>> Jason van Zyl
>>>>>>>>>>>>> Founder, Apache Maven
>>>>>>>>>>>>> http://twitter.com/jvanzyl
>>>>>>>>>>>>> ---------------------------------------------------------
>>>>>>>>>>>>>
>>>>>>>>>>>>> believe nothing, no matter where you read it,
>>>>>>>>>>>>> or who has said it,
>>>>>>>>>>>>> not even if i have said it,
>>>>>>>>>>>>> unless it agrees with your own reason
>>>>>>>>>>>>> and your own common sense.
>>>>>>>>>>>>>
>>>>>>>>>>>>> -- Buddha
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> -----
>>>>>>>>>>>> Arnaud Héritier
>>>>>>>>>>>> http://aheritier.net
>>>>>>>>>>>> Mail/GTalk: aheritier AT gmail DOT com
>>>>>>>>>>>> Twitter/Skype : aheritier
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>> ---------------------------------------------------------------------
>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>> ---------------------------------------------------------------------
>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>>>
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>>
>>>>>>>> Jason
>>>>>>>>
>>>>>>>> ----------------------------------------------------------
>>>>>>>> Jason van Zyl
>>>>>>>> Founder, Apache Maven
>>>>>>>> http://twitter.com/jvanzyl
>>>>>>>> ---------------------------------------------------------
>>>>>>>>
>>>>>>>> There's no sense in being precise when you don't even know what
>> you're
>>>>>> talking about.
>>>>>>>>
>>>>>>>> -- John von Neumann
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Jason
>>>>>>>
>>>>>>> ----------------------------------------------------------
>>>>>>> Jason van Zyl
>>>>>>> Founder, Apache Maven
>>>>>>> http://twitter.com/jvanzyl
>>>>>>> ---------------------------------------------------------
>>>>>>>
>>>>>>> Script timed out:/Users/jvanzyl/signature/signature.sh
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Jason
>>>>>>
>>>>>> ----------------------------------------------------------
>>>>>> Jason van Zyl
>>>>>> Founder, Apache Maven
>>>>>> http://twitter.com/jvanzyl
>>>>>> ---------------------------------------------------------
>>>>>>
>>>>>> We know what we are, but know not what we may be.
>>>>>>
>>>>>> -- Shakespeare
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Cheers,
>>>>> Paul
>>>>
>>>> Thanks,
>>>>
>>>> Jason
>>>>
>>>> ----------------------------------------------------------
>>>> Jason van Zyl
>>>> Founder, Apache Maven
>>>> http://twitter.com/jvanzyl
>>>> http://twitter.com/takari_io
>>>> ---------------------------------------------------------
>>>>
>>>> People develop abstractions by generalizing from concrete examples.
>>>> Every attempt to determine the correct abstraction on paper without
>>>> actually developing a running system is doomed to failure. No one
>>>> is that smart. A framework is a resuable design, so you develop it by
>>>> looking at the things it is supposed to be a design of. The more
>> examples
>>>> you look at, the more general your framework will be.
>>>>
>>>> -- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>> Thanks,
>>>
>>> Jason
>>>
>>> ----------------------------------------------------------
>>> Jason van Zyl
>>> Founder, Apache Maven
>>> http://twitter.com/jvanzyl
>>> http://twitter.com/takari_io
>>> ---------------------------------------------------------
>>>
>>> A party which is not afraid of letting culture,
>>> business, and welfare go to ruin completely can
>>> be omnipotent for a while.
>>>
>>> -- Jakob Burckhardt
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder, Apache Maven
>> http://twitter.com/jvanzyl
>> http://twitter.com/takari_io
>> ---------------------------------------------------------
>>
>> Simplex sigillum veri. (Simplicity is the seal of truth.)
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
---------------------------------------------------------
To do two things at once is to do neither.
-- Publilius Syrus, Roman slave, first century B.C.
Re: JIRA Cleanup
Posted by Mirko Friedenhagen <mf...@gmail.com>.
Jason,
the wiki page is a really good writeup and I like the strategy to force
reporters to create a simple project which will reproduce their issue.
Regards
Mirko
--
Sent from my mobile
On Jan 23, 2014 3:33 AM, "Jason van Zyl" <ja...@takari.io> wrote:
> I changed the strategy slightly as I thought it might be crappy if the
> issue was created 5 years ago, but the person updated it 2 months ago. So I
> took all the issues that have not been updated in the last year and
> unassigned and closed those out. Got to about the same number and thought
> this more fair.
>
> I referred anyone looking at the comment to
> https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
>
> I'll start sifting through what remains tomorrow.
>
> On Jan 22, 2014, at 1:02 PM, Jason van Zyl <ja...@takari.io> wrote:
>
> > Yup, it's very straight forward to add a comment to each of the issues
> that will be closed. When I publish the accompanying documentation I can
> point the comment at the documentation. Good call.
> >
> > On Jan 22, 2014, at 12:16 PM, Jason van Zyl <ja...@takari.io> wrote:
> >
> >> Sure, good idea. I assume there's a relatively straight forward way to
> do that with a bulk operation.
> >>
> >> On Jan 22, 2014, at 12:09 PM, Paul Benedict <pb...@apache.org>
> wrote:
> >>
> >>> I advise that we add a comment in each closing issue explaining that
> it was
> >>> closed specifically because it's more than 2 years old and to re-open
> it
> >>> only if it is still valid. Otherwise, it will look very rude to close a
> >>> ticket without an explanation.
> >>>
> >>> BTW, what I just recommended was done by JBoss Hibernate and Spring
> >>> Framework when they cleared out their old tickets. It was great to know
> >>> their reasoning.
> >>>
> >>>
> >>> On Wed, Jan 22, 2014 at 10:59 AM, Jason van Zyl <ja...@takari.io>
> wrote:
> >>>
> >>>> Ok, I'm going to pull the ripcord tonight (8 hours from now).
> >>>>
> >>>> On Jan 21, 2014, at 9:19 PM, Jason van Zyl <ja...@takari.io> wrote:
> >>>>
> >>>>> So after looking at the issues more closely even at the 5 year-old
> mark
> >>>> there are still too many. At the 2 year-old mark it's a bit more
> >>>> reasonable. If I close all issues older than 2 years-old which are not
> >>>> assigned thats 415 so we would be left with 220 open issues which
> after a
> >>>> week or two I can probably get through, faster with some help. But
> that's
> >>>> probably reasonable as more recent issues are pertinent to 3.x as I
> myself
> >>>> am probably not going to dig back into 2.x issues and fix them.
> >>>>>
> >>>>> So I propose sending a note to the dev and user list stating that
> we're
> >>>> trying to get the JIRA issue under control. We're closing all
> unassigned
> >>>> issues older than 2 years but people are free to reopen issues for
> bugs if
> >>>> they follow a process of providing a working stand-alone example of
> the
> >>>> problem.
> >>>>>
> >>>>> This will at least start the cleanup process.
> >>>>>
> >>>>> How's that sound?
> >>>>>
> >>>>> On Jan 20, 2014, at 4:53 PM, Jason van Zyl <ja...@takari.io> wrote:
> >>>>>
> >>>>>> Ok, I'll write something up and send it to the user and dev list.
> >>>>>>
> >>>>>> On Jan 20, 2014, at 2:17 PM, Benson Margulies <
> bimargulies@gmail.com>
> >>>> wrote:
> >>>>>>
> >>>>>>> +1 here.
> >>>>>>>
> >>>>>>> On Mon, Jan 20, 2014 at 1:12 PM, Anders Hammar <an...@hammar.net>
> >>>> wrote:
> >>>>>>>> +1 on clean up if we communicate this (and explain why).
> >>>>>>>> 0 on move
> >>>>>>>>
> >>>>>>>> /Anders
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On Mon, Jan 20, 2014 at 6:53 PM, Dominik Bartholdi <
> domi@fortysix.ch>
> >>>> wrote:
> >>>>>>>>
> >>>>>>>>> +1 cleanup is a really good idea!
> >>>>>>>>>
> >>>>>>>>> On 20.01.2014, at 18:50, Arnaud Héritier <ah...@gmail.com>
> >>>> wrote:
> >>>>>>>>>
> >>>>>>>>>> +1 with a jira cleanup (but documented and announced to users to
> >>>> let them
> >>>>>>>>>> understand what we do and why)
> >>>>>>>>>> +1 to move to ASF
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> On Mon, Jan 20, 2014 at 6:48 PM, Jason van Zyl <jason@takari.io
> >
> >>>> wrote:
> >>>>>>>>>>
> >>>>>>>>>>> Works for me to just start over on the ASF JIRA. There are a
> couple
> >>>>>>>>> issues
> >>>>>>>>>>> I'd move but we can migrate a issues easily. What can't
> continue
> >>>> is the
> >>>>>>>>>>> complete, incomprehensible mess that is there now.
> >>>>>>>>>>>
> >>>>>>>>>>> On Jan 20, 2014, at 12:32 PM, Stephen Connolly <
> >>>>>>>>>>> stephen.alan.connolly@gmail.com> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>>> If we are going wholesale dumping issues (and I am not against
> >>>> that), I
> >>>>>>>>>>>> have a more radical suggestion... let's just move core to the
> ASF
> >>>>>>>>> JIRA...
> >>>>>>>>>>>> with next to no issues needing migration it would be easy ;-)
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> On 20 January 2014 17:23, Jason van Zyl <ja...@takari.io>
> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>>> Really, it's more about dropping a nuclear bomb on JIRA.
> While
> >>>> trying
> >>>>>>>>> to
> >>>>>>>>>>>>> sift through it this weekend it's clear to me it's less than
> >>>> ideal in
> >>>>>>>>>>> there.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> There are issues that are 12 years old and while there might
> be
> >>>> some
> >>>>>>>>>>>>> useful information in there that we hand select, I think
> >>>> anything that
> >>>>>>>>>>> is
> >>>>>>>>>>>>> older than 5 years we should just close as incomplete because
> >>>> with the
> >>>>>>>>>>>>> great deal of change that's happened with 3.x most of it
> isn't
> >>>>>>>>> relevant
> >>>>>>>>>>> and
> >>>>>>>>>>>>> if it is, and someone cares that much then it can be reopened
> >>>> with a
> >>>>>>>>>>>>> stand-alone working example of the problem.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Now, as to the requirements for a stand-alone working
> example I
> >>>> think
> >>>>>>>>> we
> >>>>>>>>>>>>> should enforce this because personally I'm not going to
> check out
> >>>>>>>>>>> someone's
> >>>>>>>>>>>>> project, figure out how to interpret it in relation to the
> actual
> >>>>>>>>>>> problem
> >>>>>>>>>>>>> in Maven and then create a project I can turn into an IT. I'm
> >>>> just not
> >>>>>>>>>>>>> going to do it generally. There might be exceptions but I
> don't
> >>>> want
> >>>>>>>>> to
> >>>>>>>>>>>>> read a textual examples or try to figure out snippets of a
> >>>> production
> >>>>>>>>>>>>> project that can't be shared. In m2e we require a working
> example
> >>>>>>>>>>> project
> >>>>>>>>>>>>> to even look at a problem and if the issue sits there for a
> year
> >>>> with
> >>>>>>>>> a
> >>>>>>>>>>>>> working sample project we close it.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Having an issue tracking system with 700 open issues is
> useless,
> >>>> so I
> >>>>>>>>>>>>> would like to do a mass purge. It shouldn't really get
> beyond 50
> >>>> open
> >>>>>>>>>>>>> issues or it's just impossible to manage effectively.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Not sure what anyone else thinks but our JIRA situation is
> just
> >>>> not
> >>>>>>>>>>>>> effective. I'm thinking anything over 5 years old that isn't
> >>>> assigned
> >>>>>>>>>>> to a
> >>>>>>>>>>>>> core developer we just close as incomplete and then see what
> >>>> we're
> >>>>>>>>> left
> >>>>>>>>>>>>> with. If anyone complains then we point them at doco (I'll
> write
> >>>> it)
> >>>>>>>>>>> about
> >>>>>>>>>>>>> creating a stand-alone project because otherwise it become
> >>>>>>>>> impossible. I
> >>>>>>>>>>>>> spent 8 hours over the weekend looking at issues trying to
> >>>> interpret
> >>>>>>>>>>> what
> >>>>>>>>>>>>> someone was trying to say and I don't want to guess. If the
> user
> >>>> cares
> >>>>>>>>>>>>> enough they can make an example project.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Thanks,
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Jason
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> ----------------------------------------------------------
> >>>>>>>>>>>>> Jason van Zyl
> >>>>>>>>>>>>> Founder, Apache Maven
> >>>>>>>>>>>>> http://twitter.com/jvanzyl
> >>>>>>>>>>>>> ---------------------------------------------------------
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> happiness is like a butterfly: the more you chase it, the
> more
> >>>> it will
> >>>>>>>>>>>>> elude you, but if you turn your attention to other things, it
> >>>> will
> >>>>>>>>> come
> >>>>>>>>>>>>> and sit softly on your shoulder ...
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> -- Thoreau
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> Thanks,
> >>>>>>>>>>>
> >>>>>>>>>>> Jason
> >>>>>>>>>>>
> >>>>>>>>>>> ----------------------------------------------------------
> >>>>>>>>>>> Jason van Zyl
> >>>>>>>>>>> Founder, Apache Maven
> >>>>>>>>>>> http://twitter.com/jvanzyl
> >>>>>>>>>>> ---------------------------------------------------------
> >>>>>>>>>>>
> >>>>>>>>>>> believe nothing, no matter where you read it,
> >>>>>>>>>>> or who has said it,
> >>>>>>>>>>> not even if i have said it,
> >>>>>>>>>>> unless it agrees with your own reason
> >>>>>>>>>>> and your own common sense.
> >>>>>>>>>>>
> >>>>>>>>>>> -- Buddha
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> --
> >>>>>>>>>> -----
> >>>>>>>>>> Arnaud Héritier
> >>>>>>>>>> http://aheritier.net
> >>>>>>>>>> Mail/GTalk: aheritier AT gmail DOT com
> >>>>>>>>>> Twitter/Skype : aheritier
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> ---------------------------------------------------------------------
> >>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>
> >>>>>>>
> ---------------------------------------------------------------------
> >>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>>>>
> >>>>>>
> >>>>>> Thanks,
> >>>>>>
> >>>>>> Jason
> >>>>>>
> >>>>>> ----------------------------------------------------------
> >>>>>> Jason van Zyl
> >>>>>> Founder, Apache Maven
> >>>>>> http://twitter.com/jvanzyl
> >>>>>> ---------------------------------------------------------
> >>>>>>
> >>>>>> There's no sense in being precise when you don't even know what
> you're
> >>>> talking about.
> >>>>>>
> >>>>>> -- John von Neumann
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>> Thanks,
> >>>>>
> >>>>> Jason
> >>>>>
> >>>>> ----------------------------------------------------------
> >>>>> Jason van Zyl
> >>>>> Founder, Apache Maven
> >>>>> http://twitter.com/jvanzyl
> >>>>> ---------------------------------------------------------
> >>>>>
> >>>>> Script timed out:/Users/jvanzyl/signature/signature.sh
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>> Thanks,
> >>>>
> >>>> Jason
> >>>>
> >>>> ----------------------------------------------------------
> >>>> Jason van Zyl
> >>>> Founder, Apache Maven
> >>>> http://twitter.com/jvanzyl
> >>>> ---------------------------------------------------------
> >>>>
> >>>> We know what we are, but know not what we may be.
> >>>>
> >>>> -- Shakespeare
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> Cheers,
> >>> Paul
> >>
> >> Thanks,
> >>
> >> Jason
> >>
> >> ----------------------------------------------------------
> >> Jason van Zyl
> >> Founder, Apache Maven
> >> http://twitter.com/jvanzyl
> >> http://twitter.com/takari_io
> >> ---------------------------------------------------------
> >>
> >> People develop abstractions by generalizing from concrete examples.
> >> Every attempt to determine the correct abstraction on paper without
> >> actually developing a running system is doomed to failure. No one
> >> is that smart. A framework is a resuable design, so you develop it by
> >> looking at the things it is supposed to be a design of. The more
> examples
> >> you look at, the more general your framework will be.
> >>
> >> -- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >
> > Thanks,
> >
> > Jason
> >
> > ----------------------------------------------------------
> > Jason van Zyl
> > Founder, Apache Maven
> > http://twitter.com/jvanzyl
> > http://twitter.com/takari_io
> > ---------------------------------------------------------
> >
> > A party which is not afraid of letting culture,
> > business, and welfare go to ruin completely can
> > be omnipotent for a while.
> >
> > -- Jakob Burckhardt
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> http://twitter.com/takari_io
> ---------------------------------------------------------
>
> Simplex sigillum veri. (Simplicity is the seal of truth.)
>
>
>
>
>
>
>
>
>
>
RE: JIRA Cleanup
Posted by "Sievers, Jan" <ja...@sap.com>.
just a thought about going forward (maybe you do that already but thought I'd mention it):
when you create an issue on
https://jira.codehaus.org/browse/MNG
there are 2 JIRA fields "Testcase included" and "Patch Submitted".
a) this should help with filtering for quality bug reports in JIRA and
b) would be good to mention it on [1] or similar that bugs with these 2 attributes will get priority
Regards,
Jan
[1] http://maven.apache.org/issue-tracking.html
-----Original Message-----
From: Jason van Zyl [mailto:jason@takari.io]
Sent: Donnerstag, 23. Januar 2014 03:33
To: Maven Developers List
Subject: Re: JIRA Cleanup
I changed the strategy slightly as I thought it might be crappy if the issue was created 5 years ago, but the person updated it 2 months ago. So I took all the issues that have not been updated in the last year and unassigned and closed those out. Got to about the same number and thought this more fair.
I referred anyone looking at the comment to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
I'll start sifting through what remains tomorrow.
On Jan 22, 2014, at 1:02 PM, Jason van Zyl <ja...@takari.io> wrote:
> Yup, it's very straight forward to add a comment to each of the issues that will be closed. When I publish the accompanying documentation I can point the comment at the documentation. Good call.
>
> On Jan 22, 2014, at 12:16 PM, Jason van Zyl <ja...@takari.io> wrote:
>
>> Sure, good idea. I assume there's a relatively straight forward way to do that with a bulk operation.
>>
>> On Jan 22, 2014, at 12:09 PM, Paul Benedict <pb...@apache.org> wrote:
>>
>>> I advise that we add a comment in each closing issue explaining that it was
>>> closed specifically because it's more than 2 years old and to re-open it
>>> only if it is still valid. Otherwise, it will look very rude to close a
>>> ticket without an explanation.
>>>
>>> BTW, what I just recommended was done by JBoss Hibernate and Spring
>>> Framework when they cleared out their old tickets. It was great to know
>>> their reasoning.
>>>
>>>
>>> On Wed, Jan 22, 2014 at 10:59 AM, Jason van Zyl <ja...@takari.io> wrote:
>>>
>>>> Ok, I'm going to pull the ripcord tonight (8 hours from now).
>>>>
>>>> On Jan 21, 2014, at 9:19 PM, Jason van Zyl <ja...@takari.io> wrote:
>>>>
>>>>> So after looking at the issues more closely even at the 5 year-old mark
>>>> there are still too many. At the 2 year-old mark it's a bit more
>>>> reasonable. If I close all issues older than 2 years-old which are not
>>>> assigned thats 415 so we would be left with 220 open issues which after a
>>>> week or two I can probably get through, faster with some help. But that's
>>>> probably reasonable as more recent issues are pertinent to 3.x as I myself
>>>> am probably not going to dig back into 2.x issues and fix them.
>>>>>
>>>>> So I propose sending a note to the dev and user list stating that we're
>>>> trying to get the JIRA issue under control. We're closing all unassigned
>>>> issues older than 2 years but people are free to reopen issues for bugs if
>>>> they follow a process of providing a working stand-alone example of the
>>>> problem.
>>>>>
>>>>> This will at least start the cleanup process.
>>>>>
>>>>> How's that sound?
>>>>>
>>>>> On Jan 20, 2014, at 4:53 PM, Jason van Zyl <ja...@takari.io> wrote:
>>>>>
>>>>>> Ok, I'll write something up and send it to the user and dev list.
>>>>>>
>>>>>> On Jan 20, 2014, at 2:17 PM, Benson Margulies <bi...@gmail.com>
>>>> wrote:
>>>>>>
>>>>>>> +1 here.
>>>>>>>
>>>>>>> On Mon, Jan 20, 2014 at 1:12 PM, Anders Hammar <an...@hammar.net>
>>>> wrote:
>>>>>>>> +1 on clean up if we communicate this (and explain why).
>>>>>>>> 0 on move
>>>>>>>>
>>>>>>>> /Anders
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Jan 20, 2014 at 6:53 PM, Dominik Bartholdi <do...@fortysix.ch>
>>>> wrote:
>>>>>>>>
>>>>>>>>> +1 cleanup is a really good idea!
>>>>>>>>>
>>>>>>>>> On 20.01.2014, at 18:50, Arnaud Héritier <ah...@gmail.com>
>>>> wrote:
>>>>>>>>>
>>>>>>>>>> +1 with a jira cleanup (but documented and announced to users to
>>>> let them
>>>>>>>>>> understand what we do and why)
>>>>>>>>>> +1 to move to ASF
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Mon, Jan 20, 2014 at 6:48 PM, Jason van Zyl <ja...@takari.io>
>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Works for me to just start over on the ASF JIRA. There are a couple
>>>>>>>>> issues
>>>>>>>>>>> I'd move but we can migrate a issues easily. What can't continue
>>>> is the
>>>>>>>>>>> complete, incomprehensible mess that is there now.
>>>>>>>>>>>
>>>>>>>>>>> On Jan 20, 2014, at 12:32 PM, Stephen Connolly <
>>>>>>>>>>> stephen.alan.connolly@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> If we are going wholesale dumping issues (and I am not against
>>>> that), I
>>>>>>>>>>>> have a more radical suggestion... let's just move core to the ASF
>>>>>>>>> JIRA...
>>>>>>>>>>>> with next to no issues needing migration it would be easy ;-)
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On 20 January 2014 17:23, Jason van Zyl <ja...@takari.io> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Really, it's more about dropping a nuclear bomb on JIRA. While
>>>> trying
>>>>>>>>> to
>>>>>>>>>>>>> sift through it this weekend it's clear to me it's less than
>>>> ideal in
>>>>>>>>>>> there.
>>>>>>>>>>>>>
>>>>>>>>>>>>> There are issues that are 12 years old and while there might be
>>>> some
>>>>>>>>>>>>> useful information in there that we hand select, I think
>>>> anything that
>>>>>>>>>>> is
>>>>>>>>>>>>> older than 5 years we should just close as incomplete because
>>>> with the
>>>>>>>>>>>>> great deal of change that's happened with 3.x most of it isn't
>>>>>>>>> relevant
>>>>>>>>>>> and
>>>>>>>>>>>>> if it is, and someone cares that much then it can be reopened
>>>> with a
>>>>>>>>>>>>> stand-alone working example of the problem.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Now, as to the requirements for a stand-alone working example I
>>>> think
>>>>>>>>> we
>>>>>>>>>>>>> should enforce this because personally I'm not going to check out
>>>>>>>>>>> someone's
>>>>>>>>>>>>> project, figure out how to interpret it in relation to the actual
>>>>>>>>>>> problem
>>>>>>>>>>>>> in Maven and then create a project I can turn into an IT. I'm
>>>> just not
>>>>>>>>>>>>> going to do it generally. There might be exceptions but I don't
>>>> want
>>>>>>>>> to
>>>>>>>>>>>>> read a textual examples or try to figure out snippets of a
>>>> production
>>>>>>>>>>>>> project that can't be shared. In m2e we require a working example
>>>>>>>>>>> project
>>>>>>>>>>>>> to even look at a problem and if the issue sits there for a year
>>>> with
>>>>>>>>> a
>>>>>>>>>>>>> working sample project we close it.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Having an issue tracking system with 700 open issues is useless,
>>>> so I
>>>>>>>>>>>>> would like to do a mass purge. It shouldn't really get beyond 50
>>>> open
>>>>>>>>>>>>> issues or it's just impossible to manage effectively.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Not sure what anyone else thinks but our JIRA situation is just
>>>> not
>>>>>>>>>>>>> effective. I'm thinking anything over 5 years old that isn't
>>>> assigned
>>>>>>>>>>> to a
>>>>>>>>>>>>> core developer we just close as incomplete and then see what
>>>> we're
>>>>>>>>> left
>>>>>>>>>>>>> with. If anyone complains then we point them at doco (I'll write
>>>> it)
>>>>>>>>>>> about
>>>>>>>>>>>>> creating a stand-alone project because otherwise it become
>>>>>>>>> impossible. I
>>>>>>>>>>>>> spent 8 hours over the weekend looking at issues trying to
>>>> interpret
>>>>>>>>>>> what
>>>>>>>>>>>>> someone was trying to say and I don't want to guess. If the user
>>>> cares
>>>>>>>>>>>>> enough they can make an example project.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Jason
>>>>>>>>>>>>>
>>>>>>>>>>>>> ----------------------------------------------------------
>>>>>>>>>>>>> Jason van Zyl
>>>>>>>>>>>>> Founder, Apache Maven
>>>>>>>>>>>>> http://twitter.com/jvanzyl
>>>>>>>>>>>>> ---------------------------------------------------------
>>>>>>>>>>>>>
>>>>>>>>>>>>> happiness is like a butterfly: the more you chase it, the more
>>>> it will
>>>>>>>>>>>>> elude you, but if you turn your attention to other things, it
>>>> will
>>>>>>>>> come
>>>>>>>>>>>>> and sit softly on your shoulder ...
>>>>>>>>>>>>>
>>>>>>>>>>>>> -- Thoreau
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>>
>>>>>>>>>>> Jason
>>>>>>>>>>>
>>>>>>>>>>> ----------------------------------------------------------
>>>>>>>>>>> Jason van Zyl
>>>>>>>>>>> Founder, Apache Maven
>>>>>>>>>>> http://twitter.com/jvanzyl
>>>>>>>>>>> ---------------------------------------------------------
>>>>>>>>>>>
>>>>>>>>>>> believe nothing, no matter where you read it,
>>>>>>>>>>> or who has said it,
>>>>>>>>>>> not even if i have said it,
>>>>>>>>>>> unless it agrees with your own reason
>>>>>>>>>>> and your own common sense.
>>>>>>>>>>>
>>>>>>>>>>> -- Buddha
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> -----
>>>>>>>>>> Arnaud Héritier
>>>>>>>>>> http://aheritier.net
>>>>>>>>>> Mail/GTalk: aheritier AT gmail DOT com
>>>>>>>>>> Twitter/Skype : aheritier
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Jason
>>>>>>
>>>>>> ----------------------------------------------------------
>>>>>> Jason van Zyl
>>>>>> Founder, Apache Maven
>>>>>> http://twitter.com/jvanzyl
>>>>>> ---------------------------------------------------------
>>>>>>
>>>>>> There's no sense in being precise when you don't even know what you're
>>>> talking about.
>>>>>>
>>>>>> -- John von Neumann
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Jason
>>>>>
>>>>> ----------------------------------------------------------
>>>>> Jason van Zyl
>>>>> Founder, Apache Maven
>>>>> http://twitter.com/jvanzyl
>>>>> ---------------------------------------------------------
>>>>>
>>>>> Script timed out:/Users/jvanzyl/signature/signature.sh
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> Thanks,
>>>>
>>>> Jason
>>>>
>>>> ----------------------------------------------------------
>>>> Jason van Zyl
>>>> Founder, Apache Maven
>>>> http://twitter.com/jvanzyl
>>>> ---------------------------------------------------------
>>>>
>>>> We know what we are, but know not what we may be.
>>>>
>>>> -- Shakespeare
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Cheers,
>>> Paul
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder, Apache Maven
>> http://twitter.com/jvanzyl
>> http://twitter.com/takari_io
>> ---------------------------------------------------------
>>
>> People develop abstractions by generalizing from concrete examples.
>> Every attempt to determine the correct abstraction on paper without
>> actually developing a running system is doomed to failure. No one
>> is that smart. A framework is a resuable design, so you develop it by
>> looking at the things it is supposed to be a design of. The more examples
>> you look at, the more general your framework will be.
>>
>> -- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> http://twitter.com/takari_io
> ---------------------------------------------------------
>
> A party which is not afraid of letting culture,
> business, and welfare go to ruin completely can
> be omnipotent for a while.
>
> -- Jakob Burckhardt
>
>
>
>
>
>
>
>
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
---------------------------------------------------------
Simplex sigillum veri. (Simplicity is the seal of truth.)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: JIRA Cleanup
Posted by Jason van Zyl <ja...@takari.io>.
I changed the strategy slightly as I thought it might be crappy if the issue was created 5 years ago, but the person updated it 2 months ago. So I took all the issues that have not been updated in the last year and unassigned and closed those out. Got to about the same number and thought this more fair.
I referred anyone looking at the comment to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
I'll start sifting through what remains tomorrow.
On Jan 22, 2014, at 1:02 PM, Jason van Zyl <ja...@takari.io> wrote:
> Yup, it's very straight forward to add a comment to each of the issues that will be closed. When I publish the accompanying documentation I can point the comment at the documentation. Good call.
>
> On Jan 22, 2014, at 12:16 PM, Jason van Zyl <ja...@takari.io> wrote:
>
>> Sure, good idea. I assume there's a relatively straight forward way to do that with a bulk operation.
>>
>> On Jan 22, 2014, at 12:09 PM, Paul Benedict <pb...@apache.org> wrote:
>>
>>> I advise that we add a comment in each closing issue explaining that it was
>>> closed specifically because it's more than 2 years old and to re-open it
>>> only if it is still valid. Otherwise, it will look very rude to close a
>>> ticket without an explanation.
>>>
>>> BTW, what I just recommended was done by JBoss Hibernate and Spring
>>> Framework when they cleared out their old tickets. It was great to know
>>> their reasoning.
>>>
>>>
>>> On Wed, Jan 22, 2014 at 10:59 AM, Jason van Zyl <ja...@takari.io> wrote:
>>>
>>>> Ok, I'm going to pull the ripcord tonight (8 hours from now).
>>>>
>>>> On Jan 21, 2014, at 9:19 PM, Jason van Zyl <ja...@takari.io> wrote:
>>>>
>>>>> So after looking at the issues more closely even at the 5 year-old mark
>>>> there are still too many. At the 2 year-old mark it's a bit more
>>>> reasonable. If I close all issues older than 2 years-old which are not
>>>> assigned thats 415 so we would be left with 220 open issues which after a
>>>> week or two I can probably get through, faster with some help. But that's
>>>> probably reasonable as more recent issues are pertinent to 3.x as I myself
>>>> am probably not going to dig back into 2.x issues and fix them.
>>>>>
>>>>> So I propose sending a note to the dev and user list stating that we're
>>>> trying to get the JIRA issue under control. We're closing all unassigned
>>>> issues older than 2 years but people are free to reopen issues for bugs if
>>>> they follow a process of providing a working stand-alone example of the
>>>> problem.
>>>>>
>>>>> This will at least start the cleanup process.
>>>>>
>>>>> How's that sound?
>>>>>
>>>>> On Jan 20, 2014, at 4:53 PM, Jason van Zyl <ja...@takari.io> wrote:
>>>>>
>>>>>> Ok, I'll write something up and send it to the user and dev list.
>>>>>>
>>>>>> On Jan 20, 2014, at 2:17 PM, Benson Margulies <bi...@gmail.com>
>>>> wrote:
>>>>>>
>>>>>>> +1 here.
>>>>>>>
>>>>>>> On Mon, Jan 20, 2014 at 1:12 PM, Anders Hammar <an...@hammar.net>
>>>> wrote:
>>>>>>>> +1 on clean up if we communicate this (and explain why).
>>>>>>>> 0 on move
>>>>>>>>
>>>>>>>> /Anders
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Jan 20, 2014 at 6:53 PM, Dominik Bartholdi <do...@fortysix.ch>
>>>> wrote:
>>>>>>>>
>>>>>>>>> +1 cleanup is a really good idea!
>>>>>>>>>
>>>>>>>>> On 20.01.2014, at 18:50, Arnaud Héritier <ah...@gmail.com>
>>>> wrote:
>>>>>>>>>
>>>>>>>>>> +1 with a jira cleanup (but documented and announced to users to
>>>> let them
>>>>>>>>>> understand what we do and why)
>>>>>>>>>> +1 to move to ASF
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Mon, Jan 20, 2014 at 6:48 PM, Jason van Zyl <ja...@takari.io>
>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Works for me to just start over on the ASF JIRA. There are a couple
>>>>>>>>> issues
>>>>>>>>>>> I'd move but we can migrate a issues easily. What can't continue
>>>> is the
>>>>>>>>>>> complete, incomprehensible mess that is there now.
>>>>>>>>>>>
>>>>>>>>>>> On Jan 20, 2014, at 12:32 PM, Stephen Connolly <
>>>>>>>>>>> stephen.alan.connolly@gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> If we are going wholesale dumping issues (and I am not against
>>>> that), I
>>>>>>>>>>>> have a more radical suggestion... let's just move core to the ASF
>>>>>>>>> JIRA...
>>>>>>>>>>>> with next to no issues needing migration it would be easy ;-)
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On 20 January 2014 17:23, Jason van Zyl <ja...@takari.io> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Really, it's more about dropping a nuclear bomb on JIRA. While
>>>> trying
>>>>>>>>> to
>>>>>>>>>>>>> sift through it this weekend it's clear to me it's less than
>>>> ideal in
>>>>>>>>>>> there.
>>>>>>>>>>>>>
>>>>>>>>>>>>> There are issues that are 12 years old and while there might be
>>>> some
>>>>>>>>>>>>> useful information in there that we hand select, I think
>>>> anything that
>>>>>>>>>>> is
>>>>>>>>>>>>> older than 5 years we should just close as incomplete because
>>>> with the
>>>>>>>>>>>>> great deal of change that's happened with 3.x most of it isn't
>>>>>>>>> relevant
>>>>>>>>>>> and
>>>>>>>>>>>>> if it is, and someone cares that much then it can be reopened
>>>> with a
>>>>>>>>>>>>> stand-alone working example of the problem.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Now, as to the requirements for a stand-alone working example I
>>>> think
>>>>>>>>> we
>>>>>>>>>>>>> should enforce this because personally I'm not going to check out
>>>>>>>>>>> someone's
>>>>>>>>>>>>> project, figure out how to interpret it in relation to the actual
>>>>>>>>>>> problem
>>>>>>>>>>>>> in Maven and then create a project I can turn into an IT. I'm
>>>> just not
>>>>>>>>>>>>> going to do it generally. There might be exceptions but I don't
>>>> want
>>>>>>>>> to
>>>>>>>>>>>>> read a textual examples or try to figure out snippets of a
>>>> production
>>>>>>>>>>>>> project that can't be shared. In m2e we require a working example
>>>>>>>>>>> project
>>>>>>>>>>>>> to even look at a problem and if the issue sits there for a year
>>>> with
>>>>>>>>> a
>>>>>>>>>>>>> working sample project we close it.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Having an issue tracking system with 700 open issues is useless,
>>>> so I
>>>>>>>>>>>>> would like to do a mass purge. It shouldn't really get beyond 50
>>>> open
>>>>>>>>>>>>> issues or it's just impossible to manage effectively.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Not sure what anyone else thinks but our JIRA situation is just
>>>> not
>>>>>>>>>>>>> effective. I'm thinking anything over 5 years old that isn't
>>>> assigned
>>>>>>>>>>> to a
>>>>>>>>>>>>> core developer we just close as incomplete and then see what
>>>> we're
>>>>>>>>> left
>>>>>>>>>>>>> with. If anyone complains then we point them at doco (I'll write
>>>> it)
>>>>>>>>>>> about
>>>>>>>>>>>>> creating a stand-alone project because otherwise it become
>>>>>>>>> impossible. I
>>>>>>>>>>>>> spent 8 hours over the weekend looking at issues trying to
>>>> interpret
>>>>>>>>>>> what
>>>>>>>>>>>>> someone was trying to say and I don't want to guess. If the user
>>>> cares
>>>>>>>>>>>>> enough they can make an example project.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Jason
>>>>>>>>>>>>>
>>>>>>>>>>>>> ----------------------------------------------------------
>>>>>>>>>>>>> Jason van Zyl
>>>>>>>>>>>>> Founder, Apache Maven
>>>>>>>>>>>>> http://twitter.com/jvanzyl
>>>>>>>>>>>>> ---------------------------------------------------------
>>>>>>>>>>>>>
>>>>>>>>>>>>> happiness is like a butterfly: the more you chase it, the more
>>>> it will
>>>>>>>>>>>>> elude you, but if you turn your attention to other things, it
>>>> will
>>>>>>>>> come
>>>>>>>>>>>>> and sit softly on your shoulder ...
>>>>>>>>>>>>>
>>>>>>>>>>>>> -- Thoreau
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>>
>>>>>>>>>>> Jason
>>>>>>>>>>>
>>>>>>>>>>> ----------------------------------------------------------
>>>>>>>>>>> Jason van Zyl
>>>>>>>>>>> Founder, Apache Maven
>>>>>>>>>>> http://twitter.com/jvanzyl
>>>>>>>>>>> ---------------------------------------------------------
>>>>>>>>>>>
>>>>>>>>>>> believe nothing, no matter where you read it,
>>>>>>>>>>> or who has said it,
>>>>>>>>>>> not even if i have said it,
>>>>>>>>>>> unless it agrees with your own reason
>>>>>>>>>>> and your own common sense.
>>>>>>>>>>>
>>>>>>>>>>> -- Buddha
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> -----
>>>>>>>>>> Arnaud Héritier
>>>>>>>>>> http://aheritier.net
>>>>>>>>>> Mail/GTalk: aheritier AT gmail DOT com
>>>>>>>>>> Twitter/Skype : aheritier
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Jason
>>>>>>
>>>>>> ----------------------------------------------------------
>>>>>> Jason van Zyl
>>>>>> Founder, Apache Maven
>>>>>> http://twitter.com/jvanzyl
>>>>>> ---------------------------------------------------------
>>>>>>
>>>>>> There's no sense in being precise when you don't even know what you're
>>>> talking about.
>>>>>>
>>>>>> -- John von Neumann
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Jason
>>>>>
>>>>> ----------------------------------------------------------
>>>>> Jason van Zyl
>>>>> Founder, Apache Maven
>>>>> http://twitter.com/jvanzyl
>>>>> ---------------------------------------------------------
>>>>>
>>>>> Script timed out:/Users/jvanzyl/signature/signature.sh
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> Thanks,
>>>>
>>>> Jason
>>>>
>>>> ----------------------------------------------------------
>>>> Jason van Zyl
>>>> Founder, Apache Maven
>>>> http://twitter.com/jvanzyl
>>>> ---------------------------------------------------------
>>>>
>>>> We know what we are, but know not what we may be.
>>>>
>>>> -- Shakespeare
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Cheers,
>>> Paul
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder, Apache Maven
>> http://twitter.com/jvanzyl
>> http://twitter.com/takari_io
>> ---------------------------------------------------------
>>
>> People develop abstractions by generalizing from concrete examples.
>> Every attempt to determine the correct abstraction on paper without
>> actually developing a running system is doomed to failure. No one
>> is that smart. A framework is a resuable design, so you develop it by
>> looking at the things it is supposed to be a design of. The more examples
>> you look at, the more general your framework will be.
>>
>> -- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> http://twitter.com/takari_io
> ---------------------------------------------------------
>
> A party which is not afraid of letting culture,
> business, and welfare go to ruin completely can
> be omnipotent for a while.
>
> -- Jakob Burckhardt
>
>
>
>
>
>
>
>
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
---------------------------------------------------------
Simplex sigillum veri. (Simplicity is the seal of truth.)
Re: JIRA Cleanup
Posted by Jason van Zyl <ja...@takari.io>.
Yup, it's very straight forward to add a comment to each of the issues that will be closed. When I publish the accompanying documentation I can point the comment at the documentation. Good call.
On Jan 22, 2014, at 12:16 PM, Jason van Zyl <ja...@takari.io> wrote:
> Sure, good idea. I assume there's a relatively straight forward way to do that with a bulk operation.
>
> On Jan 22, 2014, at 12:09 PM, Paul Benedict <pb...@apache.org> wrote:
>
>> I advise that we add a comment in each closing issue explaining that it was
>> closed specifically because it's more than 2 years old and to re-open it
>> only if it is still valid. Otherwise, it will look very rude to close a
>> ticket without an explanation.
>>
>> BTW, what I just recommended was done by JBoss Hibernate and Spring
>> Framework when they cleared out their old tickets. It was great to know
>> their reasoning.
>>
>>
>> On Wed, Jan 22, 2014 at 10:59 AM, Jason van Zyl <ja...@takari.io> wrote:
>>
>>> Ok, I'm going to pull the ripcord tonight (8 hours from now).
>>>
>>> On Jan 21, 2014, at 9:19 PM, Jason van Zyl <ja...@takari.io> wrote:
>>>
>>>> So after looking at the issues more closely even at the 5 year-old mark
>>> there are still too many. At the 2 year-old mark it's a bit more
>>> reasonable. If I close all issues older than 2 years-old which are not
>>> assigned thats 415 so we would be left with 220 open issues which after a
>>> week or two I can probably get through, faster with some help. But that's
>>> probably reasonable as more recent issues are pertinent to 3.x as I myself
>>> am probably not going to dig back into 2.x issues and fix them.
>>>>
>>>> So I propose sending a note to the dev and user list stating that we're
>>> trying to get the JIRA issue under control. We're closing all unassigned
>>> issues older than 2 years but people are free to reopen issues for bugs if
>>> they follow a process of providing a working stand-alone example of the
>>> problem.
>>>>
>>>> This will at least start the cleanup process.
>>>>
>>>> How's that sound?
>>>>
>>>> On Jan 20, 2014, at 4:53 PM, Jason van Zyl <ja...@takari.io> wrote:
>>>>
>>>>> Ok, I'll write something up and send it to the user and dev list.
>>>>>
>>>>> On Jan 20, 2014, at 2:17 PM, Benson Margulies <bi...@gmail.com>
>>> wrote:
>>>>>
>>>>>> +1 here.
>>>>>>
>>>>>> On Mon, Jan 20, 2014 at 1:12 PM, Anders Hammar <an...@hammar.net>
>>> wrote:
>>>>>>> +1 on clean up if we communicate this (and explain why).
>>>>>>> 0 on move
>>>>>>>
>>>>>>> /Anders
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Jan 20, 2014 at 6:53 PM, Dominik Bartholdi <do...@fortysix.ch>
>>> wrote:
>>>>>>>
>>>>>>>> +1 cleanup is a really good idea!
>>>>>>>>
>>>>>>>> On 20.01.2014, at 18:50, Arnaud Héritier <ah...@gmail.com>
>>> wrote:
>>>>>>>>
>>>>>>>>> +1 with a jira cleanup (but documented and announced to users to
>>> let them
>>>>>>>>> understand what we do and why)
>>>>>>>>> +1 to move to ASF
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Mon, Jan 20, 2014 at 6:48 PM, Jason van Zyl <ja...@takari.io>
>>> wrote:
>>>>>>>>>
>>>>>>>>>> Works for me to just start over on the ASF JIRA. There are a couple
>>>>>>>> issues
>>>>>>>>>> I'd move but we can migrate a issues easily. What can't continue
>>> is the
>>>>>>>>>> complete, incomprehensible mess that is there now.
>>>>>>>>>>
>>>>>>>>>> On Jan 20, 2014, at 12:32 PM, Stephen Connolly <
>>>>>>>>>> stephen.alan.connolly@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> If we are going wholesale dumping issues (and I am not against
>>> that), I
>>>>>>>>>>> have a more radical suggestion... let's just move core to the ASF
>>>>>>>> JIRA...
>>>>>>>>>>> with next to no issues needing migration it would be easy ;-)
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On 20 January 2014 17:23, Jason van Zyl <ja...@takari.io> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Really, it's more about dropping a nuclear bomb on JIRA. While
>>> trying
>>>>>>>> to
>>>>>>>>>>>> sift through it this weekend it's clear to me it's less than
>>> ideal in
>>>>>>>>>> there.
>>>>>>>>>>>>
>>>>>>>>>>>> There are issues that are 12 years old and while there might be
>>> some
>>>>>>>>>>>> useful information in there that we hand select, I think
>>> anything that
>>>>>>>>>> is
>>>>>>>>>>>> older than 5 years we should just close as incomplete because
>>> with the
>>>>>>>>>>>> great deal of change that's happened with 3.x most of it isn't
>>>>>>>> relevant
>>>>>>>>>> and
>>>>>>>>>>>> if it is, and someone cares that much then it can be reopened
>>> with a
>>>>>>>>>>>> stand-alone working example of the problem.
>>>>>>>>>>>>
>>>>>>>>>>>> Now, as to the requirements for a stand-alone working example I
>>> think
>>>>>>>> we
>>>>>>>>>>>> should enforce this because personally I'm not going to check out
>>>>>>>>>> someone's
>>>>>>>>>>>> project, figure out how to interpret it in relation to the actual
>>>>>>>>>> problem
>>>>>>>>>>>> in Maven and then create a project I can turn into an IT. I'm
>>> just not
>>>>>>>>>>>> going to do it generally. There might be exceptions but I don't
>>> want
>>>>>>>> to
>>>>>>>>>>>> read a textual examples or try to figure out snippets of a
>>> production
>>>>>>>>>>>> project that can't be shared. In m2e we require a working example
>>>>>>>>>> project
>>>>>>>>>>>> to even look at a problem and if the issue sits there for a year
>>> with
>>>>>>>> a
>>>>>>>>>>>> working sample project we close it.
>>>>>>>>>>>>
>>>>>>>>>>>> Having an issue tracking system with 700 open issues is useless,
>>> so I
>>>>>>>>>>>> would like to do a mass purge. It shouldn't really get beyond 50
>>> open
>>>>>>>>>>>> issues or it's just impossible to manage effectively.
>>>>>>>>>>>>
>>>>>>>>>>>> Not sure what anyone else thinks but our JIRA situation is just
>>> not
>>>>>>>>>>>> effective. I'm thinking anything over 5 years old that isn't
>>> assigned
>>>>>>>>>> to a
>>>>>>>>>>>> core developer we just close as incomplete and then see what
>>> we're
>>>>>>>> left
>>>>>>>>>>>> with. If anyone complains then we point them at doco (I'll write
>>> it)
>>>>>>>>>> about
>>>>>>>>>>>> creating a stand-alone project because otherwise it become
>>>>>>>> impossible. I
>>>>>>>>>>>> spent 8 hours over the weekend looking at issues trying to
>>> interpret
>>>>>>>>>> what
>>>>>>>>>>>> someone was trying to say and I don't want to guess. If the user
>>> cares
>>>>>>>>>>>> enough they can make an example project.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>
>>>>>>>>>>>> Jason
>>>>>>>>>>>>
>>>>>>>>>>>> ----------------------------------------------------------
>>>>>>>>>>>> Jason van Zyl
>>>>>>>>>>>> Founder, Apache Maven
>>>>>>>>>>>> http://twitter.com/jvanzyl
>>>>>>>>>>>> ---------------------------------------------------------
>>>>>>>>>>>>
>>>>>>>>>>>> happiness is like a butterfly: the more you chase it, the more
>>> it will
>>>>>>>>>>>> elude you, but if you turn your attention to other things, it
>>> will
>>>>>>>> come
>>>>>>>>>>>> and sit softly on your shoulder ...
>>>>>>>>>>>>
>>>>>>>>>>>> -- Thoreau
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>>
>>>>>>>>>> Jason
>>>>>>>>>>
>>>>>>>>>> ----------------------------------------------------------
>>>>>>>>>> Jason van Zyl
>>>>>>>>>> Founder, Apache Maven
>>>>>>>>>> http://twitter.com/jvanzyl
>>>>>>>>>> ---------------------------------------------------------
>>>>>>>>>>
>>>>>>>>>> believe nothing, no matter where you read it,
>>>>>>>>>> or who has said it,
>>>>>>>>>> not even if i have said it,
>>>>>>>>>> unless it agrees with your own reason
>>>>>>>>>> and your own common sense.
>>>>>>>>>>
>>>>>>>>>> -- Buddha
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> -----
>>>>>>>>> Arnaud Héritier
>>>>>>>>> http://aheritier.net
>>>>>>>>> Mail/GTalk: aheritier AT gmail DOT com
>>>>>>>>> Twitter/Skype : aheritier
>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Jason
>>>>>
>>>>> ----------------------------------------------------------
>>>>> Jason van Zyl
>>>>> Founder, Apache Maven
>>>>> http://twitter.com/jvanzyl
>>>>> ---------------------------------------------------------
>>>>>
>>>>> There's no sense in being precise when you don't even know what you're
>>> talking about.
>>>>>
>>>>> -- John von Neumann
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> Thanks,
>>>>
>>>> Jason
>>>>
>>>> ----------------------------------------------------------
>>>> Jason van Zyl
>>>> Founder, Apache Maven
>>>> http://twitter.com/jvanzyl
>>>> ---------------------------------------------------------
>>>>
>>>> Script timed out:/Users/jvanzyl/signature/signature.sh
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>> Thanks,
>>>
>>> Jason
>>>
>>> ----------------------------------------------------------
>>> Jason van Zyl
>>> Founder, Apache Maven
>>> http://twitter.com/jvanzyl
>>> ---------------------------------------------------------
>>>
>>> We know what we are, but know not what we may be.
>>>
>>> -- Shakespeare
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>> --
>> Cheers,
>> Paul
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> http://twitter.com/takari_io
> ---------------------------------------------------------
>
> People develop abstractions by generalizing from concrete examples.
> Every attempt to determine the correct abstraction on paper without
> actually developing a running system is doomed to failure. No one
> is that smart. A framework is a resuable design, so you develop it by
> looking at the things it is supposed to be a design of. The more examples
> you look at, the more general your framework will be.
>
> -- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks
>
>
>
>
>
>
>
>
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
---------------------------------------------------------
A party which is not afraid of letting culture,
business, and welfare go to ruin completely can
be omnipotent for a while.
-- Jakob Burckhardt
Re: JIRA Cleanup
Posted by Jason van Zyl <ja...@takari.io>.
Sure, good idea. I assume there's a relatively straight forward way to do that with a bulk operation.
On Jan 22, 2014, at 12:09 PM, Paul Benedict <pb...@apache.org> wrote:
> I advise that we add a comment in each closing issue explaining that it was
> closed specifically because it's more than 2 years old and to re-open it
> only if it is still valid. Otherwise, it will look very rude to close a
> ticket without an explanation.
>
> BTW, what I just recommended was done by JBoss Hibernate and Spring
> Framework when they cleared out their old tickets. It was great to know
> their reasoning.
>
>
> On Wed, Jan 22, 2014 at 10:59 AM, Jason van Zyl <ja...@takari.io> wrote:
>
>> Ok, I'm going to pull the ripcord tonight (8 hours from now).
>>
>> On Jan 21, 2014, at 9:19 PM, Jason van Zyl <ja...@takari.io> wrote:
>>
>>> So after looking at the issues more closely even at the 5 year-old mark
>> there are still too many. At the 2 year-old mark it's a bit more
>> reasonable. If I close all issues older than 2 years-old which are not
>> assigned thats 415 so we would be left with 220 open issues which after a
>> week or two I can probably get through, faster with some help. But that's
>> probably reasonable as more recent issues are pertinent to 3.x as I myself
>> am probably not going to dig back into 2.x issues and fix them.
>>>
>>> So I propose sending a note to the dev and user list stating that we're
>> trying to get the JIRA issue under control. We're closing all unassigned
>> issues older than 2 years but people are free to reopen issues for bugs if
>> they follow a process of providing a working stand-alone example of the
>> problem.
>>>
>>> This will at least start the cleanup process.
>>>
>>> How's that sound?
>>>
>>> On Jan 20, 2014, at 4:53 PM, Jason van Zyl <ja...@takari.io> wrote:
>>>
>>>> Ok, I'll write something up and send it to the user and dev list.
>>>>
>>>> On Jan 20, 2014, at 2:17 PM, Benson Margulies <bi...@gmail.com>
>> wrote:
>>>>
>>>>> +1 here.
>>>>>
>>>>> On Mon, Jan 20, 2014 at 1:12 PM, Anders Hammar <an...@hammar.net>
>> wrote:
>>>>>> +1 on clean up if we communicate this (and explain why).
>>>>>> 0 on move
>>>>>>
>>>>>> /Anders
>>>>>>
>>>>>>
>>>>>> On Mon, Jan 20, 2014 at 6:53 PM, Dominik Bartholdi <do...@fortysix.ch>
>> wrote:
>>>>>>
>>>>>>> +1 cleanup is a really good idea!
>>>>>>>
>>>>>>> On 20.01.2014, at 18:50, Arnaud Héritier <ah...@gmail.com>
>> wrote:
>>>>>>>
>>>>>>>> +1 with a jira cleanup (but documented and announced to users to
>> let them
>>>>>>>> understand what we do and why)
>>>>>>>> +1 to move to ASF
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Jan 20, 2014 at 6:48 PM, Jason van Zyl <ja...@takari.io>
>> wrote:
>>>>>>>>
>>>>>>>>> Works for me to just start over on the ASF JIRA. There are a couple
>>>>>>> issues
>>>>>>>>> I'd move but we can migrate a issues easily. What can't continue
>> is the
>>>>>>>>> complete, incomprehensible mess that is there now.
>>>>>>>>>
>>>>>>>>> On Jan 20, 2014, at 12:32 PM, Stephen Connolly <
>>>>>>>>> stephen.alan.connolly@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> If we are going wholesale dumping issues (and I am not against
>> that), I
>>>>>>>>>> have a more radical suggestion... let's just move core to the ASF
>>>>>>> JIRA...
>>>>>>>>>> with next to no issues needing migration it would be easy ;-)
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 20 January 2014 17:23, Jason van Zyl <ja...@takari.io> wrote:
>>>>>>>>>>
>>>>>>>>>>> Really, it's more about dropping a nuclear bomb on JIRA. While
>> trying
>>>>>>> to
>>>>>>>>>>> sift through it this weekend it's clear to me it's less than
>> ideal in
>>>>>>>>> there.
>>>>>>>>>>>
>>>>>>>>>>> There are issues that are 12 years old and while there might be
>> some
>>>>>>>>>>> useful information in there that we hand select, I think
>> anything that
>>>>>>>>> is
>>>>>>>>>>> older than 5 years we should just close as incomplete because
>> with the
>>>>>>>>>>> great deal of change that's happened with 3.x most of it isn't
>>>>>>> relevant
>>>>>>>>> and
>>>>>>>>>>> if it is, and someone cares that much then it can be reopened
>> with a
>>>>>>>>>>> stand-alone working example of the problem.
>>>>>>>>>>>
>>>>>>>>>>> Now, as to the requirements for a stand-alone working example I
>> think
>>>>>>> we
>>>>>>>>>>> should enforce this because personally I'm not going to check out
>>>>>>>>> someone's
>>>>>>>>>>> project, figure out how to interpret it in relation to the actual
>>>>>>>>> problem
>>>>>>>>>>> in Maven and then create a project I can turn into an IT. I'm
>> just not
>>>>>>>>>>> going to do it generally. There might be exceptions but I don't
>> want
>>>>>>> to
>>>>>>>>>>> read a textual examples or try to figure out snippets of a
>> production
>>>>>>>>>>> project that can't be shared. In m2e we require a working example
>>>>>>>>> project
>>>>>>>>>>> to even look at a problem and if the issue sits there for a year
>> with
>>>>>>> a
>>>>>>>>>>> working sample project we close it.
>>>>>>>>>>>
>>>>>>>>>>> Having an issue tracking system with 700 open issues is useless,
>> so I
>>>>>>>>>>> would like to do a mass purge. It shouldn't really get beyond 50
>> open
>>>>>>>>>>> issues or it's just impossible to manage effectively.
>>>>>>>>>>>
>>>>>>>>>>> Not sure what anyone else thinks but our JIRA situation is just
>> not
>>>>>>>>>>> effective. I'm thinking anything over 5 years old that isn't
>> assigned
>>>>>>>>> to a
>>>>>>>>>>> core developer we just close as incomplete and then see what
>> we're
>>>>>>> left
>>>>>>>>>>> with. If anyone complains then we point them at doco (I'll write
>> it)
>>>>>>>>> about
>>>>>>>>>>> creating a stand-alone project because otherwise it become
>>>>>>> impossible. I
>>>>>>>>>>> spent 8 hours over the weekend looking at issues trying to
>> interpret
>>>>>>>>> what
>>>>>>>>>>> someone was trying to say and I don't want to guess. If the user
>> cares
>>>>>>>>>>> enough they can make an example project.
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>>
>>>>>>>>>>> Jason
>>>>>>>>>>>
>>>>>>>>>>> ----------------------------------------------------------
>>>>>>>>>>> Jason van Zyl
>>>>>>>>>>> Founder, Apache Maven
>>>>>>>>>>> http://twitter.com/jvanzyl
>>>>>>>>>>> ---------------------------------------------------------
>>>>>>>>>>>
>>>>>>>>>>> happiness is like a butterfly: the more you chase it, the more
>> it will
>>>>>>>>>>> elude you, but if you turn your attention to other things, it
>> will
>>>>>>> come
>>>>>>>>>>> and sit softly on your shoulder ...
>>>>>>>>>>>
>>>>>>>>>>> -- Thoreau
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>>
>>>>>>>>> Jason
>>>>>>>>>
>>>>>>>>> ----------------------------------------------------------
>>>>>>>>> Jason van Zyl
>>>>>>>>> Founder, Apache Maven
>>>>>>>>> http://twitter.com/jvanzyl
>>>>>>>>> ---------------------------------------------------------
>>>>>>>>>
>>>>>>>>> believe nothing, no matter where you read it,
>>>>>>>>> or who has said it,
>>>>>>>>> not even if i have said it,
>>>>>>>>> unless it agrees with your own reason
>>>>>>>>> and your own common sense.
>>>>>>>>>
>>>>>>>>> -- Buddha
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> -----
>>>>>>>> Arnaud Héritier
>>>>>>>> http://aheritier.net
>>>>>>>> Mail/GTalk: aheritier AT gmail DOT com
>>>>>>>> Twitter/Skype : aheritier
>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>
>>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>
>>>>
>>>> Thanks,
>>>>
>>>> Jason
>>>>
>>>> ----------------------------------------------------------
>>>> Jason van Zyl
>>>> Founder, Apache Maven
>>>> http://twitter.com/jvanzyl
>>>> ---------------------------------------------------------
>>>>
>>>> There's no sense in being precise when you don't even know what you're
>> talking about.
>>>>
>>>> -- John von Neumann
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>> Thanks,
>>>
>>> Jason
>>>
>>> ----------------------------------------------------------
>>> Jason van Zyl
>>> Founder, Apache Maven
>>> http://twitter.com/jvanzyl
>>> ---------------------------------------------------------
>>>
>>> Script timed out:/Users/jvanzyl/signature/signature.sh
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder, Apache Maven
>> http://twitter.com/jvanzyl
>> ---------------------------------------------------------
>>
>> We know what we are, but know not what we may be.
>>
>> -- Shakespeare
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>
> --
> Cheers,
> Paul
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
---------------------------------------------------------
People develop abstractions by generalizing from concrete examples.
Every attempt to determine the correct abstraction on paper without
actually developing a running system is doomed to failure. No one
is that smart. A framework is a resuable design, so you develop it by
looking at the things it is supposed to be a design of. The more examples
you look at, the more general your framework will be.
-- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks
Re: JIRA Cleanup
Posted by Paul Benedict <pb...@apache.org>.
I advise that we add a comment in each closing issue explaining that it was
closed specifically because it's more than 2 years old and to re-open it
only if it is still valid. Otherwise, it will look very rude to close a
ticket without an explanation.
BTW, what I just recommended was done by JBoss Hibernate and Spring
Framework when they cleared out their old tickets. It was great to know
their reasoning.
On Wed, Jan 22, 2014 at 10:59 AM, Jason van Zyl <ja...@takari.io> wrote:
> Ok, I'm going to pull the ripcord tonight (8 hours from now).
>
> On Jan 21, 2014, at 9:19 PM, Jason van Zyl <ja...@takari.io> wrote:
>
> > So after looking at the issues more closely even at the 5 year-old mark
> there are still too many. At the 2 year-old mark it's a bit more
> reasonable. If I close all issues older than 2 years-old which are not
> assigned thats 415 so we would be left with 220 open issues which after a
> week or two I can probably get through, faster with some help. But that's
> probably reasonable as more recent issues are pertinent to 3.x as I myself
> am probably not going to dig back into 2.x issues and fix them.
> >
> > So I propose sending a note to the dev and user list stating that we're
> trying to get the JIRA issue under control. We're closing all unassigned
> issues older than 2 years but people are free to reopen issues for bugs if
> they follow a process of providing a working stand-alone example of the
> problem.
> >
> > This will at least start the cleanup process.
> >
> > How's that sound?
> >
> > On Jan 20, 2014, at 4:53 PM, Jason van Zyl <ja...@takari.io> wrote:
> >
> >> Ok, I'll write something up and send it to the user and dev list.
> >>
> >> On Jan 20, 2014, at 2:17 PM, Benson Margulies <bi...@gmail.com>
> wrote:
> >>
> >>> +1 here.
> >>>
> >>> On Mon, Jan 20, 2014 at 1:12 PM, Anders Hammar <an...@hammar.net>
> wrote:
> >>>> +1 on clean up if we communicate this (and explain why).
> >>>> 0 on move
> >>>>
> >>>> /Anders
> >>>>
> >>>>
> >>>> On Mon, Jan 20, 2014 at 6:53 PM, Dominik Bartholdi <do...@fortysix.ch>
> wrote:
> >>>>
> >>>>> +1 cleanup is a really good idea!
> >>>>>
> >>>>> On 20.01.2014, at 18:50, Arnaud Héritier <ah...@gmail.com>
> wrote:
> >>>>>
> >>>>>> +1 with a jira cleanup (but documented and announced to users to
> let them
> >>>>>> understand what we do and why)
> >>>>>> +1 to move to ASF
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> On Mon, Jan 20, 2014 at 6:48 PM, Jason van Zyl <ja...@takari.io>
> wrote:
> >>>>>>
> >>>>>>> Works for me to just start over on the ASF JIRA. There are a couple
> >>>>> issues
> >>>>>>> I'd move but we can migrate a issues easily. What can't continue
> is the
> >>>>>>> complete, incomprehensible mess that is there now.
> >>>>>>>
> >>>>>>> On Jan 20, 2014, at 12:32 PM, Stephen Connolly <
> >>>>>>> stephen.alan.connolly@gmail.com> wrote:
> >>>>>>>
> >>>>>>>> If we are going wholesale dumping issues (and I am not against
> that), I
> >>>>>>>> have a more radical suggestion... let's just move core to the ASF
> >>>>> JIRA...
> >>>>>>>> with next to no issues needing migration it would be easy ;-)
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On 20 January 2014 17:23, Jason van Zyl <ja...@takari.io> wrote:
> >>>>>>>>
> >>>>>>>>> Really, it's more about dropping a nuclear bomb on JIRA. While
> trying
> >>>>> to
> >>>>>>>>> sift through it this weekend it's clear to me it's less than
> ideal in
> >>>>>>> there.
> >>>>>>>>>
> >>>>>>>>> There are issues that are 12 years old and while there might be
> some
> >>>>>>>>> useful information in there that we hand select, I think
> anything that
> >>>>>>> is
> >>>>>>>>> older than 5 years we should just close as incomplete because
> with the
> >>>>>>>>> great deal of change that's happened with 3.x most of it isn't
> >>>>> relevant
> >>>>>>> and
> >>>>>>>>> if it is, and someone cares that much then it can be reopened
> with a
> >>>>>>>>> stand-alone working example of the problem.
> >>>>>>>>>
> >>>>>>>>> Now, as to the requirements for a stand-alone working example I
> think
> >>>>> we
> >>>>>>>>> should enforce this because personally I'm not going to check out
> >>>>>>> someone's
> >>>>>>>>> project, figure out how to interpret it in relation to the actual
> >>>>>>> problem
> >>>>>>>>> in Maven and then create a project I can turn into an IT. I'm
> just not
> >>>>>>>>> going to do it generally. There might be exceptions but I don't
> want
> >>>>> to
> >>>>>>>>> read a textual examples or try to figure out snippets of a
> production
> >>>>>>>>> project that can't be shared. In m2e we require a working example
> >>>>>>> project
> >>>>>>>>> to even look at a problem and if the issue sits there for a year
> with
> >>>>> a
> >>>>>>>>> working sample project we close it.
> >>>>>>>>>
> >>>>>>>>> Having an issue tracking system with 700 open issues is useless,
> so I
> >>>>>>>>> would like to do a mass purge. It shouldn't really get beyond 50
> open
> >>>>>>>>> issues or it's just impossible to manage effectively.
> >>>>>>>>>
> >>>>>>>>> Not sure what anyone else thinks but our JIRA situation is just
> not
> >>>>>>>>> effective. I'm thinking anything over 5 years old that isn't
> assigned
> >>>>>>> to a
> >>>>>>>>> core developer we just close as incomplete and then see what
> we're
> >>>>> left
> >>>>>>>>> with. If anyone complains then we point them at doco (I'll write
> it)
> >>>>>>> about
> >>>>>>>>> creating a stand-alone project because otherwise it become
> >>>>> impossible. I
> >>>>>>>>> spent 8 hours over the weekend looking at issues trying to
> interpret
> >>>>>>> what
> >>>>>>>>> someone was trying to say and I don't want to guess. If the user
> cares
> >>>>>>>>> enough they can make an example project.
> >>>>>>>>>
> >>>>>>>>> Thanks,
> >>>>>>>>>
> >>>>>>>>> Jason
> >>>>>>>>>
> >>>>>>>>> ----------------------------------------------------------
> >>>>>>>>> Jason van Zyl
> >>>>>>>>> Founder, Apache Maven
> >>>>>>>>> http://twitter.com/jvanzyl
> >>>>>>>>> ---------------------------------------------------------
> >>>>>>>>>
> >>>>>>>>> happiness is like a butterfly: the more you chase it, the more
> it will
> >>>>>>>>> elude you, but if you turn your attention to other things, it
> will
> >>>>> come
> >>>>>>>>> and sit softly on your shoulder ...
> >>>>>>>>>
> >>>>>>>>> -- Thoreau
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>
> >>>>>>> Thanks,
> >>>>>>>
> >>>>>>> Jason
> >>>>>>>
> >>>>>>> ----------------------------------------------------------
> >>>>>>> Jason van Zyl
> >>>>>>> Founder, Apache Maven
> >>>>>>> http://twitter.com/jvanzyl
> >>>>>>> ---------------------------------------------------------
> >>>>>>>
> >>>>>>> believe nothing, no matter where you read it,
> >>>>>>> or who has said it,
> >>>>>>> not even if i have said it,
> >>>>>>> unless it agrees with your own reason
> >>>>>>> and your own common sense.
> >>>>>>>
> >>>>>>> -- Buddha
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> -----
> >>>>>> Arnaud Héritier
> >>>>>> http://aheritier.net
> >>>>>> Mail/GTalk: aheritier AT gmail DOT com
> >>>>>> Twitter/Skype : aheritier
> >>>>>
> >>>>>
> >>>>> ---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>>
> >>>>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>
> >>
> >> Thanks,
> >>
> >> Jason
> >>
> >> ----------------------------------------------------------
> >> Jason van Zyl
> >> Founder, Apache Maven
> >> http://twitter.com/jvanzyl
> >> ---------------------------------------------------------
> >>
> >> There's no sense in being precise when you don't even know what you're
> talking about.
> >>
> >> -- John von Neumann
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >
> > Thanks,
> >
> > Jason
> >
> > ----------------------------------------------------------
> > Jason van Zyl
> > Founder, Apache Maven
> > http://twitter.com/jvanzyl
> > ---------------------------------------------------------
> >
> > Script timed out:/Users/jvanzyl/signature/signature.sh
> >
> >
> >
> >
> >
> >
> >
> >
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
>
> We know what we are, but know not what we may be.
>
> -- Shakespeare
>
>
>
>
>
>
>
>
>
--
Cheers,
Paul
Re: JIRA Cleanup
Posted by Jason van Zyl <ja...@takari.io>.
Ok, I'm going to pull the ripcord tonight (8 hours from now).
On Jan 21, 2014, at 9:19 PM, Jason van Zyl <ja...@takari.io> wrote:
> So after looking at the issues more closely even at the 5 year-old mark there are still too many. At the 2 year-old mark it's a bit more reasonable. If I close all issues older than 2 years-old which are not assigned thats 415 so we would be left with 220 open issues which after a week or two I can probably get through, faster with some help. But that's probably reasonable as more recent issues are pertinent to 3.x as I myself am probably not going to dig back into 2.x issues and fix them.
>
> So I propose sending a note to the dev and user list stating that we're trying to get the JIRA issue under control. We're closing all unassigned issues older than 2 years but people are free to reopen issues for bugs if they follow a process of providing a working stand-alone example of the problem.
>
> This will at least start the cleanup process.
>
> How's that sound?
>
> On Jan 20, 2014, at 4:53 PM, Jason van Zyl <ja...@takari.io> wrote:
>
>> Ok, I'll write something up and send it to the user and dev list.
>>
>> On Jan 20, 2014, at 2:17 PM, Benson Margulies <bi...@gmail.com> wrote:
>>
>>> +1 here.
>>>
>>> On Mon, Jan 20, 2014 at 1:12 PM, Anders Hammar <an...@hammar.net> wrote:
>>>> +1 on clean up if we communicate this (and explain why).
>>>> 0 on move
>>>>
>>>> /Anders
>>>>
>>>>
>>>> On Mon, Jan 20, 2014 at 6:53 PM, Dominik Bartholdi <do...@fortysix.ch> wrote:
>>>>
>>>>> +1 cleanup is a really good idea!
>>>>>
>>>>> On 20.01.2014, at 18:50, Arnaud Héritier <ah...@gmail.com> wrote:
>>>>>
>>>>>> +1 with a jira cleanup (but documented and announced to users to let them
>>>>>> understand what we do and why)
>>>>>> +1 to move to ASF
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Mon, Jan 20, 2014 at 6:48 PM, Jason van Zyl <ja...@takari.io> wrote:
>>>>>>
>>>>>>> Works for me to just start over on the ASF JIRA. There are a couple
>>>>> issues
>>>>>>> I'd move but we can migrate a issues easily. What can't continue is the
>>>>>>> complete, incomprehensible mess that is there now.
>>>>>>>
>>>>>>> On Jan 20, 2014, at 12:32 PM, Stephen Connolly <
>>>>>>> stephen.alan.connolly@gmail.com> wrote:
>>>>>>>
>>>>>>>> If we are going wholesale dumping issues (and I am not against that), I
>>>>>>>> have a more radical suggestion... let's just move core to the ASF
>>>>> JIRA...
>>>>>>>> with next to no issues needing migration it would be easy ;-)
>>>>>>>>
>>>>>>>>
>>>>>>>> On 20 January 2014 17:23, Jason van Zyl <ja...@takari.io> wrote:
>>>>>>>>
>>>>>>>>> Really, it's more about dropping a nuclear bomb on JIRA. While trying
>>>>> to
>>>>>>>>> sift through it this weekend it's clear to me it's less than ideal in
>>>>>>> there.
>>>>>>>>>
>>>>>>>>> There are issues that are 12 years old and while there might be some
>>>>>>>>> useful information in there that we hand select, I think anything that
>>>>>>> is
>>>>>>>>> older than 5 years we should just close as incomplete because with the
>>>>>>>>> great deal of change that's happened with 3.x most of it isn't
>>>>> relevant
>>>>>>> and
>>>>>>>>> if it is, and someone cares that much then it can be reopened with a
>>>>>>>>> stand-alone working example of the problem.
>>>>>>>>>
>>>>>>>>> Now, as to the requirements for a stand-alone working example I think
>>>>> we
>>>>>>>>> should enforce this because personally I'm not going to check out
>>>>>>> someone's
>>>>>>>>> project, figure out how to interpret it in relation to the actual
>>>>>>> problem
>>>>>>>>> in Maven and then create a project I can turn into an IT. I'm just not
>>>>>>>>> going to do it generally. There might be exceptions but I don't want
>>>>> to
>>>>>>>>> read a textual examples or try to figure out snippets of a production
>>>>>>>>> project that can't be shared. In m2e we require a working example
>>>>>>> project
>>>>>>>>> to even look at a problem and if the issue sits there for a year with
>>>>> a
>>>>>>>>> working sample project we close it.
>>>>>>>>>
>>>>>>>>> Having an issue tracking system with 700 open issues is useless, so I
>>>>>>>>> would like to do a mass purge. It shouldn't really get beyond 50 open
>>>>>>>>> issues or it's just impossible to manage effectively.
>>>>>>>>>
>>>>>>>>> Not sure what anyone else thinks but our JIRA situation is just not
>>>>>>>>> effective. I'm thinking anything over 5 years old that isn't assigned
>>>>>>> to a
>>>>>>>>> core developer we just close as incomplete and then see what we're
>>>>> left
>>>>>>>>> with. If anyone complains then we point them at doco (I'll write it)
>>>>>>> about
>>>>>>>>> creating a stand-alone project because otherwise it become
>>>>> impossible. I
>>>>>>>>> spent 8 hours over the weekend looking at issues trying to interpret
>>>>>>> what
>>>>>>>>> someone was trying to say and I don't want to guess. If the user cares
>>>>>>>>> enough they can make an example project.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>>
>>>>>>>>> Jason
>>>>>>>>>
>>>>>>>>> ----------------------------------------------------------
>>>>>>>>> Jason van Zyl
>>>>>>>>> Founder, Apache Maven
>>>>>>>>> http://twitter.com/jvanzyl
>>>>>>>>> ---------------------------------------------------------
>>>>>>>>>
>>>>>>>>> happiness is like a butterfly: the more you chase it, the more it will
>>>>>>>>> elude you, but if you turn your attention to other things, it will
>>>>> come
>>>>>>>>> and sit softly on your shoulder ...
>>>>>>>>>
>>>>>>>>> -- Thoreau
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Jason
>>>>>>>
>>>>>>> ----------------------------------------------------------
>>>>>>> Jason van Zyl
>>>>>>> Founder, Apache Maven
>>>>>>> http://twitter.com/jvanzyl
>>>>>>> ---------------------------------------------------------
>>>>>>>
>>>>>>> believe nothing, no matter where you read it,
>>>>>>> or who has said it,
>>>>>>> not even if i have said it,
>>>>>>> unless it agrees with your own reason
>>>>>>> and your own common sense.
>>>>>>>
>>>>>>> -- Buddha
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> -----
>>>>>> Arnaud Héritier
>>>>>> http://aheritier.net
>>>>>> Mail/GTalk: aheritier AT gmail DOT com
>>>>>> Twitter/Skype : aheritier
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>
>>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder, Apache Maven
>> http://twitter.com/jvanzyl
>> ---------------------------------------------------------
>>
>> There's no sense in being precise when you don't even know what you're talking about.
>>
>> -- John von Neumann
>>
>>
>>
>>
>>
>>
>>
>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
>
> Script timed out:/Users/jvanzyl/signature/signature.sh
>
>
>
>
>
>
>
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
We know what we are, but know not what we may be.
-- Shakespeare
Re: JIRA Cleanup
Posted by Jason van Zyl <ja...@takari.io>.
So after looking at the issues more closely even at the 5 year-old mark there are still too many. At the 2 year-old mark it's a bit more reasonable. If I close all issues older than 2 years-old which are not assigned thats 415 so we would be left with 220 open issues which after a week or two I can probably get through, faster with some help. But that's probably reasonable as more recent issues are pertinent to 3.x as I myself am probably not going to dig back into 2.x issues and fix them.
So I propose sending a note to the dev and user list stating that we're trying to get the JIRA issue under control. We're closing all unassigned issues older than 2 years but people are free to reopen issues for bugs if they follow a process of providing a working stand-alone example of the problem.
This will at least start the cleanup process.
How's that sound?
On Jan 20, 2014, at 4:53 PM, Jason van Zyl <ja...@takari.io> wrote:
> Ok, I'll write something up and send it to the user and dev list.
>
> On Jan 20, 2014, at 2:17 PM, Benson Margulies <bi...@gmail.com> wrote:
>
>> +1 here.
>>
>> On Mon, Jan 20, 2014 at 1:12 PM, Anders Hammar <an...@hammar.net> wrote:
>>> +1 on clean up if we communicate this (and explain why).
>>> 0 on move
>>>
>>> /Anders
>>>
>>>
>>> On Mon, Jan 20, 2014 at 6:53 PM, Dominik Bartholdi <do...@fortysix.ch> wrote:
>>>
>>>> +1 cleanup is a really good idea!
>>>>
>>>> On 20.01.2014, at 18:50, Arnaud Héritier <ah...@gmail.com> wrote:
>>>>
>>>>> +1 with a jira cleanup (but documented and announced to users to let them
>>>>> understand what we do and why)
>>>>> +1 to move to ASF
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Mon, Jan 20, 2014 at 6:48 PM, Jason van Zyl <ja...@takari.io> wrote:
>>>>>
>>>>>> Works for me to just start over on the ASF JIRA. There are a couple
>>>> issues
>>>>>> I'd move but we can migrate a issues easily. What can't continue is the
>>>>>> complete, incomprehensible mess that is there now.
>>>>>>
>>>>>> On Jan 20, 2014, at 12:32 PM, Stephen Connolly <
>>>>>> stephen.alan.connolly@gmail.com> wrote:
>>>>>>
>>>>>>> If we are going wholesale dumping issues (and I am not against that), I
>>>>>>> have a more radical suggestion... let's just move core to the ASF
>>>> JIRA...
>>>>>>> with next to no issues needing migration it would be easy ;-)
>>>>>>>
>>>>>>>
>>>>>>> On 20 January 2014 17:23, Jason van Zyl <ja...@takari.io> wrote:
>>>>>>>
>>>>>>>> Really, it's more about dropping a nuclear bomb on JIRA. While trying
>>>> to
>>>>>>>> sift through it this weekend it's clear to me it's less than ideal in
>>>>>> there.
>>>>>>>>
>>>>>>>> There are issues that are 12 years old and while there might be some
>>>>>>>> useful information in there that we hand select, I think anything that
>>>>>> is
>>>>>>>> older than 5 years we should just close as incomplete because with the
>>>>>>>> great deal of change that's happened with 3.x most of it isn't
>>>> relevant
>>>>>> and
>>>>>>>> if it is, and someone cares that much then it can be reopened with a
>>>>>>>> stand-alone working example of the problem.
>>>>>>>>
>>>>>>>> Now, as to the requirements for a stand-alone working example I think
>>>> we
>>>>>>>> should enforce this because personally I'm not going to check out
>>>>>> someone's
>>>>>>>> project, figure out how to interpret it in relation to the actual
>>>>>> problem
>>>>>>>> in Maven and then create a project I can turn into an IT. I'm just not
>>>>>>>> going to do it generally. There might be exceptions but I don't want
>>>> to
>>>>>>>> read a textual examples or try to figure out snippets of a production
>>>>>>>> project that can't be shared. In m2e we require a working example
>>>>>> project
>>>>>>>> to even look at a problem and if the issue sits there for a year with
>>>> a
>>>>>>>> working sample project we close it.
>>>>>>>>
>>>>>>>> Having an issue tracking system with 700 open issues is useless, so I
>>>>>>>> would like to do a mass purge. It shouldn't really get beyond 50 open
>>>>>>>> issues or it's just impossible to manage effectively.
>>>>>>>>
>>>>>>>> Not sure what anyone else thinks but our JIRA situation is just not
>>>>>>>> effective. I'm thinking anything over 5 years old that isn't assigned
>>>>>> to a
>>>>>>>> core developer we just close as incomplete and then see what we're
>>>> left
>>>>>>>> with. If anyone complains then we point them at doco (I'll write it)
>>>>>> about
>>>>>>>> creating a stand-alone project because otherwise it become
>>>> impossible. I
>>>>>>>> spent 8 hours over the weekend looking at issues trying to interpret
>>>>>> what
>>>>>>>> someone was trying to say and I don't want to guess. If the user cares
>>>>>>>> enough they can make an example project.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>>
>>>>>>>> Jason
>>>>>>>>
>>>>>>>> ----------------------------------------------------------
>>>>>>>> Jason van Zyl
>>>>>>>> Founder, Apache Maven
>>>>>>>> http://twitter.com/jvanzyl
>>>>>>>> ---------------------------------------------------------
>>>>>>>>
>>>>>>>> happiness is like a butterfly: the more you chase it, the more it will
>>>>>>>> elude you, but if you turn your attention to other things, it will
>>>> come
>>>>>>>> and sit softly on your shoulder ...
>>>>>>>>
>>>>>>>> -- Thoreau
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Jason
>>>>>>
>>>>>> ----------------------------------------------------------
>>>>>> Jason van Zyl
>>>>>> Founder, Apache Maven
>>>>>> http://twitter.com/jvanzyl
>>>>>> ---------------------------------------------------------
>>>>>>
>>>>>> believe nothing, no matter where you read it,
>>>>>> or who has said it,
>>>>>> not even if i have said it,
>>>>>> unless it agrees with your own reason
>>>>>> and your own common sense.
>>>>>>
>>>>>> -- Buddha
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> -----
>>>>> Arnaud Héritier
>>>>> http://aheritier.net
>>>>> Mail/GTalk: aheritier AT gmail DOT com
>>>>> Twitter/Skype : aheritier
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
>
> There's no sense in being precise when you don't even know what you're talking about.
>
> -- John von Neumann
>
>
>
>
>
>
>
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
Script timed out:/Users/jvanzyl/signature/signature.sh
Re: JIRA Cleanup
Posted by Jason van Zyl <ja...@takari.io>.
Ok, I'll write something up and send it to the user and dev list.
On Jan 20, 2014, at 2:17 PM, Benson Margulies <bi...@gmail.com> wrote:
> +1 here.
>
> On Mon, Jan 20, 2014 at 1:12 PM, Anders Hammar <an...@hammar.net> wrote:
>> +1 on clean up if we communicate this (and explain why).
>> 0 on move
>>
>> /Anders
>>
>>
>> On Mon, Jan 20, 2014 at 6:53 PM, Dominik Bartholdi <do...@fortysix.ch> wrote:
>>
>>> +1 cleanup is a really good idea!
>>>
>>> On 20.01.2014, at 18:50, Arnaud Héritier <ah...@gmail.com> wrote:
>>>
>>>> +1 with a jira cleanup (but documented and announced to users to let them
>>>> understand what we do and why)
>>>> +1 to move to ASF
>>>>
>>>>
>>>>
>>>>
>>>> On Mon, Jan 20, 2014 at 6:48 PM, Jason van Zyl <ja...@takari.io> wrote:
>>>>
>>>>> Works for me to just start over on the ASF JIRA. There are a couple
>>> issues
>>>>> I'd move but we can migrate a issues easily. What can't continue is the
>>>>> complete, incomprehensible mess that is there now.
>>>>>
>>>>> On Jan 20, 2014, at 12:32 PM, Stephen Connolly <
>>>>> stephen.alan.connolly@gmail.com> wrote:
>>>>>
>>>>>> If we are going wholesale dumping issues (and I am not against that), I
>>>>>> have a more radical suggestion... let's just move core to the ASF
>>> JIRA...
>>>>>> with next to no issues needing migration it would be easy ;-)
>>>>>>
>>>>>>
>>>>>> On 20 January 2014 17:23, Jason van Zyl <ja...@takari.io> wrote:
>>>>>>
>>>>>>> Really, it's more about dropping a nuclear bomb on JIRA. While trying
>>> to
>>>>>>> sift through it this weekend it's clear to me it's less than ideal in
>>>>> there.
>>>>>>>
>>>>>>> There are issues that are 12 years old and while there might be some
>>>>>>> useful information in there that we hand select, I think anything that
>>>>> is
>>>>>>> older than 5 years we should just close as incomplete because with the
>>>>>>> great deal of change that's happened with 3.x most of it isn't
>>> relevant
>>>>> and
>>>>>>> if it is, and someone cares that much then it can be reopened with a
>>>>>>> stand-alone working example of the problem.
>>>>>>>
>>>>>>> Now, as to the requirements for a stand-alone working example I think
>>> we
>>>>>>> should enforce this because personally I'm not going to check out
>>>>> someone's
>>>>>>> project, figure out how to interpret it in relation to the actual
>>>>> problem
>>>>>>> in Maven and then create a project I can turn into an IT. I'm just not
>>>>>>> going to do it generally. There might be exceptions but I don't want
>>> to
>>>>>>> read a textual examples or try to figure out snippets of a production
>>>>>>> project that can't be shared. In m2e we require a working example
>>>>> project
>>>>>>> to even look at a problem and if the issue sits there for a year with
>>> a
>>>>>>> working sample project we close it.
>>>>>>>
>>>>>>> Having an issue tracking system with 700 open issues is useless, so I
>>>>>>> would like to do a mass purge. It shouldn't really get beyond 50 open
>>>>>>> issues or it's just impossible to manage effectively.
>>>>>>>
>>>>>>> Not sure what anyone else thinks but our JIRA situation is just not
>>>>>>> effective. I'm thinking anything over 5 years old that isn't assigned
>>>>> to a
>>>>>>> core developer we just close as incomplete and then see what we're
>>> left
>>>>>>> with. If anyone complains then we point them at doco (I'll write it)
>>>>> about
>>>>>>> creating a stand-alone project because otherwise it become
>>> impossible. I
>>>>>>> spent 8 hours over the weekend looking at issues trying to interpret
>>>>> what
>>>>>>> someone was trying to say and I don't want to guess. If the user cares
>>>>>>> enough they can make an example project.
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Jason
>>>>>>>
>>>>>>> ----------------------------------------------------------
>>>>>>> Jason van Zyl
>>>>>>> Founder, Apache Maven
>>>>>>> http://twitter.com/jvanzyl
>>>>>>> ---------------------------------------------------------
>>>>>>>
>>>>>>> happiness is like a butterfly: the more you chase it, the more it will
>>>>>>> elude you, but if you turn your attention to other things, it will
>>> come
>>>>>>> and sit softly on your shoulder ...
>>>>>>>
>>>>>>> -- Thoreau
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Jason
>>>>>
>>>>> ----------------------------------------------------------
>>>>> Jason van Zyl
>>>>> Founder, Apache Maven
>>>>> http://twitter.com/jvanzyl
>>>>> ---------------------------------------------------------
>>>>>
>>>>> believe nothing, no matter where you read it,
>>>>> or who has said it,
>>>>> not even if i have said it,
>>>>> unless it agrees with your own reason
>>>>> and your own common sense.
>>>>>
>>>>> -- Buddha
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> -----
>>>> Arnaud Héritier
>>>> http://aheritier.net
>>>> Mail/GTalk: aheritier AT gmail DOT com
>>>> Twitter/Skype : aheritier
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
There's no sense in being precise when you don't even know what you're talking about.
-- John von Neumann
Re: JIRA Cleanup
Posted by Benson Margulies <bi...@gmail.com>.
+1 here.
On Mon, Jan 20, 2014 at 1:12 PM, Anders Hammar <an...@hammar.net> wrote:
> +1 on clean up if we communicate this (and explain why).
> 0 on move
>
> /Anders
>
>
> On Mon, Jan 20, 2014 at 6:53 PM, Dominik Bartholdi <do...@fortysix.ch> wrote:
>
>> +1 cleanup is a really good idea!
>>
>> On 20.01.2014, at 18:50, Arnaud Héritier <ah...@gmail.com> wrote:
>>
>> > +1 with a jira cleanup (but documented and announced to users to let them
>> > understand what we do and why)
>> > +1 to move to ASF
>> >
>> >
>> >
>> >
>> > On Mon, Jan 20, 2014 at 6:48 PM, Jason van Zyl <ja...@takari.io> wrote:
>> >
>> >> Works for me to just start over on the ASF JIRA. There are a couple
>> issues
>> >> I'd move but we can migrate a issues easily. What can't continue is the
>> >> complete, incomprehensible mess that is there now.
>> >>
>> >> On Jan 20, 2014, at 12:32 PM, Stephen Connolly <
>> >> stephen.alan.connolly@gmail.com> wrote:
>> >>
>> >>> If we are going wholesale dumping issues (and I am not against that), I
>> >>> have a more radical suggestion... let's just move core to the ASF
>> JIRA...
>> >>> with next to no issues needing migration it would be easy ;-)
>> >>>
>> >>>
>> >>> On 20 January 2014 17:23, Jason van Zyl <ja...@takari.io> wrote:
>> >>>
>> >>>> Really, it's more about dropping a nuclear bomb on JIRA. While trying
>> to
>> >>>> sift through it this weekend it's clear to me it's less than ideal in
>> >> there.
>> >>>>
>> >>>> There are issues that are 12 years old and while there might be some
>> >>>> useful information in there that we hand select, I think anything that
>> >> is
>> >>>> older than 5 years we should just close as incomplete because with the
>> >>>> great deal of change that's happened with 3.x most of it isn't
>> relevant
>> >> and
>> >>>> if it is, and someone cares that much then it can be reopened with a
>> >>>> stand-alone working example of the problem.
>> >>>>
>> >>>> Now, as to the requirements for a stand-alone working example I think
>> we
>> >>>> should enforce this because personally I'm not going to check out
>> >> someone's
>> >>>> project, figure out how to interpret it in relation to the actual
>> >> problem
>> >>>> in Maven and then create a project I can turn into an IT. I'm just not
>> >>>> going to do it generally. There might be exceptions but I don't want
>> to
>> >>>> read a textual examples or try to figure out snippets of a production
>> >>>> project that can't be shared. In m2e we require a working example
>> >> project
>> >>>> to even look at a problem and if the issue sits there for a year with
>> a
>> >>>> working sample project we close it.
>> >>>>
>> >>>> Having an issue tracking system with 700 open issues is useless, so I
>> >>>> would like to do a mass purge. It shouldn't really get beyond 50 open
>> >>>> issues or it's just impossible to manage effectively.
>> >>>>
>> >>>> Not sure what anyone else thinks but our JIRA situation is just not
>> >>>> effective. I'm thinking anything over 5 years old that isn't assigned
>> >> to a
>> >>>> core developer we just close as incomplete and then see what we're
>> left
>> >>>> with. If anyone complains then we point them at doco (I'll write it)
>> >> about
>> >>>> creating a stand-alone project because otherwise it become
>> impossible. I
>> >>>> spent 8 hours over the weekend looking at issues trying to interpret
>> >> what
>> >>>> someone was trying to say and I don't want to guess. If the user cares
>> >>>> enough they can make an example project.
>> >>>>
>> >>>> Thanks,
>> >>>>
>> >>>> Jason
>> >>>>
>> >>>> ----------------------------------------------------------
>> >>>> Jason van Zyl
>> >>>> Founder, Apache Maven
>> >>>> http://twitter.com/jvanzyl
>> >>>> ---------------------------------------------------------
>> >>>>
>> >>>> happiness is like a butterfly: the more you chase it, the more it will
>> >>>> elude you, but if you turn your attention to other things, it will
>> come
>> >>>> and sit softly on your shoulder ...
>> >>>>
>> >>>> -- Thoreau
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>
>> >> Thanks,
>> >>
>> >> Jason
>> >>
>> >> ----------------------------------------------------------
>> >> Jason van Zyl
>> >> Founder, Apache Maven
>> >> http://twitter.com/jvanzyl
>> >> ---------------------------------------------------------
>> >>
>> >> believe nothing, no matter where you read it,
>> >> or who has said it,
>> >> not even if i have said it,
>> >> unless it agrees with your own reason
>> >> and your own common sense.
>> >>
>> >> -- Buddha
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >
>> >
>> > --
>> > -----
>> > Arnaud Héritier
>> > http://aheritier.net
>> > Mail/GTalk: aheritier AT gmail DOT com
>> > Twitter/Skype : aheritier
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: JIRA Cleanup
Posted by Anders Hammar <an...@hammar.net>.
+1 on clean up if we communicate this (and explain why).
0 on move
/Anders
On Mon, Jan 20, 2014 at 6:53 PM, Dominik Bartholdi <do...@fortysix.ch> wrote:
> +1 cleanup is a really good idea!
>
> On 20.01.2014, at 18:50, Arnaud Héritier <ah...@gmail.com> wrote:
>
> > +1 with a jira cleanup (but documented and announced to users to let them
> > understand what we do and why)
> > +1 to move to ASF
> >
> >
> >
> >
> > On Mon, Jan 20, 2014 at 6:48 PM, Jason van Zyl <ja...@takari.io> wrote:
> >
> >> Works for me to just start over on the ASF JIRA. There are a couple
> issues
> >> I'd move but we can migrate a issues easily. What can't continue is the
> >> complete, incomprehensible mess that is there now.
> >>
> >> On Jan 20, 2014, at 12:32 PM, Stephen Connolly <
> >> stephen.alan.connolly@gmail.com> wrote:
> >>
> >>> If we are going wholesale dumping issues (and I am not against that), I
> >>> have a more radical suggestion... let's just move core to the ASF
> JIRA...
> >>> with next to no issues needing migration it would be easy ;-)
> >>>
> >>>
> >>> On 20 January 2014 17:23, Jason van Zyl <ja...@takari.io> wrote:
> >>>
> >>>> Really, it's more about dropping a nuclear bomb on JIRA. While trying
> to
> >>>> sift through it this weekend it's clear to me it's less than ideal in
> >> there.
> >>>>
> >>>> There are issues that are 12 years old and while there might be some
> >>>> useful information in there that we hand select, I think anything that
> >> is
> >>>> older than 5 years we should just close as incomplete because with the
> >>>> great deal of change that's happened with 3.x most of it isn't
> relevant
> >> and
> >>>> if it is, and someone cares that much then it can be reopened with a
> >>>> stand-alone working example of the problem.
> >>>>
> >>>> Now, as to the requirements for a stand-alone working example I think
> we
> >>>> should enforce this because personally I'm not going to check out
> >> someone's
> >>>> project, figure out how to interpret it in relation to the actual
> >> problem
> >>>> in Maven and then create a project I can turn into an IT. I'm just not
> >>>> going to do it generally. There might be exceptions but I don't want
> to
> >>>> read a textual examples or try to figure out snippets of a production
> >>>> project that can't be shared. In m2e we require a working example
> >> project
> >>>> to even look at a problem and if the issue sits there for a year with
> a
> >>>> working sample project we close it.
> >>>>
> >>>> Having an issue tracking system with 700 open issues is useless, so I
> >>>> would like to do a mass purge. It shouldn't really get beyond 50 open
> >>>> issues or it's just impossible to manage effectively.
> >>>>
> >>>> Not sure what anyone else thinks but our JIRA situation is just not
> >>>> effective. I'm thinking anything over 5 years old that isn't assigned
> >> to a
> >>>> core developer we just close as incomplete and then see what we're
> left
> >>>> with. If anyone complains then we point them at doco (I'll write it)
> >> about
> >>>> creating a stand-alone project because otherwise it become
> impossible. I
> >>>> spent 8 hours over the weekend looking at issues trying to interpret
> >> what
> >>>> someone was trying to say and I don't want to guess. If the user cares
> >>>> enough they can make an example project.
> >>>>
> >>>> Thanks,
> >>>>
> >>>> Jason
> >>>>
> >>>> ----------------------------------------------------------
> >>>> Jason van Zyl
> >>>> Founder, Apache Maven
> >>>> http://twitter.com/jvanzyl
> >>>> ---------------------------------------------------------
> >>>>
> >>>> happiness is like a butterfly: the more you chase it, the more it will
> >>>> elude you, but if you turn your attention to other things, it will
> come
> >>>> and sit softly on your shoulder ...
> >>>>
> >>>> -- Thoreau
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>
> >> Thanks,
> >>
> >> Jason
> >>
> >> ----------------------------------------------------------
> >> Jason van Zyl
> >> Founder, Apache Maven
> >> http://twitter.com/jvanzyl
> >> ---------------------------------------------------------
> >>
> >> believe nothing, no matter where you read it,
> >> or who has said it,
> >> not even if i have said it,
> >> unless it agrees with your own reason
> >> and your own common sense.
> >>
> >> -- Buddha
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >
> >
> > --
> > -----
> > Arnaud Héritier
> > http://aheritier.net
> > Mail/GTalk: aheritier AT gmail DOT com
> > Twitter/Skype : aheritier
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: JIRA Cleanup
Posted by Dominik Bartholdi <do...@fortysix.ch>.
+1 cleanup is a really good idea!
On 20.01.2014, at 18:50, Arnaud Héritier <ah...@gmail.com> wrote:
> +1 with a jira cleanup (but documented and announced to users to let them
> understand what we do and why)
> +1 to move to ASF
>
>
>
>
> On Mon, Jan 20, 2014 at 6:48 PM, Jason van Zyl <ja...@takari.io> wrote:
>
>> Works for me to just start over on the ASF JIRA. There are a couple issues
>> I'd move but we can migrate a issues easily. What can't continue is the
>> complete, incomprehensible mess that is there now.
>>
>> On Jan 20, 2014, at 12:32 PM, Stephen Connolly <
>> stephen.alan.connolly@gmail.com> wrote:
>>
>>> If we are going wholesale dumping issues (and I am not against that), I
>>> have a more radical suggestion... let's just move core to the ASF JIRA...
>>> with next to no issues needing migration it would be easy ;-)
>>>
>>>
>>> On 20 January 2014 17:23, Jason van Zyl <ja...@takari.io> wrote:
>>>
>>>> Really, it's more about dropping a nuclear bomb on JIRA. While trying to
>>>> sift through it this weekend it's clear to me it's less than ideal in
>> there.
>>>>
>>>> There are issues that are 12 years old and while there might be some
>>>> useful information in there that we hand select, I think anything that
>> is
>>>> older than 5 years we should just close as incomplete because with the
>>>> great deal of change that's happened with 3.x most of it isn't relevant
>> and
>>>> if it is, and someone cares that much then it can be reopened with a
>>>> stand-alone working example of the problem.
>>>>
>>>> Now, as to the requirements for a stand-alone working example I think we
>>>> should enforce this because personally I'm not going to check out
>> someone's
>>>> project, figure out how to interpret it in relation to the actual
>> problem
>>>> in Maven and then create a project I can turn into an IT. I'm just not
>>>> going to do it generally. There might be exceptions but I don't want to
>>>> read a textual examples or try to figure out snippets of a production
>>>> project that can't be shared. In m2e we require a working example
>> project
>>>> to even look at a problem and if the issue sits there for a year with a
>>>> working sample project we close it.
>>>>
>>>> Having an issue tracking system with 700 open issues is useless, so I
>>>> would like to do a mass purge. It shouldn't really get beyond 50 open
>>>> issues or it's just impossible to manage effectively.
>>>>
>>>> Not sure what anyone else thinks but our JIRA situation is just not
>>>> effective. I'm thinking anything over 5 years old that isn't assigned
>> to a
>>>> core developer we just close as incomplete and then see what we're left
>>>> with. If anyone complains then we point them at doco (I'll write it)
>> about
>>>> creating a stand-alone project because otherwise it become impossible. I
>>>> spent 8 hours over the weekend looking at issues trying to interpret
>> what
>>>> someone was trying to say and I don't want to guess. If the user cares
>>>> enough they can make an example project.
>>>>
>>>> Thanks,
>>>>
>>>> Jason
>>>>
>>>> ----------------------------------------------------------
>>>> Jason van Zyl
>>>> Founder, Apache Maven
>>>> http://twitter.com/jvanzyl
>>>> ---------------------------------------------------------
>>>>
>>>> happiness is like a butterfly: the more you chase it, the more it will
>>>> elude you, but if you turn your attention to other things, it will come
>>>> and sit softly on your shoulder ...
>>>>
>>>> -- Thoreau
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder, Apache Maven
>> http://twitter.com/jvanzyl
>> ---------------------------------------------------------
>>
>> believe nothing, no matter where you read it,
>> or who has said it,
>> not even if i have said it,
>> unless it agrees with your own reason
>> and your own common sense.
>>
>> -- Buddha
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>
> --
> -----
> Arnaud Héritier
> http://aheritier.net
> Mail/GTalk: aheritier AT gmail DOT com
> Twitter/Skype : aheritier
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: JIRA Cleanup
Posted by Arnaud Héritier <ah...@gmail.com>.
+1 with a jira cleanup (but documented and announced to users to let them
understand what we do and why)
+1 to move to ASF
On Mon, Jan 20, 2014 at 6:48 PM, Jason van Zyl <ja...@takari.io> wrote:
> Works for me to just start over on the ASF JIRA. There are a couple issues
> I'd move but we can migrate a issues easily. What can't continue is the
> complete, incomprehensible mess that is there now.
>
> On Jan 20, 2014, at 12:32 PM, Stephen Connolly <
> stephen.alan.connolly@gmail.com> wrote:
>
> > If we are going wholesale dumping issues (and I am not against that), I
> > have a more radical suggestion... let's just move core to the ASF JIRA...
> > with next to no issues needing migration it would be easy ;-)
> >
> >
> > On 20 January 2014 17:23, Jason van Zyl <ja...@takari.io> wrote:
> >
> >> Really, it's more about dropping a nuclear bomb on JIRA. While trying to
> >> sift through it this weekend it's clear to me it's less than ideal in
> there.
> >>
> >> There are issues that are 12 years old and while there might be some
> >> useful information in there that we hand select, I think anything that
> is
> >> older than 5 years we should just close as incomplete because with the
> >> great deal of change that's happened with 3.x most of it isn't relevant
> and
> >> if it is, and someone cares that much then it can be reopened with a
> >> stand-alone working example of the problem.
> >>
> >> Now, as to the requirements for a stand-alone working example I think we
> >> should enforce this because personally I'm not going to check out
> someone's
> >> project, figure out how to interpret it in relation to the actual
> problem
> >> in Maven and then create a project I can turn into an IT. I'm just not
> >> going to do it generally. There might be exceptions but I don't want to
> >> read a textual examples or try to figure out snippets of a production
> >> project that can't be shared. In m2e we require a working example
> project
> >> to even look at a problem and if the issue sits there for a year with a
> >> working sample project we close it.
> >>
> >> Having an issue tracking system with 700 open issues is useless, so I
> >> would like to do a mass purge. It shouldn't really get beyond 50 open
> >> issues or it's just impossible to manage effectively.
> >>
> >> Not sure what anyone else thinks but our JIRA situation is just not
> >> effective. I'm thinking anything over 5 years old that isn't assigned
> to a
> >> core developer we just close as incomplete and then see what we're left
> >> with. If anyone complains then we point them at doco (I'll write it)
> about
> >> creating a stand-alone project because otherwise it become impossible. I
> >> spent 8 hours over the weekend looking at issues trying to interpret
> what
> >> someone was trying to say and I don't want to guess. If the user cares
> >> enough they can make an example project.
> >>
> >> Thanks,
> >>
> >> Jason
> >>
> >> ----------------------------------------------------------
> >> Jason van Zyl
> >> Founder, Apache Maven
> >> http://twitter.com/jvanzyl
> >> ---------------------------------------------------------
> >>
> >> happiness is like a butterfly: the more you chase it, the more it will
> >> elude you, but if you turn your attention to other things, it will come
> >> and sit softly on your shoulder ...
> >>
> >> -- Thoreau
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
>
> believe nothing, no matter where you read it,
> or who has said it,
> not even if i have said it,
> unless it agrees with your own reason
> and your own common sense.
>
> -- Buddha
>
>
>
>
>
>
>
>
>
--
-----
Arnaud Héritier
http://aheritier.net
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier
Re: JIRA Cleanup
Posted by Jason van Zyl <ja...@takari.io>.
Works for me to just start over on the ASF JIRA. There are a couple issues I'd move but we can migrate a issues easily. What can't continue is the complete, incomprehensible mess that is there now.
On Jan 20, 2014, at 12:32 PM, Stephen Connolly <st...@gmail.com> wrote:
> If we are going wholesale dumping issues (and I am not against that), I
> have a more radical suggestion... let's just move core to the ASF JIRA...
> with next to no issues needing migration it would be easy ;-)
>
>
> On 20 January 2014 17:23, Jason van Zyl <ja...@takari.io> wrote:
>
>> Really, it's more about dropping a nuclear bomb on JIRA. While trying to
>> sift through it this weekend it's clear to me it's less than ideal in there.
>>
>> There are issues that are 12 years old and while there might be some
>> useful information in there that we hand select, I think anything that is
>> older than 5 years we should just close as incomplete because with the
>> great deal of change that's happened with 3.x most of it isn't relevant and
>> if it is, and someone cares that much then it can be reopened with a
>> stand-alone working example of the problem.
>>
>> Now, as to the requirements for a stand-alone working example I think we
>> should enforce this because personally I'm not going to check out someone's
>> project, figure out how to interpret it in relation to the actual problem
>> in Maven and then create a project I can turn into an IT. I'm just not
>> going to do it generally. There might be exceptions but I don't want to
>> read a textual examples or try to figure out snippets of a production
>> project that can't be shared. In m2e we require a working example project
>> to even look at a problem and if the issue sits there for a year with a
>> working sample project we close it.
>>
>> Having an issue tracking system with 700 open issues is useless, so I
>> would like to do a mass purge. It shouldn't really get beyond 50 open
>> issues or it's just impossible to manage effectively.
>>
>> Not sure what anyone else thinks but our JIRA situation is just not
>> effective. I'm thinking anything over 5 years old that isn't assigned to a
>> core developer we just close as incomplete and then see what we're left
>> with. If anyone complains then we point them at doco (I'll write it) about
>> creating a stand-alone project because otherwise it become impossible. I
>> spent 8 hours over the weekend looking at issues trying to interpret what
>> someone was trying to say and I don't want to guess. If the user cares
>> enough they can make an example project.
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder, Apache Maven
>> http://twitter.com/jvanzyl
>> ---------------------------------------------------------
>>
>> happiness is like a butterfly: the more you chase it, the more it will
>> elude you, but if you turn your attention to other things, it will come
>> and sit softly on your shoulder ...
>>
>> -- Thoreau
>>
>>
>>
>>
>>
>>
>>
>>
>>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
believe nothing, no matter where you read it,
or who has said it,
not even if i have said it,
unless it agrees with your own reason
and your own common sense.
-- Buddha
Re: JIRA Cleanup
Posted by Stephen Connolly <st...@gmail.com>.
If we are going wholesale dumping issues (and I am not against that), I
have a more radical suggestion... let's just move core to the ASF JIRA...
with next to no issues needing migration it would be easy ;-)
On 20 January 2014 17:23, Jason van Zyl <ja...@takari.io> wrote:
> Really, it's more about dropping a nuclear bomb on JIRA. While trying to
> sift through it this weekend it's clear to me it's less than ideal in there.
>
> There are issues that are 12 years old and while there might be some
> useful information in there that we hand select, I think anything that is
> older than 5 years we should just close as incomplete because with the
> great deal of change that's happened with 3.x most of it isn't relevant and
> if it is, and someone cares that much then it can be reopened with a
> stand-alone working example of the problem.
>
> Now, as to the requirements for a stand-alone working example I think we
> should enforce this because personally I'm not going to check out someone's
> project, figure out how to interpret it in relation to the actual problem
> in Maven and then create a project I can turn into an IT. I'm just not
> going to do it generally. There might be exceptions but I don't want to
> read a textual examples or try to figure out snippets of a production
> project that can't be shared. In m2e we require a working example project
> to even look at a problem and if the issue sits there for a year with a
> working sample project we close it.
>
> Having an issue tracking system with 700 open issues is useless, so I
> would like to do a mass purge. It shouldn't really get beyond 50 open
> issues or it's just impossible to manage effectively.
>
> Not sure what anyone else thinks but our JIRA situation is just not
> effective. I'm thinking anything over 5 years old that isn't assigned to a
> core developer we just close as incomplete and then see what we're left
> with. If anyone complains then we point them at doco (I'll write it) about
> creating a stand-alone project because otherwise it become impossible. I
> spent 8 hours over the weekend looking at issues trying to interpret what
> someone was trying to say and I don't want to guess. If the user cares
> enough they can make an example project.
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
>
> happiness is like a butterfly: the more you chase it, the more it will
> elude you, but if you turn your attention to other things, it will come
> and sit softly on your shoulder ...
>
> -- Thoreau
>
>
>
>
>
>
>
>
>