[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-dev
Subject:    Re: [HEADS-UP] ActiveMQ JIRA clean-up
From:       Clebert Suconic <clebert.suconic () gmail ! com>
Date:       2020-12-02 19:35:30
Message-ID: CAKF+bsrdT7mRb1k4VkRh=7UZ4pHxbx4CtkDqYM+Cawvmi_YY4w () mail ! gmail ! com
[Download RAW message or body]

One thing I always do, is to use this project of mine to filter the
JIRAs that were part of the release:

https://github.com/rh-messaging/jira-git-report

I used to have it on my personal github and I moved it there.


Basically when you filter the commits, you would have a list of
commits associated with the interval you pass.

To give you an idea of what I'm talking about, here at the end of the
report, click on "60 JIRAS on ARTEMIS JIRAs"


http://activemq.apache.org/components/artemis/download/commit-report-2.16.0

It is a tool I wrote specifically to this purpose as I was always
having to filter the JIRAs commit by commit.

Feel free to ask me for help if I got you interested and you would
like to do the same on AMQ jira.


On Tue, Dec 1, 2020 at 11:56 PM Jean-Baptiste Onofre <jb@nanthrax.net> wrote:
> 
> +1
> 
> I did a quick pass before 5.15.14 release, but definitely a more "concrete" plan \
> makes sense. 
> Thanks !
> Regards
> JB
> 
> > Le 1 déc. 2020 à 19:19, Matt Pavlovich <mattrpav@gmail.com> a écrit :
> > 
> > Hey all-
> > 
> > In an effort to clean-up a number of tickets that are more likely stale and fixed \
> > in recent releases, I'm planning on making a clean-up pass through JIRA. 
> > For tickets that pre-date 5.15.x (over 400 issues)
> > 1. Review the ticket for relevance and likeliness to still be an issue.
> > 2. If likely fixed or a non-issue, ask the reporter to confirm the issue is still \
> > a problem in 5.15.13 (or newer) 3. Note to the reporter that the ticket will be \
> > closed in 30 days if there is no response. 
> > Thanks,
> > Matt Pavlovich
> 


--
Clebert Suconic


[prev in list] [next in list] [prev in thread] [next in thread]