accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Billie Rinaldi <billie.rina...@gmail.com>
Subject Re: [DISCUSS] any blockers on current release lines?
Date Thu, 15 Jun 2017 14:26:08 GMT
On Wed, Jun 14, 2017 at 5:10 AM, Michael Wall <mjwall@gmail.com> wrote:

> I have one (https://issues.apache.org/jira/browse/ACCUMULO-4615) but it is
> not a blocker, so nevermind.
>
> Anyone jira savvy know what's up with the landing page for
> https://issues.apache.org/jira/projects/ACCUMULO.  For me, it goes to a
> kanban board Billie created for an Accumulo Hackathon in 2016.  I don't
> really care where the landing page page, I just think it shouldn't be some
> from 2016.
>

I noticed this with YARN as well; the default YARN page goes to some random
kanban board now. I guess they must have changed some default setting for
the entire JIRA. I am not sure which setting, so we'll have to look into it.


>
> On Tue, Jun 13, 2017 at 5:37 PM Michael Wall <mjwall@gmail.com> wrote:
>
> > I've got one maybe two for 1.8, but right now jira seems funky.
> > https://issues.apache.org/jira/browse/ACCUMULO is going to some Accumulo
> > Hackathon 2016 kanban board.  Any know anything about that.  I'll look
> > again tonight and try to find those tickets
> >
> > I have been wanting to talk about the tickets in general and how many are
> > currently open.  Many haven't been looked at in some time and just get
> > moved from "next release" to "next release".  I'll wait until this
> > discussion is done though.
> >
> > On Tue, Jun 13, 2017 at 5:22 PM Christopher <ctubbsii@apache.org> wrote:
> >
> >> Usually such discussions are in the context of an anticipated release.
> Are
> >> you planning to champion a release soon? I'd be in favor of a
> maintenance
> >> release or two.
> >>
> >> On Tue, Jun 13, 2017 at 4:57 PM Sean Busbey <busbey@cloudera.com>
> wrote:
> >>
> >> > Right, I believe we'd be pushing out any non-completed issues to a
> >> > future release. Presumably if any of those TODOs required waiting for
> >> > a release they'd be marked blocker, or someone here would have them in
> >> > mind?
> >> >
> >> > On Tue, Jun 13, 2017 at 12:45 PM, Christopher <ctubbsii@apache.org>
> >> wrote:
> >> > > Link to issues, by release branch:
> >> > >
> >> >
> >> https://issues.apache.org/jira/projects/ACCUMULO?
> selectedItem=com.atlassian.jira.jira-projects-plugin:release-page
> >> > >
> >> > > On Tue, Jun 13, 2017 at 3:09 PM Sean Busbey <busbey@apache.org>
> >> wrote:
> >> > >
> >> > >> Here's how we're doing on lag for releases:
> >> > >>
> >> > >> * branch-1.7, last maintenance release March 25th 2017, 9 issues
> >> marked
> >> > >> done, no blockers
> >> > >> * branch-1.8, last maintenance release Feb 26th 2017, 14 issues
> >> marked
> >> > >> done, no blockers
> >> > >> * master, last minor release September 6th 2016, last major release
> >> May
> >> > >> 2014, 80 issues marked done, 3 things marked blocker
> >> > >>
> >> > >> Anyone know of any other blockers on releases right now?
> >> > >>
> >> > >> Folks have time for a discussion about wether or not we should
keep
> >> > things
> >> > >> currently marked blocker as blocker?
> >> > >>
> >> >
> >> >
> >> >
> >> > --
> >> > busbey
> >> >
> >>
> >
>

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