I think we should consider releasing 1.4.2 to make fixes for
ACCUMULO-779, ACCUMULO-766, and ACCUMULO-409 available.  Thoughts?

Are there other fixes people would like to see in 1.4.2?  I think
ACCUMULO-798 would be good to get in.

I have been looking through the open tickets marked as fix for 1.4.2
trying to organize them.  I could use some help, some tickets I am not
sure what the status is.   Its frustrating that we can no longer see
svn commits in jira.  If you have a moment take a look at the open
1.4.2 tickets.   If you know that a ticket is complete or should be
moved to 1.5, update it please.

Keith

It would be really nice to have ACCUMULO-739 included in a stable 1.4.x
release as well - although I'm sure there will be some debate about this
since it enhances the API.
On Tue, Oct 9, 2012 at 6:56 PM, Keith Turner <[EMAIL PROTECTED]> wrote:

> I think we should consider releasing 1.4.2 to make fixes for
> ACCUMULO-779, ACCUMULO-766, and ACCUMULO-409 available.  Thoughts?
>
> Are there other fixes people would like to see in 1.4.2?  I think
> ACCUMULO-798 would be good to get in.
>
> I have been looking through the open tickets marked as fix for 1.4.2
> trying to organize them.  I could use some help, some tickets I am not
> sure what the status is.   Its frustrating that we can no longer see
> svn commits in jira.  If you have a moment take a look at the open
> 1.4.2 tickets.   If you know that a ticket is complete or should be
> moved to 1.5, update it please.
>
> Keith
>

Done.

On Thu, Oct 11, 2012 at 8:18 AM, Ed Kohlwey <[EMAIL PROTECTED]> wrote:
> It would be really nice to have ACCUMULO-739 included in a stable 1.4.x
> release as well - although I'm sure there will be some debate about this
> since it enhances the API.
>
>
> On Tue, Oct 9, 2012 at 6:56 PM, Keith Turner <[EMAIL PROTECTED]> wrote:
>
>> I think we should consider releasing 1.4.2 to make fixes for
>> ACCUMULO-779, ACCUMULO-766, and ACCUMULO-409 available.  Thoughts?
>>
>> Are there other fixes people would like to see in 1.4.2?  I think
>> ACCUMULO-798 would be good to get in.
>>
>> I have been looking through the open tickets marked as fix for 1.4.2
>> trying to organize them.  I could use some help, some tickets I am not
>> sure what the status is.   Its frustrating that we can no longer see
>> svn commits in jira.  If you have a moment take a look at the open
>> 1.4.2 tickets.   If you know that a ticket is complete or should be
>> moved to 1.5, update it please.
>>
>> Keith
>>

I want to make a few minor tweaks to the init.d scripts, which I plan on
doing tomorrow. After that, I definitely want to see a release as well.
On Oct 9, 2012 6:56 PM, "Keith Turner" <[EMAIL PROTECTED]> wrote:

> I think we should consider releasing 1.4.2 to make fixes for
> ACCUMULO-779, ACCUMULO-766, and ACCUMULO-409 available.  Thoughts?
>
> Are there other fixes people would like to see in 1.4.2?  I think
> ACCUMULO-798 would be good to get in.
>
> I have been looking through the open tickets marked as fix for 1.4.2
> trying to organize them.  I could use some help, some tickets I am not
> sure what the status is.   Its frustrating that we can no longer see
> svn commits in jira.  If you have a moment take a look at the open
> 1.4.2 tickets.   If you know that a ticket is complete or should be
> moved to 1.5, update it please.
>
> Keith
>

+1

I'll take a pass at the tickets tonight to see what I can see.

Adam
On Oct 9, 2012 6:56 PM, "Keith Turner" <[EMAIL PROTECTED]> wrote:

> I think we should consider releasing 1.4.2 to make fixes for
> ACCUMULO-779, ACCUMULO-766, and ACCUMULO-409 available.  Thoughts?
>
> Are there other fixes people would like to see in 1.4.2?  I think
> ACCUMULO-798 would be good to get in.
>
> I have been looking through the open tickets marked as fix for 1.4.2
> trying to organize them.  I could use some help, some tickets I am not
> sure what the status is.   Its frustrating that we can no longer see
> svn commits in jira.  If you have a moment take a look at the open
> 1.4.2 tickets.   If you know that a ticket is complete or should be
> moved to 1.5, update it please.
>
> Keith
>

+1

Also, I would like to hand over the task of creating the release to
Christopher Tubbs; he has more maven experience, and pays attention to
details.  I can work closely with him during the release process.
On Tue, Oct 9, 2012 at 6:56 PM, Keith Turner <[EMAIL PROTECTED]> wrote:

> I think we should consider releasing 1.4.2 to make fixes for
> ACCUMULO-779, ACCUMULO-766, and ACCUMULO-409 available.  Thoughts?
>
> Are there other fixes people would like to see in 1.4.2?  I think
> ACCUMULO-798 would be good to get in.
>
> I have been looking through the open tickets marked as fix for 1.4.2
> trying to organize them.  I could use some help, some tickets I am not
> sure what the status is.   Its frustrating that we can no longer see
> svn commits in jira.  If you have a moment take a look at the open
> 1.4.2 tickets.   If you know that a ticket is complete or should be
> moved to 1.5, update it please.
>
> Keith
>

While I appreciate the thought, (I certainly would be interested in
seeing the release process in action, so I know what Maven stuff I
might be able to do to automate/improve it), I don't have much time
this week (or next). I'll definitely want to get more involved in the
release when it comes time to release 1.5.0, though.

On Tue, Oct 9, 2012 at 7:48 PM, Eric Newton <[EMAIL PROTECTED]> wrote:
> +1
>
> Also, I would like to hand over the task of creating the release to
> Christopher Tubbs; he has more maven experience, and pays attention to
> details.  I can work closely with him during the release process.
>
>
> On Tue, Oct 9, 2012 at 6:56 PM, Keith Turner <[EMAIL PROTECTED]> wrote:
>
>> I think we should consider releasing 1.4.2 to make fixes for
>> ACCUMULO-779, ACCUMULO-766, and ACCUMULO-409 available.  Thoughts?
>>
>> Are there other fixes people would like to see in 1.4.2?  I think
>> ACCUMULO-798 would be good to get in.
>>
>> I have been looking through the open tickets marked as fix for 1.4.2
>> trying to organize them.  I could use some help, some tickets I am not
>> sure what the status is.   Its frustrating that we can no longer see
>> svn commits in jira.  If you have a moment take a look at the open
>> 1.4.2 tickets.   If you know that a ticket is complete or should be
>> moved to 1.5, update it please.
>>
>> Keith
>>

OK, but you are still on the hook for helping me get the maven release
automated!

-Eric

On Thu, Oct 11, 2012 at 6:34 PM, Christopher Tubbs <[EMAIL PROTECTED]> wrote:
> While I appreciate the thought, (I certainly would be interested in
> seeing the release process in action, so I know what Maven stuff I
> might be able to do to automate/improve it), I don't have much time
> this week (or next). I'll definitely want to get more involved in the
> release when it comes time to release 1.5.0, though.
>
> On Tue, Oct 9, 2012 at 7:48 PM, Eric Newton <[EMAIL PROTECTED]> wrote:
>> +1
>>
>> Also, I would like to hand over the task of creating the release to
>> Christopher Tubbs; he has more maven experience, and pays attention to
>> details.  I can work closely with him during the release process.
>>
>>
>> On Tue, Oct 9, 2012 at 6:56 PM, Keith Turner <[EMAIL PROTECTED]> wrote:
>>
>>> I think we should consider releasing 1.4.2 to make fixes for
>>> ACCUMULO-779, ACCUMULO-766, and ACCUMULO-409 available.  Thoughts?
>>>
>>> Are there other fixes people would like to see in 1.4.2?  I think
>>> ACCUMULO-798 would be good to get in.
>>>
>>> I have been looking through the open tickets marked as fix for 1.4.2
>>> trying to organize them.  I could use some help, some tickets I am not
>>> sure what the status is.   Its frustrating that we can no longer see
>>> svn commits in jira.  If you have a moment take a look at the open
>>> 1.4.2 tickets.   If you know that a ticket is complete or should be
>>> moved to 1.5, update it please.
>>>
>>> Keith
>>>

I can run continuous ingest and random walk test on a cluster for this release.

On Tue, Oct 9, 2012 at 7:48 PM, Eric Newton <[EMAIL PROTECTED]> wrote:
> +1
>
> Also, I would like to hand over the task of creating the release to
> Christopher Tubbs; he has more maven experience, and pays attention to
> details.  I can work closely with him during the release process.
>
>
> On Tue, Oct 9, 2012 at 6:56 PM, Keith Turner <[EMAIL PROTECTED]> wrote:
>
>> I think we should consider releasing 1.4.2 to make fixes for
>> ACCUMULO-779, ACCUMULO-766, and ACCUMULO-409 available.  Thoughts?
>>
>> Are there other fixes people would like to see in 1.4.2?  I think
>> ACCUMULO-798 would be good to get in.
>>
>> I have been looking through the open tickets marked as fix for 1.4.2
>> trying to organize them.  I could use some help, some tickets I am not
>> sure what the status is.   Its frustrating that we can no longer see
>> svn commits in jira.  If you have a moment take a look at the open
>> 1.4.2 tickets.   If you know that a ticket is complete or should be
>> moved to 1.5, update it please.
>>
>> Keith
>>

It would be cool if we could figure out how to include the accumulo-pig
code in this release -- or if we decide it shouldn't be included in core
releases, to release it separately.

Billie
On Tue, Oct 9, 2012 at 3:56 PM, Keith Turner <[EMAIL PROTECTED]> wrote:

> I think we should consider releasing 1.4.2 to make fixes for
> ACCUMULO-779, ACCUMULO-766, and ACCUMULO-409 available.  Thoughts?
>
> Are there other fixes people would like to see in 1.4.2?  I think
> ACCUMULO-798 would be good to get in.
>
> I have been looking through the open tickets marked as fix for 1.4.2
> trying to organize them.  I could use some help, some tickets I am not
> sure what the status is.   Its frustrating that we can no longer see
> svn commits in jira.  If you have a moment take a look at the open
> 1.4.2 tickets.   If you know that a ticket is complete or should be
> moved to 1.5, update it please.
>
> Keith
>

Forgive me if there was previous discussions I don't recall...

My first thought would be to treat it the same as the wikisearch code.
We could then bundle the appropriate version of accumulo-pig,
wikisearch, etc for the given release of Accumulo we're making. For
example, Accumulo-Pig-1.0 is compatible with Accumulo-1.4.2 and so forth.

It would be cool to create a community of addons/plugins/abstractions if
we can come up with some procedures for facilitating such projects. It
would also be much less onerous for users if we do some legwork to tie a
version of an extra to a version of Accumulo.

On 10/10/12 8:25 AM, Billie Rinaldi wrote:
> It would be cool if we could figure out how to include the accumulo-pig
> code in this release -- or if we decide it shouldn't be included in core
> releases, to release it separately.
>
> Billie
>
>
> On Tue, Oct 9, 2012 at 3:56 PM, Keith Turner <[EMAIL PROTECTED]> wrote:
>
>> I think we should consider releasing 1.4.2 to make fixes for
>> ACCUMULO-779, ACCUMULO-766, and ACCUMULO-409 available.  Thoughts?
>>
>> Are there other fixes people would like to see in 1.4.2?  I think
>> ACCUMULO-798 would be good to get in.
>>
>> I have been looking through the open tickets marked as fix for 1.4.2
>> trying to organize them.  I could use some help, some tickets I am not
>> sure what the status is.   Its frustrating that we can no longer see
>> svn commits in jira.  If you have a moment take a look at the open
>> 1.4.2 tickets.   If you know that a ticket is complete or should be
>> moved to 1.5, update it please.
>>
>> Keith
>>

On Wed, Oct 10, 2012 at 8:25 AM, Billie Rinaldi <[EMAIL PROTECTED]> wrote:
> It would be cool if we could figure out how to include the accumulo-pig
> code in this release -- or if we decide it shouldn't be included in core
> releases, to release it separately.

It would definitely be nice to make that available to users.  I am not
too familiar with the code.  What is the status of it?  Is it release
ready (feature complete, enough test, documentation)?

>
> Billie
>
>
> On Tue, Oct 9, 2012 at 3:56 PM, Keith Turner <[EMAIL PROTECTED]> wrote:
>
>> I think we should consider releasing 1.4.2 to make fixes for
>> ACCUMULO-779, ACCUMULO-766, and ACCUMULO-409 available.  Thoughts?
>>
>> Are there other fixes people would like to see in 1.4.2?  I think
>> ACCUMULO-798 would be good to get in.
>>
>> I have been looking through the open tickets marked as fix for 1.4.2
>> trying to organize them.  I could use some help, some tickets I am not
>> sure what the status is.   Its frustrating that we can no longer see
>> svn commits in jira.  If you have a moment take a look at the open
>> 1.4.2 tickets.   If you know that a ticket is complete or should be
>> moved to 1.5, update it please.
>>
>> Keith
>>

I went ahead and created the 1.4.3 tag in JIRA, so as we decide what fixes
to roll in/what to delay we can mark as such.

Additionally, there are a few tickets with patches available. I vaguely
recall a tool for reviewing patches, what's it called and/or how do I get
to it?

John

On Wed, Oct 10, 2012 at 12:26 PM, Keith Turner <[EMAIL PROTECTED]> wrote:

> On Wed, Oct 10, 2012 at 8:25 AM, Billie Rinaldi <[EMAIL PROTECTED]> wrote:
> > It would be cool if we could figure out how to include the accumulo-pig
> > code in this release -- or if we decide it shouldn't be included in core
> > releases, to release it separately.
>
> It would definitely be nice to make that available to users.  I am not
> too familiar with the code.  What is the status of it?  Is it release
> ready (feature complete, enough test, documentation)?
>
> >
> > Billie
> >
> >
> > On Tue, Oct 9, 2012 at 3:56 PM, Keith Turner <[EMAIL PROTECTED]> wrote:
> >
> >> I think we should consider releasing 1.4.2 to make fixes for
> >> ACCUMULO-779, ACCUMULO-766, and ACCUMULO-409 available.  Thoughts?
> >>
> >> Are there other fixes people would like to see in 1.4.2?  I think
> >> ACCUMULO-798 would be good to get in.
> >>
> >> I have been looking through the open tickets marked as fix for 1.4.2
> >> trying to organize them.  I could use some help, some tickets I am not
> >> sure what the status is.   Its frustrating that we can no longer see
> >> svn commits in jira.  If you have a moment take a look at the open
> >> 1.4.2 tickets.   If you know that a ticket is complete or should be
> >> moved to 1.5, update it please.
> >>
> >> Keith
> >>
>

On Wed, Oct 10, 2012 at 12:32 PM, John Vines <[EMAIL PROTECTED]> wrote:
> I went ahead and created the 1.4.3 tag in JIRA, so as we decide what fixes
> to roll in/what to delay we can mark as such.
>
> Additionally, there are a few tickets with patches available. I vaguely
> recall a tool for reviewing patches, what's it called and/or how do I get
> to it?

Apache has a review board instance https://reviews.apache.org/.  Is
that what you were thinking of?

>
> John
>
> On Wed, Oct 10, 2012 at 12:26 PM, Keith Turner <[EMAIL PROTECTED]> wrote:
>
>> On Wed, Oct 10, 2012 at 8:25 AM, Billie Rinaldi <[EMAIL PROTECTED]> wrote:
>> > It would be cool if we could figure out how to include the accumulo-pig
>> > code in this release -- or if we decide it shouldn't be included in core
>> > releases, to release it separately.
>>
>> It would definitely be nice to make that available to users.  I am not
>> too familiar with the code.  What is the status of it?  Is it release
>> ready (feature complete, enough test, documentation)?
>>
>> >
>> > Billie
>> >
>> >
>> > On Tue, Oct 9, 2012 at 3:56 PM, Keith Turner <[EMAIL PROTECTED]> wrote:
>> >
>> >> I think we should consider releasing 1.4.2 to make fixes for
>> >> ACCUMULO-779, ACCUMULO-766, and ACCUMULO-409 available.  Thoughts?
>> >>
>> >> Are there other fixes people would like to see in 1.4.2?  I think
>> >> ACCUMULO-798 would be good to get in.
>> >>
>> >> I have been looking through the open tickets marked as fix for 1.4.2
>> >> trying to organize them.  I could use some help, some tickets I am not
>> >> sure what the status is.   Its frustrating that we can no longer see
>> >> svn commits in jira.  If you have a moment take a look at the open
>> >> 1.4.2 tickets.   If you know that a ticket is complete or should be
>> >> moved to 1.5, update it please.
>> >>
>> >> Keith
>> >>
>>

On Tue, Oct 9, 2012 at 3:56 PM, Keith Turner <[EMAIL PROTECTED]> wrote:

> I think we should consider releasing 1.4.2 to make fixes for
> ACCUMULO-779, ACCUMULO-766, and ACCUMULO-409 available.  Thoughts?
>
> Are there other fixes people would like to see in 1.4.2?  I think
> ACCUMULO-798 would be good to get in.
>
> I have been looking through the open tickets marked as fix for 1.4.2
> trying to organize them.  I could use some help, some tickets I am not
> sure what the status is.   Its frustrating that we can no longer see
> svn commits in jira.  If you have a moment take a look at the open
> 1.4.2 tickets.   If you know that a ticket is complete or should be
> moved to 1.5, update it please.
>

I'd like to make sure ACCUMULO-507 works as that changed how we pass ranges
to MapReduce jobs.  Does anyone have a job that was failing due to too many
ranges that they could test with the new version?

You can take a look at the changes if you search for "ACCUMULO-507
to:commits" in gmail.  I agree it is unfortunate that we can't view commits
in JIRA anymore.

Billie

>
> Keith
>