You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by Michael Wall <mj...@gmail.com> on 2017/01/09 19:29:40 UTC
Time for a 1.8.1?
Thinking it is time for a 1.8.1 release. I'm happy to be the release
manager since I did the 1.8.0. Just trying to get a sense for where people
think we are.
Mike
Re: Time for a 1.8.1?
Posted by Josh Elser <jo...@gmail.com>.
Sorry, +1 to a release.
Will try to devote some time to it.
Thanks for driving.
Michael Wall wrote:
> Ok, so I got one +1 and nothing else. I assume that mean no concerns and
> start going through jira tickets. Is anyone going to be available to help
> test the RC?
>
> Mike
>
> On Mon, Jan 9, 2017 at 2:35 PM, Christopher<ct...@apache.org> wrote:
>
>> +1 for a 1.8.1 and a 1.7.3 both within the next 2 weeks, if we can. I can
>> help.
>>
>> There are a few outstanding bugs marked for 1.7.3 (59) and 1.8.1 (161), but
>> most of those can be punted to a future bugfix release. We don't need to
>> wait on them to push out an update. We just need to know people will be
>> willing to try out / test these release candidates to get the current
>> outstanding fixes pushed.
>>
>> On Mon, Jan 9, 2017 at 2:29 PM Michael Wall<mj...@gmail.com> wrote:
>>
>>> Thinking it is time for a 1.8.1 release. I'm happy to be the release
>>> manager since I did the 1.8.0. Just trying to get a sense for where
>> people
>>> think we are.
>>>
>>> Mike
>>>
>> --
>> Christopher
>>
>
Re: Time for a 1.8.1?
Posted by Michael Wall <mj...@gmail.com>.
There are 8 tickets left in jira for 1.8.1 (
https://issues.apache.org/jira/issues/?jql=project%20%3D%20ACCUMULO%20AND%20fixVersion%20%3D%201.8.1%20AND%20resolution%20%3D%20Unresolved%20
)
https://issues.apache.org/jira/browse/ACCUMULO-4553 - DeleteTable repo not
replayable -Assigned to John Vines but Ed is looking at to see if related
to 4574
https://issues.apache.org/jira/browse/ACCUMULO-4574 - Online fate bug -
Assigned to Ed
https://issues.apache.org/jira/browse/ACCUMULO-4446 - Logging of
getMonitorLock - Assigned to Luis, ready for a merge which I can do
https://issues.apache.org/jira/browse/ACCUMULO-4342 - Stopping tabletserver
with dynamic ports - Assigned to me cause I have an interest
https://issues.apache.org/jira/browse/ACCUMULO-4479 - UPGRADING.md missed
1.8 info - Assigned to me
https://issues.apache.org/jira/browse/ACCUMULO-4480 - Docs on user testing
- Assigned to me
https://issues.apache.org/jira/browse/ACCUMULO-4333 - Follow on for GC WAL
bug I - Assigned to me since I did 4157
https://issues.apache.org/jira/browse/ACCUMULO-4432 - Assert ITs are
categories - Assigned to Christopher
Please evaluate all new tickets and put in 1.8.2 unless they really need to
be in 1.8.1. If I moved a ticket you need in 1.8.1, sorry please move it
back.
Thanks
On Thu, Jan 26, 2017 at 8:21 AM Michael Wall <mj...@gmail.com> wrote:
> I will be moving tickets from 1.8.1 to 1.8.2 this morning. I know Ed has
> a couple that I'll leave 1.8.1. If I move something you needed in 1.8.1,
> move it back.
>
> On Thu, Jan 19, 2017 at 11:44 AM Mike Miller <mi...@gmail.com>
> wrote:
>
> I can do some testing. I can use the Wikisearch stuff I recently fixed to
> test ingest and query.
>
> On Thu, Jan 19, 2017 at 8:29 AM, DAVID MARION <dl...@comcast.net>
> wrote:
>
> > I can test the RC with Timely. We found and fixed an issue in the 1.8.0
> > release that way.
> >
> > >
> > > On January 19, 2017 at 8:08 AM Michael Wall <mj...@gmail.com>
> > wrote:
> > >
> > > Ok, so I got one +1 and nothing else. I assume that mean no
> concerns
> > and
> > > start going through jira tickets. Is anyone going to be available
> to
> > help
> > > test the RC?
> > >
> > > Mike
> > >
> > > On Mon, Jan 9, 2017 at 2:35 PM, Christopher <ct...@apache.org>
> > wrote:
> > >
> > > > >
> > > > +1 for a 1.8.1 and a 1.7.3 both within the next 2 weeks, if
> we
> > can. I can
> > > > help.
> > > >
> > > > There are a few outstanding bugs marked for 1.7.3 (59) and
> > 1.8.1 (161), but
> > > > most of those can be punted to a future bugfix release. We
> > don't need to
> > > > wait on them to push out an update. We just need to know
> > people will be
> > > > willing to try out / test these release candidates to get the
> > current
> > > > outstanding fixes pushed.
> > > >
> > > > On Mon, Jan 9, 2017 at 2:29 PM Michael Wall <
> mjwall@gmail.com>
> > wrote:
> > > >
> > > > > > >
> > > > > Thinking it is time for a 1.8.1 release. I'm happy to
> be
> > the release
> > > > > manager since I did the 1.8.0. Just trying to get a
> > sense for where
> > > > > people
> > > > > think we are.
> > > > >
> > > > > Mike
> > > > >
> > > > > --
> > > > > Christopher
> > > > >
> > > > > > >
> > > > >
> >
>
>
Re: Time for a 1.8.1?
Posted by Michael Wall <mj...@gmail.com>.
I will be moving tickets from 1.8.1 to 1.8.2 this morning. I know Ed has a
couple that I'll leave 1.8.1. If I move something you needed in 1.8.1,
move it back.
On Thu, Jan 19, 2017 at 11:44 AM Mike Miller <mi...@gmail.com>
wrote:
> I can do some testing. I can use the Wikisearch stuff I recently fixed to
> test ingest and query.
>
> On Thu, Jan 19, 2017 at 8:29 AM, DAVID MARION <dl...@comcast.net>
> wrote:
>
> > I can test the RC with Timely. We found and fixed an issue in the 1.8.0
> > release that way.
> >
> > >
> > > On January 19, 2017 at 8:08 AM Michael Wall <mj...@gmail.com>
> > wrote:
> > >
> > > Ok, so I got one +1 and nothing else. I assume that mean no
> concerns
> > and
> > > start going through jira tickets. Is anyone going to be available
> to
> > help
> > > test the RC?
> > >
> > > Mike
> > >
> > > On Mon, Jan 9, 2017 at 2:35 PM, Christopher <ct...@apache.org>
> > wrote:
> > >
> > > > >
> > > > +1 for a 1.8.1 and a 1.7.3 both within the next 2 weeks, if
> we
> > can. I can
> > > > help.
> > > >
> > > > There are a few outstanding bugs marked for 1.7.3 (59) and
> > 1.8.1 (161), but
> > > > most of those can be punted to a future bugfix release. We
> > don't need to
> > > > wait on them to push out an update. We just need to know
> > people will be
> > > > willing to try out / test these release candidates to get the
> > current
> > > > outstanding fixes pushed.
> > > >
> > > > On Mon, Jan 9, 2017 at 2:29 PM Michael Wall <
> mjwall@gmail.com>
> > wrote:
> > > >
> > > > > > >
> > > > > Thinking it is time for a 1.8.1 release. I'm happy to
> be
> > the release
> > > > > manager since I did the 1.8.0. Just trying to get a
> > sense for where
> > > > > people
> > > > > think we are.
> > > > >
> > > > > Mike
> > > > >
> > > > > --
> > > > > Christopher
> > > > >
> > > > > > >
> > > > >
> >
>
Re: Time for a 1.8.1?
Posted by Mike Miller <mi...@gmail.com>.
I can do some testing. I can use the Wikisearch stuff I recently fixed to
test ingest and query.
On Thu, Jan 19, 2017 at 8:29 AM, DAVID MARION <dl...@comcast.net> wrote:
> I can test the RC with Timely. We found and fixed an issue in the 1.8.0
> release that way.
>
> >
> > On January 19, 2017 at 8:08 AM Michael Wall <mj...@gmail.com>
> wrote:
> >
> > Ok, so I got one +1 and nothing else. I assume that mean no concerns
> and
> > start going through jira tickets. Is anyone going to be available to
> help
> > test the RC?
> >
> > Mike
> >
> > On Mon, Jan 9, 2017 at 2:35 PM, Christopher <ct...@apache.org>
> wrote:
> >
> > > >
> > > +1 for a 1.8.1 and a 1.7.3 both within the next 2 weeks, if we
> can. I can
> > > help.
> > >
> > > There are a few outstanding bugs marked for 1.7.3 (59) and
> 1.8.1 (161), but
> > > most of those can be punted to a future bugfix release. We
> don't need to
> > > wait on them to push out an update. We just need to know
> people will be
> > > willing to try out / test these release candidates to get the
> current
> > > outstanding fixes pushed.
> > >
> > > On Mon, Jan 9, 2017 at 2:29 PM Michael Wall <mj...@gmail.com>
> wrote:
> > >
> > > > > >
> > > > Thinking it is time for a 1.8.1 release. I'm happy to be
> the release
> > > > manager since I did the 1.8.0. Just trying to get a
> sense for where
> > > > people
> > > > think we are.
> > > >
> > > > Mike
> > > >
> > > > --
> > > > Christopher
> > > >
> > > > > >
> > > >
>
Re: Time for a 1.8.1?
Posted by DAVID MARION <dl...@comcast.net>.
I can test the RC with Timely. We found and fixed an issue in the 1.8.0 release that way.
>
> On January 19, 2017 at 8:08 AM Michael Wall <mj...@gmail.com> wrote:
>
> Ok, so I got one +1 and nothing else. I assume that mean no concerns and
> start going through jira tickets. Is anyone going to be available to help
> test the RC?
>
> Mike
>
> On Mon, Jan 9, 2017 at 2:35 PM, Christopher <ct...@apache.org> wrote:
>
> > >
> > +1 for a 1.8.1 and a 1.7.3 both within the next 2 weeks, if we can. I can
> > help.
> >
> > There are a few outstanding bugs marked for 1.7.3 (59) and 1.8.1 (161), but
> > most of those can be punted to a future bugfix release. We don't need to
> > wait on them to push out an update. We just need to know people will be
> > willing to try out / test these release candidates to get the current
> > outstanding fixes pushed.
> >
> > On Mon, Jan 9, 2017 at 2:29 PM Michael Wall <mj...@gmail.com> wrote:
> >
> > > > >
> > > Thinking it is time for a 1.8.1 release. I'm happy to be the release
> > > manager since I did the 1.8.0. Just trying to get a sense for where
> > > people
> > > think we are.
> > >
> > > Mike
> > >
> > > --
> > > Christopher
> > >
> > > > >
> > >
Re: Time for a 1.8.1?
Posted by Michael Wall <mj...@gmail.com>.
Ok, so I got one +1 and nothing else. I assume that mean no concerns and
start going through jira tickets. Is anyone going to be available to help
test the RC?
Mike
On Mon, Jan 9, 2017 at 2:35 PM, Christopher <ct...@apache.org> wrote:
> +1 for a 1.8.1 and a 1.7.3 both within the next 2 weeks, if we can. I can
> help.
>
> There are a few outstanding bugs marked for 1.7.3 (59) and 1.8.1 (161), but
> most of those can be punted to a future bugfix release. We don't need to
> wait on them to push out an update. We just need to know people will be
> willing to try out / test these release candidates to get the current
> outstanding fixes pushed.
>
> On Mon, Jan 9, 2017 at 2:29 PM Michael Wall <mj...@gmail.com> wrote:
>
> > Thinking it is time for a 1.8.1 release. I'm happy to be the release
> > manager since I did the 1.8.0. Just trying to get a sense for where
> people
> > think we are.
> >
> > Mike
> >
> --
> Christopher
>
Re: Time for a 1.8.1?
Posted by Christopher <ct...@apache.org>.
+1 for a 1.8.1 and a 1.7.3 both within the next 2 weeks, if we can. I can
help.
There are a few outstanding bugs marked for 1.7.3 (59) and 1.8.1 (161), but
most of those can be punted to a future bugfix release. We don't need to
wait on them to push out an update. We just need to know people will be
willing to try out / test these release candidates to get the current
outstanding fixes pushed.
On Mon, Jan 9, 2017 at 2:29 PM Michael Wall <mj...@gmail.com> wrote:
> Thinking it is time for a 1.8.1 release. I'm happy to be the release
> manager since I did the 1.8.0. Just trying to get a sense for where people
> think we are.
>
> Mike
>
--
Christopher