changes since rc0 and updated the 2.1.4 release notes.
> Pushed two commits to the website repo.
>
> https://github.com/apache/accumulo/compare/2.1.4-rc0...2.1.4-rc2
>
> On Tue, Aug 12, 2025 at 9:37 PM Christopher wrote:
>
> > Accumulo Developers,
> >
> > Please con
(https://github.com/apache/accumulo/issues/5809)
On Tue, Aug 19, 2025 at 5:32 PM Keith Turner wrote:
>
> +1
>
> Verified tar ball hashes and signatures.
> Built src tar and compared src tar to branch.
> Looked at changes since rc0.
>
> On Tue, Aug 12, 2025 at 9:
still time for others to test and vote on these artifacts.
On Fri, Aug 15, 2025 at 4:42 PM Christopher wrote:
>
> I wouldn't consider it a blocker. It's still the same license, just a
> version typo. And it's only for convenience. It's easy to check the
> license
> JQuery was updated to version 3.7.1 in #3754, but the LICENSE file still
> refers to version 3.6.1. It looks like the license is the same though. I
> don't know if the version number being incorrect is enough to veto this or
> not.
>
> On Thu, Aug 14, 2025 at 5:17 PM Christop
sily.
> Thoughts on whether this issue is important enough to fix in 2.1.4 and
> create another release candidate, or whether we include it in a 2.1.5
> release?
>
> On Tue, Aug 12, 2025 at 9:38 PM Christopher wrote:
>
> > Accumulo Developers,
> >
> > Pl
Accumulo Developers,
Please consider the following candidate for Apache Accumulo 2.1.4.
(note: rc1 was abandoned before an email was produced, so that's why
you didn't see it, in case you're wondering)
Git Commit:
e557fd95fedbce9988ea95b685f13a2d469ca34c
Branch:
2.1.4-rc2
If this vote pa
Sorry I didn't see this question until now. My response would have
been "no", I thought you covered it adequately in the Accumulo report.
On Wed, Jul 9, 2025 at 9:39 PM dev1 wrote:
>
> The report was filed without changes – thanks for the reviews
>
> Ed Coleman
>
>
Since Fluo got a board report notice as well, due to the pending
actions to dispose of its permissions and complete the transfer, I
submitted a report for Fluo which simply said:
## Description:
The mission of Apache Fluo is the creation and maintenance of software related
to the storage and incre
Accumulo Developers,
This is a test release candidate only. There is no need to vote.
However, please consider using this for testing purposes, to provide
feedback on the current state of 2.1.4-SNAPSHOT, so we can prepare a
real release candidate soon. Please disregard further references to
voting
On Tue, Jun 10, 2025 at 7:52 PM Dave Marion wrote:
>
> I made a comment regarding the TableNotFoundException hierarchy at [0]. I
> don't understand why our specific exceptions (TNFE for example) don't
> extend AccumuloException. If the hierarchy is changed in our Exception
Mainly because it's a b
project community.
Christopher
On behalf of the Accumulo PMC
The board asked for a report this month to check on the progress of
the Fluo migration to Accumulo that they approved last month. I
volunteered to help draft it for Ed. It is due at the end of today, so
please don't delay if you have suggested edits. Here is my draft of
that report for peer review
Hello Apache Fluo users and developers,
The Apache Fluo project is now operating under new management. During
the April 2025 meeting, the ASF Board approved the transition of the
Fluo project to be managed by the Accumulo PMC. The Fluo PMC is
dissolved.
For users and contributors, little will cha
Okay, seems like there's no changes needed, so I'll send this out shortly.
On Wed, Apr 30, 2025 at 2:22 PM Dominic Garguilo wrote:
>
> Looks good!
>
> On Wed, Apr 30, 2025 at 1:14 PM Daniel Roberts wrote:
>
> > Looks good to me!
> >
> > On Tue,
Accumulo Devs,
See the following draft of an announcement I intend to send to the
Fluo Dev list, the Accumulo Dev list (this list), the Accumulo user
list, and the Apache Rya dev list (a project that uses Fluo). Please
let me know if you have any suggested changes before I send it in the
coming da
st for official Apache
> business and it remains a channel for users to contact us.
>
> ## Links
>
> [1] https://lists.apache.org/thread/dcf5b1ypb6ynlklkrfs7r6dbmg9wqsoh
>
>
> [2] https://lists.apache.org/thread/z6h10zzbx6m0lfdr09d45o851tl0xsvl
>
> [3] https://li
rom: Dave Marion
> Date: Monday, April 7, 2025 at 3:49 PM
> To: dev@accumulo.apache.org
> Subject: Re: Accumulo quarterly report - due Wednesday 4/9th
> Looks good to me. Removing the fluo content, as suggested, is also fine
> with me.
>
> On Mon, Apr 7, 2025 at 3:29 PM Christopher
Looks fine to me, but I'm wondering if we should omit the Fluo portions
from this, in order to avoid spreading the conversation across too many
forums. Maybe just a simple statement like "see Fluo report" and I can
include the details from your summary of the matter on the Fluo report
instead.
On
ve a few manual
steps. However, you'll still need to merge the upstream branch onto your
own local branch for cases like this.
On Wed, Mar 12, 2025 at 2:25 PM Christopher wrote:
> There aren't really any objections to this, so I'm going to start working
> toward
ge anything new into it. Merges coming from 2.1 can
go straight into the main branch now.
On Tue, Mar 11, 2025 at 10:08 PM Christopher wrote:
> It could be done before a 2.1.4 release, but I agree should that be soon.
> For this, I'm more concerned about how it's going to mess up
branch, when should we change our merge
> strategy
> > for 2.1 changes?
> >
> > There's a couple of on-going efforts that are resolved in preparation for
> > the 2.1.4 release.
> > Should we continue to merge them forward via the 3.1 branch or just
> >
When the 3.1-deprecations branch
> does exists will need to agree on how to do merges from 2.1. Seems like
> merges from 2.1 will not need to go through the 3.1-deprecations branch in
> general, could on an as needed basis though.
>
>
>
> On Thu, Mar 6, 2025 at 5:05 PM Christoph
or license issues
(like updating copyright dates in NOTICE files)
6. Release 3.1.0 before 4.0.0 is released (at some point before... not
necessarily urgent)
On Wed, Mar 5, 2025 at 6:44 PM Christopher wrote:
> Great idea! I don't know how well it will work in practice... I remember a
>
intain semver compliance, then we could create a new 3.1
> branch off of the 3.0 tag that contains solely the deprecations and release
> that. That 3.1 version would require very little testing.
>
> On Wed, Mar 5, 2025 at 2:47 PM Christopher wrote:
>
> > I was recently in a conv
I was recently in a conversation where the question was raised about what
future versions of Accumulo are expected.
There was a time during the elasticity/4.0 development, before that was
merged into the main branch that I thought it would be a good idea to have
a 3.1 LTM release. However, most of
Looks good to me as well.
On Mon, Jan 6, 2025 at 11:24 AM Dominic Garguilo
wrote:
> Looks good to me. Thanks Ed!
>
> On Mon, Jan 6, 2025 at 11:17 AM Kevin Rathbun wrote:
>
> > Thanks Ed! Looks good to me.
> >
> > On 2025/01/06 15:31:33 Dave Marion wrote:
> > > Looks good. Thanks Ed!
> > >
> > >
y
branch, but I reopened them and updated them to target the main
branch. I merged one of them (#289) and commented on a few others
which I think are probably okay to merge.
Regards,
Christopher
LGTM too
On Tue, Oct 1, 2024 at 7:31 AM Daniel Roberts wrote:
> Thanks Ed!
> I reviewed it and I didn't see any issues other than the previously
> mentioned link issue in [6]
>
>
>
>
>
>
> On Tue, Oct 1, 2024 at 7:24 AM Dave Marion wrote:
>
> > Looks good. Thanks Ed!
> >
> > On Sun, Sep 29, 202
Oh, there's a typo in the last link ([6])
On Mon, Sep 30, 2024 at 6:09 PM Christopher wrote:
>
> Looks good to me. I would probably change the reference to the "main
> GitHub branch" to "main branch in git", since it's not a
> GitHub-specific thing.
Looks good to me. I would probably change the reference to the "main
GitHub branch" to "main branch in git", since it's not a
GitHub-specific thing. But it's not important.
On Sun, Sep 29, 2024 at 2:40 PM Ed Coleman wrote:
>
> The Accumulo community decided to draft the Apache community reports o
ut I don't believe the removal of Kerberos
> would be a blocker since acceptable alternatives exist within the
> ecosystem.
>
> Thanks,
> Marc
>
> On Fri, Aug 23, 2024 at 3:38 PM Christopher Shannon <
> christopher.l.shan...@gmail.com> wrote:
>
> > To provide
ey can.
>
> Best of luck gathering feedback.
>
> Thanks,
> Marc
>
>
> On Fri, Aug 23, 2024 at 1:34 PM Christopher wrote:
>
>> The ASF doesn't have a formal system on which we could reliably conduct
>> such a poll. This is just an informal open discussion with
best effort attempt to get some initial feedback.
On Fri, Aug 23, 2024, 13:20 Marc Parisi wrote:
> Would the data be any less useful if this were an anonymous poll?
>
>
>
> On Fri, Aug 23, 2024 at 12:52 PM Christopher Shannon <
> christopher.l.shan...@gmail.com> wrote:
&
Oops, I cc'd the wrong dev list so make sure responses go to the right one.
On Fri, Aug 23, 2024 at 12:50 PM Christopher Shannon <
christopher.l.shan...@gmail.com> wrote:
> Hello Apache Accumulo Users,
>
> The Accumulo PMC would like to get some feedback on how widely used
&
(soon-ish,
but not immediately)
* Update accumulo-testing to support elasticity
Of these, the only immediate actions we're planning on taking is the
branching in the "GitHub updates" section above. Both Dave Marion and
Christopher Tubbs said they'd be willing to do this, and wil
1 PM Kevin Rathbun wrote:
>
> Looks good to me.
>
> One very minor thing I noticed is the two links at the bottom do not include
> the trailing `/`. Maybe can remove this or add it to the link itself?
>
> On 2024/08/13 22:32:24 Christopher wrote:
> > Hi Accumulo Devs,
>
Hi Accumulo Devs,
Please check the following release announcement for errors before it
is sent to annou...@apache.org and u...@accumulo.apache.org . This
will conclude the post-vote release tasks at
https://github.com/apache/accumulo/issues/4803
***
The Apache Accumulo project is pleased to annou
, Aug 12, 2024 at 3:48 PM Christopher wrote:
>
> This vote passes with 9 +1s and no other votes.
>
> The post-vote release tasks are tracked on
> https://github.com/apache/accumulo/issues/4803
>
> On Mon, Aug 12, 2024 at 3:44 PM Christopher wrote:
> >
> > My vote
This vote passes with 9 +1s and no other votes.
The post-vote release tasks are tracked on
https://github.com/apache/accumulo/issues/4803
On Mon, Aug 12, 2024 at 3:44 PM Christopher wrote:
>
> My vote is +1
>
> I checked:
>
> * sigs/checksums for all artifacts
> * bi
ug 7, 2024 at 8:24 PM Christopher wrote:
>
> I plan on closing this vote tomorrow after making my own vote.
>
> On Wed, Jul 31, 2024 at 9:52 PM Daniel Roberts wrote:
> >
> > +1 binding
> >
> > ran "mvn clean package verify" on src contents
> >
> >
> > * verified sunny day tests pass with "mvn clean verify -Psunny" (src)
> > * verified signatures (bin + src)
> > * verified hashes (bin + src)
> > * verified LICENSE and NOTICE files both present at top-level (bin + src)
> > * verified no binary fi
2024 at 3:55 PM Dominic Garguilo
wrote:
> +1 binding
>
> * verified hashes
> * ran mvn clean verify -Psunny on tar which passes cleanly
> * stood up an instance via uno and did some basic table operations and
> ingest with no issues
>
> On Mon, Jul 29, 2024 at 2:10 AM Ch
Accumulo Developers,
Please consider the following candidate for Apache Accumulo 2.1.3.
Git Commit:
8f52dd10f7cbfef192c9cc431543619b7072139a
Branch:
2.1.3-rc1
If this vote passes, a gpg-signed tag will be created using:
git tag -f -s -m 'Apache Accumulo 2.1.3' rel/2.1.3 \
8f52dd1
cker. If it's something you're working on, or created and
nobody's working on, and you know it can wait, then feel free to move
it to the 2.1.4 milestone.
https://github.com/apache/accumulo/milestones/2.1.3
https://github.com/apache/accumulo/milestones/2.1.4
Thanks,
Christopher
Welcome, and congrats Kevin!
On Fri, Jul 26, 2024 at 9:46 AM Daniel Roberts wrote:
> Welcome Kevin!!
>
> On Fri, Jul 26, 2024, 9:23 AM Dave Marion wrote:
>
> > welcome Kevin!
> >
> > On Thu, Jul 25, 2024 at 6:37 PM Christopher wrote:
> >
> > >
Hi Accumulo Devs,
I just want to offer my welcome to our newest committer and PMC
member, Kevin Rathbun!
ASF Id: krathbun
GitHub: kevinrr888
Best regards,
Christopher
would be appreciated.
Thanks,
Christopher
ojects. Other times, it may
be useful to keep the project around for future reference. In those
cases, just close it. We actually have a few that probably can be
deleted, but I'm not sure if anybody's using them, so I have just left
them alone as a closed project.
To summarize the most important bits:
* Follow the naming convention,
* Make sure it's Public,
* Set Base role to Read,
* Add accumulo-committers as Admin,
* Link to apache/accumulo repo
I hope these tips help.
Kind regards,
Christopher
;m assuming that the Elasticity project (new) will
> remain as-is for now, right? Thanks Christopher.
>
> On Wed, Jul 10, 2024 at 12:14 PM Christopher wrote:
>
> > So, it sounds like everybody who weighed in was okay with my proposed
> > approach. Dave suggested an alternat
notes in the past I have looked
> > through all the commits since the last release and found notable commits
> > that were not properly tagged in the issue system.
> >
> > On Tue, Jul 2, 2024 at 7:05 PM Christopher wrote:
> >
> > > Hi Accumulo Devs,
> > >
LGTM
On Mon, Jul 8, 2024 at 5:19 PM Dominic Garguilo
wrote:
> Looks good! Thanks!
>
> On Mon, Jul 8, 2024 at 5:13 PM Daniel Roberts wrote:
> >
> > Minor update to the "Other" section:
> > ---
> > During the past quarter, Accumulo had an opportunity to perform at-scale
> > testing of 2.1 experim
On Wed, Jul 3, 2024 at 5:37 PM Dave Marion wrote:
>
> Comments inline.
>
> On Wed, Jul 3, 2024 at 4:33 PM Christopher wrote:
>
> > I think you are proposing a single "2.1.3" issue, for example, whose
> > body somewhere (top comment, perhaps) is manually u
e the post-vote release checklist[1] issues that we have. Yes, this
> means that the developer is going to have to update some other number of
> tickets when creating a ticket or PR. But, I think it might give us back
> the functionality that we had.
>
> [1] https://github.com/a
No objections from me, I am +1 for going with the single milestone approach
as it seems like the best way for now unless Github makes improvements.
On Tue, Jul 2, 2024 at 7:05 PM Christopher wrote:
> Hi Accumulo Devs,
>
> I wanted to bring to everybody's attention that GitHub
d prefer not
to rely on the automatic migration from classic to new projects
because there are too many unknowns and too many things can go wrong.
So, are there any objections to going with the single milestone
approach I've described?
Or perhaps you feel strongly that the new projects *are* best fo
TEST TEST TEST
Accumulo Developers,
The following is a test release candidate vote for 2.1.3. You do NOT
need to vote on this. It will be discarded, and a new release
candidate will be made when a release candidate is ready for voting.
Please consider the following candidate for Apache Accumulo
I agree with Dave that it could be moved out of Other and into the
Project activity and Releases sections. But I don't know that it
matters much.
On Fri, Apr 5, 2024 at 4:21 PM Daniel Roberts wrote:
>
> Report looks good!
>
> On Fri, Apr 5, 2024 at 3:41 PM Dave Marion wrote:
>
> > I'm fine with
LGTM
On Tue, Apr 2, 2024 at 11:09 AM Ed Coleman wrote:
>
> Thanks - I incorporated the suggestions.
>
> On 2024/04/02 14:57:56 Mark Owens wrote:
> > LGTM
> >
> > I have two small grammatical suggestions you can consider if you'd like.
> >
> > > The difference between committers and PMC members is
24 at 7:53 AM Dave Marion wrote:
> Christopher,
>
> Regarding your issues, notes, etc.:
>
> 1. IIRC versions 1 and 2 were not built correctly and I did not restart
> the numbering for the first good build.
> 2. The build script gave me the option of where to put the branch
ran the example and both benchmarks using the instructions in the readme
>
>
>
> On Fri, Feb 16, 2024 at 7:53 AM Dave Marion wrote:
>
> > Christopher,
> >
> > Regarding your issues, notes, etc.:
> >
> > 1. IIRC versions 1 and 2 were not built corre
+1, I verified:
* source-release artifact content matches contents of git checkout at the
commit that will be tagged
* signatures match and are signed by the key with the specified fingerprint
* nexus-generated md5 and sha1 hashes exist in the staging repo and match
the artifacts
* the jar, the po
On Mon, Jan 15, 2024 at 2:18 AM Christofer Dutz
wrote:
>
> Hi Christopher,
>
> I do understand that some of the things Apache requires from its projects may
> seem obsolete and outdated.
I hope I didn't give the impression that that's what I think. I know
it's a c
stated above, especially that it's a potentially
harmful custom if the release manager relies on it.
Kind regards,
Christopher
On Sun, Jan 14, 2024, 10:14 Christofer Dutz wrote:
> Hi all,
>
> while reviewing the project's activity as part of me preparing for the
> upcom
LGTM as well
On Fri, Jan 5, 2024 at 10:45 AM Christopher wrote:
> Looks good to me.
>
> On Fri, Jan 5, 2024 at 10:43 AM Dave Marion wrote:
> >
> > Looks good Ed. Thanks!
> >
> > On Fri, Jan 5, 2024 at 10:20 AM dev1 wrote:
> >
> > >
> &g
Looks good to me.
On Fri, Jan 5, 2024 at 10:43 AM Dave Marion wrote:
>
> Looks good Ed. Thanks!
>
> On Fri, Jan 5, 2024 at 10:20 AM dev1 wrote:
>
> >
> >
> > The Accumulo community decided to draft the Apache community reports on
> > the Accumulo dev list – and this is a draft of the January rep
The following is the draft of the announcement for 1.10.4
***
The Apache Accumulo project is pleased to announce the release of
Apache Accumulo 1.10.4! Apache Accumulo 1.10.4 is the final bug fix
release of the 1.10 LTM release line. After this release, the 1.10
release line will be considered end
This vote passes with 6 +1s and no other votes.
Thanks all.
The post-vote release steps are being tracked at:
https://github.com/apache/accumulo/issues/3947
On Thu, Nov 16, 2023 at 3:59 PM Christopher wrote:
>
> I offer my +1 as well.
> I checked the signatures and and checksums, and
1
>
> On Mon, Nov 13, 2023 at 9:42 AM Christopher wrote:
>
> > Accumulo Developers,
> >
> > Please consider the following candidate for Apache Accumulo 1.10.4 (a
> > closeout final release for 1.10)
> >
> > Git Commit:
> > 47ac68d1a220a90bc80
y$Counts
>REFERENCED=146147488
>UNREFERENCED=105
>
>
> On Mon, Nov 13, 2023 at 9:42 AM Christopher wrote:
>
> > Accumulo Developers,
> >
> > Please consider the following candidate for Apache Accumulo 1.10.4 (a
> > closeout final release for 1.10)
>
Accumulo Developers,
Please consider the following candidate for Apache Accumulo 1.10.4 (a
closeout final release for 1.10)
Git Commit:
47ac68d1a220a90bc80618f9684252b243df6b27
Branch:
1.10.4-rc1
If this vote passes, a gpg-signed tag will be created using:
git tag -f -s -m 'Apache Ac
On Sat, Oct 14, 2023 at 9:41 AM Vincent Russell
wrote:
>
> Christopher,
>
> I don't remember configuring anything with regards to commons-vfs. How do
> I disable this?
There's some VFS stuff enabled by default, for backwards
compatibility. There isn't an explicit
I think a performance hit is expected, due to the expected overhead of the
TLS handshake, and the number of connections Accumulo requires in order to
distribute work across a cluster. I think whether the overhead is tolerable
is a per user decision, and may also be dependent upon the details of you
t work eventually if the manager is actually running. If that
doesn't happen eventually, I'm not sure what could be happening
without further troubleshooting.
On Thu, Oct 12, 2023 at 12:36 PM Vincent Russell
wrote:
>
> Christopher,
>
> I have run through an upgrade with a
e make sure that we have some good
> first-issues identified.
>
> Ed Coleman
>
>
> From: Christopher
> Date: Wednesday, September 27, 2023 at 8:09 PM
> To: dev@accumulo.apache.org
> Subject: Re: Accumulo Board Report - due by Oct 11th
> Now that I think about it, I wonder if
current variations in GitHub activity are due to quiet post-release
> activity and work concentrating on a redesign efforts, including activity
> occurring on Confluence
>
> - Accumulo has transitioned from Jira to GitHub issues. The remaining Jira
> activity re
I wouldn't describe the ongoing activity as "moderate". It seems
pretty busy, at least as busy as ever, anyway. Maybe that's what you
meant, but it feels like the word "moderate" carries the connotation
of "mediocre" to me. I think we've been pretty active addressing the
2.1 issues. Not everything
own" because another monitor was running, though. I would expect the
2.1 behavior you described over that 2.0 behavior.
On Mon, Sep 25, 2023 at 11:59 AM Vincent Russell
wrote:
>
> Thank you Christopher,
>
> I did neglect to update the log4j2 files.
>
> One thing that i
g overrides in the system properties or environment variables
that control log4j.
On Tue, Sep 12, 2023 at 8:10 PM Vincent Russell
wrote:
>
> Thank you Christopher,
>
> Don't worry. I definitely planned on testing an upgrade on a test
> cluster. :)
>
> I just up
I'm not 100% certain about the name, but a new repo is a really low risk
thing. I say go for it.
On Thu, Sep 7, 2023, 08:54 Marc P. wrote:
> Out of curiosity, what is the benefit of having a new repo over a release
> target of accumulo-visibility ?
>
> I've used VisibilityEvaluator on non Accumu
doing that, we could probably offer
more specific insight, having probably seen it before.
On Wed, Aug 30, 2023 at 4:50 PM Vincent Russell
wrote:
>
> Thank you Christopher.
>
> Does there exist some documentation for upgrading zookeeper from 3.4.14 to
> 3.8.1? Is there a preferre
The correct link seems to be
https://accumulo.apache.org/docs/2.x/troubleshooting/zookeeper#zookeeper-acls
It looks like both `bin/accumulo dump-zoo` and `bin/accumulo-util
dump-zoo` will do the same thing. It was originally a disconnected
utility that existed for convenience, but was incorporated
See below for the draft consolidated release announcement for 2.1.2
and 3.0.0. I intend to send this out on Tuesday evening to the apache
announce list and our own user list, but am presenting it here for
review while I polish up the release notes.
***
The Apache Accumulo project is pleased to ann
This vote passes with 6 +1s and no other votes.
The post-vote release tasks are tracked at
https://github.com/apache/accumulo/issues/3713
On Mon, Aug 21, 2023 at 4:53 PM Christopher wrote:
>
> +1
>
> I checked:
>
> * signatures, hashes
> * full ITs
> * bin tarball's
This vote passes with 6 +1s and no other votes.
The post-vote release tasks are tracked at
https://github.com/apache/accumulo/issues/3714
On Mon, Aug 21, 2023 at 4:54 PM Christopher wrote:
>
> +1
>
> I checked:
>
> * signatures, hashes
> * full ITs
> * bin tarball's
* built from tar with no errors
> * ran all tests and ITs (only failure was the known
> flaky MemoryStarvedScanIT)
>
> On Mon, Aug 14, 2023 at 4:18 AM Christopher wrote:
>
> > Accumulo Developers,
> >
> > Please consider the followi
d hashes
> * verified psunny passes successfully
>
> On Mon, Aug 14, 2023 at 4:08 AM Christopher wrote:
>
> > Accumulo Developers,
> >
> > Please consider the following candidate for Apache Accumulo 2.1.2.
> >
> > Git Commit:
> > ee7ae63a823477b
from tar with no errors (including errorprone)
> > * Sunny tests passed
> > * Started an uno instances and did some spot checks
> > * Verified no unexpected exception in the log files
> >
> > Ed Coleman
> >
> > From: Christopher
> &g
ing Uno to make sure everything started correctly
On Mon, Aug 14, 2023 at 6:23 PM dev1 wrote:
> +1
>
> Verified signatures and successfully ran sunny tests. Errorprone does
> fail with a minor error with assert usages that is fixed in PR 3691.
>
> Ed Coleman
>
> From: Chri
Accumulo Developers,
Please consider the following candidate for Apache Accumulo 3.0.0.
Git Commit:
fcf3192f27935ee3c66426fb89799ee0850944f2
Branch:
3.0.0-rc1
If this vote passes, a gpg-signed tag will be created using:
git tag -f -s -m 'Apache Accumulo 3.0.0' rel/3.0.0 \
fcf3192
Accumulo Developers,
Please consider the following candidate for Apache Accumulo 2.1.2.
Git Commit:
ee7ae63a823477b557aa9415a92653e95aa64cb1
Branch:
2.1.2-rc1
If this vote passes, a gpg-signed tag will be created using:
git tag -f -s -m 'Apache Accumulo 2.1.2' rel/2.1.2 \
ee7ae63
Congrats Dan!
On Thu, Aug 10, 2023 at 12:08 AM Christopher wrote:
> Welcome Dan, and congrats
>
> On Wed, Aug 9, 2023, 18:27 dev1 wrote:
>
> > The Project Management Committee (PMC) for Apache Accumulo has invited
> Dan
> > Roberts to become a committer / PMC m
Welcome Dan, and congrats
On Wed, Aug 9, 2023, 18:27 dev1 wrote:
> The Project Management Committee (PMC) for Apache Accumulo has invited Dan
> Roberts to become a committer / PMC member and we are pleased to announce
> that they have accepted.
>
> Being a committer enables easier contribution t
Accumulo Developers,
***
NOTE: This is just a TEST release candidate to verify the release
process, and to establish a milestone as a baseline for testing. There
is no need to actually vote, because this is not a real vote.
***
Please consider the following candidate for Apache Accumulo 3.0.0.
G
Thanks all.
This vote passes with 8 "+1" and no other votes.
I will work on the post-vote tasks, which I'm tracking at
https://github.com/apache/accumulo/issues/3507
On Mon, Jun 19, 2023, 10:43 Christopher wrote:
> +1
>
> Verified:
> * Hashes/sigs
> * Full ITs
t graph. Ran this for a few hours. Saw 149
> > > successful completions of the test across the 10 walkers.
> > >
> > > [1]:
> > > https://github.com/apache/accumulo/issues/2667#issuecomment-1269905344
> > >
> > > On Wed, Jun 14, 2023 at 1:49 AM
and sha512) match expected
> > Sunny tests passed with no failures.
> >
> > Ed Coleman
> >
> > From: Christopher
> > Date: Wednesday, June 14, 2023 at 1:49 AM
> > To: accumulo-dev
> > Subject: [VOTE] Apache Accumulo 2.1.1-rc2
> > Accumul
Accumulo Developers,
Please consider the following candidate for Apache Accumulo 2.1.1.
Stuff that's changed since RC1:
* Fix flaky gc tests: https://github.com/apache/accumulo/pull/3490
* Fix hung compactions: https://github.com/apache/accumulo/pull/3492
* Show lowercase table names better in mo
Given the building consensus around #3491, and the fact that a patch
is already merged in, I will withdraw this vote, and cut an RC2 soon
with the updates.
On Tue, Jun 13, 2023 at 7:33 PM Adam Lerman wrote:
>
> -1 because of #3491
>
> On Mon, Jun 12, 2023 at 8:06 PM Christ
Accumulo Developers,
Please consider the following candidate for Apache Accumulo 2.1.1.
Git Commit:
4937a2739f2a9f27e99bd6105cad644a9b868e8b
Branch:
2.1.1-rc1
If this vote passes, a gpg-signed tag will be created using:
git tag -f -s -m 'Apache Accumulo 2.1.1' rel/2.1.1 \
4937a27
ian Loss wrote:
>
> > LGTM. Thanks Christopher.
> >
> > > On Apr 28, 2023, at 2:18 AM, Christopher wrote:
> > >
> > > Accumulo Devs,
> > >
> > > See the below draft release announcement that will be sent to the
> > > users list and
1 - 100 of 2214 matches
Mail list logo
