hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stack <st...@duboce.net>
Subject Re: Changing resolution in JIRA
Date Thu, 19 Nov 2015 16:25:57 GMT
Try now. Made you an administrator Lars.
St.Ack

On Thu, Nov 19, 2015 at 5:07 AM, Lars Francke <lars.francke@gmail.com>
wrote:

> That was quick: I'm not allowed to close issues.
>
> Would you consider giving me more permissions for JIRA also as per my other
> previous mail?
>
> On Thu, Nov 19, 2015 at 2:04 PM, Lars Francke <lars.francke@gmail.com>
> wrote:
>
> > As a first step I'm going to try and change all issues to closed that
> > match this JIRA filter:
> >
> > "project = HBASE AND status = Resolved AND fixVersion in
> > releasedVersions() AND fixVersion NOT IN unreleasedVersions()"
> >
> > This closes fewer issues than per your definition but leaves the
> > possibility of changing issues that have been applied to any unreleased
> > version. Currently this filter matches 2243 issues.
> >
> > On Mon, Nov 9, 2015 at 9:32 PM, Lars Francke <lars.francke@gmail.com>
> > wrote:
> >
> >> Sounds sensible. There's a whole bunch of them (~3600 in total but
> >> haven't checked yet whether they are in a released version).
> >>
> >> Yet another question: What should we tag things like infrastructure
> >> changes (Jenkins etc.)? A new "dummy" version "infra"? Similar for
> 0.89-fb
> >> issues (https://issues.apache.org/jira/browse/HBASE-4758) and some of
> >> the very old issues from when HBase was a Hadoop subproject (Hadoop
> >> 0.13.0). Then there are a bunch of pseudo versions like hbase-7290 (
> >> https://issues.apache.org/jira/browse/HBASE/fixforversion/12323900). We
> >> could also leave all those empty as they haven't really been released
> but
> >> it makes these hygiene tasks a lot harder when you can't distinguish
> >> between "forgotten to set" and "not planned for any release".
> >>
> >> I'd love to clean up a bit but I don't have proper permissions. Not sure
> >> if you can (or want to) only give those out for committers.
> >>
> >> On Mon, Nov 9, 2015 at 7:56 PM, Ted Yu <yuzhihong@gmail.com> wrote:
> >>
> >>> Lars:
> >>> Resolved issues for released versions should be closed.
> >>>
> >>> Cheers
> >>>
> >>> On Mon, Nov 9, 2015 at 11:52 AM, Lars Francke <lars.francke@gmail.com>
> >>> wrote:
> >>>
> >>> > Thanks guys!
> >>> >
> >>> > Another related question: Resolved vs. Closed? Should all resolved
> >>> issues
> >>> > (especially the old ones) be closed? If so I'd be happy to work a bit
> >>> on
> >>> > this but I don't have the proper permissions to do so.
> >>> >
> >>> > On Mon, Nov 9, 2015 at 5:15 PM, Andrew Purtell <apurtell@apache.org>
> >>> > wrote:
> >>> >
> >>> > > I believe that's correct. Anyway, I don't think we object to this
> >>> > practice.
> >>> > > Please feel free to help us with JIRA hygiene.
> >>> > >
> >>> > > On Mon, Nov 9, 2015 at 8:37 AM, Nick Dimiduk <ndimiduk@gmail.com>
> >>> wrote:
> >>> > >
> >>> > > > I think reopen and reclose is "how it is done."
> >>> > > >
> >>> > > > On Monday, November 9, 2015, Lars Francke <
> lars.francke@gmail.com>
> >>> > > wrote:
> >>> > > >
> >>> > > > > Thanks Nicolas, that's good to know. Probably fixed
in some
> kind
> >>> of
> >>> > > > > workflow then. Let's see if someone else has an idea.
> >>> > > > >
> >>> > > > > On Mon, Nov 9, 2015 at 10:12 AM, Nicolas Liochon <
> >>> nkeywal@gmail.com
> >>> > > > > <javascript:;>> wrote:
> >>> > > > >
> >>> > > > > > fwiw, I gave it a try and I can't change the resolution
> myself,
> >>> > even
> >>> > > > if I
> >>> > > > > > have the admin bit on the jira.
> >>> > > > > > But may be a jira guru can do something about this...
> >>> > > > > >
> >>> > > > > > On Mon, Nov 9, 2015 at 10:17 AM, Lars Francke <
> >>> > > lars.francke@gmail.com
> >>> > > > > <javascript:;>>
> >>> > > > > > wrote:
> >>> > > > > >
> >>> > > > > > > Hi,
> >>> > > > > > >
> >>> > > > > > > LarsG and I have been looking at a couple
of JIRA issues
> >>> (861 to
> >>> > be
> >>> > > > > > > precise) that are listed as Resolved &
Fixed but without a
> >>> Fix
> >>> > > > version.
> >>> > > > > > > Some of them should have been closed as Invalid
instead of
> >>> Fixed
> >>> > > and
> >>> > > > > > > various other problems.
> >>> > > > > > >
> >>> > > > > > > We weren't able to change the Resolution though.
We worked
> >>> around
> >>> > > it
> >>> > > > by
> >>> > > > > > > reopening and closing again. Is there any
other way to do
> >>> this
> >>> > or a
> >>> > > > set
> >>> > > > > > of
> >>> > > > > > > permissions you could give me and/or Lars
George?
> >>> > > > > > >
> >>> > > > > > > Thanks!
> >>> > > > > > >
> >>> > > > > > > Cheers,
> >>> > > > > > > Lars
> >>> > > > > > >
> >>> > > > > >
> >>> > > > >
> >>> > > >
> >>> > >
> >>> > >
> >>> > >
> >>> > > --
> >>> > > Best regards,
> >>> > >
> >>> > >    - Andy
> >>> > >
> >>> > > Problems worthy of attack prove their worth by hitting back. -
Piet
> >>> Hein
> >>> > > (via Tom White)
> >>> > >
> >>> >
> >>>
> >>
> >>
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message