Please change the subject if you're going to change this into a conversation about when to start votes. This subject is for votes for an RC candidate.
On Mon, Apr 28, 2014 at 11:30 AM, William Slacum < [email protected]> wrote: > I was concerned about the lack of activity. I don't have a personal need > for an extension, but I do recall a discussion about Friday RC's > potentially being problematic in the past, which is why I brought it up. > > > On Mon, Apr 28, 2014 at 11:21 AM, Christopher <[email protected]> wrote: > > > I don't know what everyone's schedules are. If the point of a vote was > > to begin performing testing, I'd say yes, or if this were RC1, I'd say > > yes (or extended it to 4 days so it's not a surprise). However, since > > we're already in the RC mindset, having had 3 prior ones already, an > > RC4 was already expected to be forthcoming. Since I don't think any of > > the issues since RC3 invalidate the previous testing, and because this > > is RC4, having gone through several previous candidates, I think a 3 > > day vote starting on Friday is fine. That gives many people an > > opportunity to examine the release candidate's changes since the last > > one, whether they do so on a weekend or whether they do so on Monday. > > > > I'm not concerned about the lack of initial activity... that's usually > > the pattern for votes. > > > > Do you think you need extra time to evaluate the release candidate? Do > > we need to discuss an extension? > > > > -- > > Christopher L Tubbs II > > http://gravatar.com/ctubbsii > > > > > > On Mon, Apr 28, 2014 at 8:24 AM, William Slacum > > <[email protected]> wrote: > > > Do you think doing this on a Friday was a good idea? I know that point > > came > > > up earlier, and it was possibly due to already discovered issues that > > would > > > fail the release, but I think the lack of traffic on here is > significant. > > > > > > > > > On Fri, Apr 25, 2014 at 8:37 PM, Christopher <[email protected]> > > wrote: > > > > > >> Correction on the vote end date. It's: > > >> Tue, 2014 April 29 01:00 UTC ... or > > >> Mon, 2014 April 28 21:00 EDT (9pm) > > >> > > >> The initial email had the wrong date (28 instead of 29). > > >> > > >> -- > > >> Christopher L Tubbs II > > >> http://gravatar.com/ctubbsii > > >> > > >> > > >> On Fri, Apr 25, 2014 at 8:35 PM, Christopher <[email protected]> > > wrote: > > >> > Accumulo Developers, > > >> > > > >> > Please consider the following candidate for Accumulo 1.6.0. > > >> > > > >> > Git Commit: 95ddea99e120102ce3316efbbe4948b574e59bc3 > > >> > Branch: 1.6.0-RC4 > > >> > > > >> > Staging repo: > > >> > > > https://repository.apache.org/content/repositories/orgapacheaccumulo-1010 > > >> > Source: > > >> > > > https://repository.apache.org/content/repositories/orgapacheaccumulo-1010/org/apache/accumulo/accumulo/1.6.0/accumulo-1.6.0-src.tar.gz > > >> > Binary: > > >> > > > https://repository.apache.org/content/repositories/orgapacheaccumulo-1010/org/apache/accumulo/accumulo/1.6.0/accumulo-1.6.0-bin.tar.gz > > >> > (Append ".sha1", ".md5" or ".asc" to download the signature/hash > for a > > >> > given artifact.) > > >> > > > >> > All artifacts were built and staged with: > > >> > mvn release:prepare && mvn release:perform > > >> > > > >> > Signing keys available at: > https://www.apache.org/dist/accumulo/KEYS > > >> > > > >> > Release notes (in progress): > > >> http://accumulo.apache.org/release_notes/1.6.0 > > >> > > > >> > Changes since RC3 (`git log 5678e51..origin/1.6.0-RC4`): > > >> > > > >> > https://issues.apache.org/jira/browse/ACCUMULO-1219 > > >> > https://issues.apache.org/jira/browse/ACCUMULO-2523 > > >> > https://issues.apache.org/jira/browse/ACCUMULO-2569 > > >> > https://issues.apache.org/jira/browse/ACCUMULO-2654 > > >> > https://issues.apache.org/jira/browse/ACCUMULO-2707 > > >> > https://issues.apache.org/jira/browse/ACCUMULO-2713 > > >> > https://issues.apache.org/jira/browse/ACCUMULO-2714 > > >> > https://issues.apache.org/jira/browse/ACCUMULO-2715 > > >> > https://issues.apache.org/jira/browse/ACCUMULO-2716 > > >> > https://issues.apache.org/jira/browse/ACCUMULO-2717 > > >> > https://issues.apache.org/jira/browse/ACCUMULO-2718 > > >> > https://issues.apache.org/jira/browse/ACCUMULO-2720 > > >> > https://issues.apache.org/jira/browse/ACCUMULO-2723 > > >> > https://issues.apache.org/jira/browse/ACCUMULO-2726 > > >> > https://issues.apache.org/jira/browse/ACCUMULO-2728 > > >> > https://issues.apache.org/jira/browse/ACCUMULO-2729 > > >> > https://issues.apache.org/jira/browse/ACCUMULO-2733 > > >> > https://issues.apache.org/jira/browse/ACCUMULO-2734 > > >> > > > >> > This vote will remain open for 72 hours (3 days), until Tue, 2014 > > >> > April 28 01:00 UTC. > > >> > (That's 9pm EDT on Monday.) > > >> > > > >> > [ ] +1 - I have verified and accept... > > >> > [ ] +0 - I have reservations, but not strong enough to vote > against... > > >> > [ ] -1 - Because..., I do not accept... > > >> > ... these artifacts as the 1.6.0 release of Apache Accumulo. > > >> > > > >> > Thanks. > > >> > > > >> > P.S. Hint: download the whole staging repo with > > >> > wget -erobots=off -r -l inf -np -nH > > >> > > > >> > > > https://repository.apache.org/content/repositories/orgapacheaccumulo-1010/ > > >> > # note the trailing slash is needed > > >> > > > >> > -- > > >> > Christopher L Tubbs II > > >> > http://gravatar.com/ctubbsii > > >> > > >
