Okay, I've now set up a jira component and made myself the default assignee. I also made tickets for the initial import process and the future improvements that got brought up on the DISCUSS thread.
I'll take care of everything under the import umbrella. I unassigned myself from the improvements since I'm not doing them right now and I don't want to discourage newcomers from picking them up. On Tue, Mar 17, 2015 at 5:30 PM, Sean Busbey <[email protected]> wrote: > Vote passes > > +1: 7 votes > -1: 0 votes > > -- > Sean > On Mar 10, 2015 1:48 AM, "Sean Busbey" <[email protected]> wrote: > >> Hi Accumulo! >> >> This is the VOTE thread following our DISCUSS thread on establishing a >> new contrib for upgrade testing. For more details, please see the prior >> DISCUSS thread on this topic[1]. >> >> Cloudera has recently made public some code used for doing correctness >> testing for Accumulo installations across upgrades[2]. The project contains >> simple data load and verification tools as well as a rudimentary upgrade >> test automation script. Cloudera would like to donate this code to the >> ASF and use it as a starting place for a contrib repository focused on >> testing Accumulo across versions generally. >> >> Upon passage of this vote, the Accumulo PMC will adopt this repo as a >> code base for the new project contrib "accumulo-upgrade-tests" subject to >> the ASF IP clearance process[3]. >> >> Either as a part of the IP clearance process or immediately thereafter >> the repo's docs, artifacts, and packages will be updated to make use of >> ASF releases ad naming conventions rather than vendor specific materials. >> >> I (Sean Busbey) have volunteered to shepherd the paperwork in the IP >> clearance process, handle the updates to ASF releases, and serve as >> component lead for a new Jira component to cover the contrib. >> >> Note that as a contrib repository, the artifacts from this repo will be >> versioned independently from the primary Accumulo codebase. While this repo >> seeks to be useful for testing across Accumulo releases, this proposal does >> not establish any requirement for its use on release candidates of the >> primary codebase. >> >> Per our bylaws, this vote will require consensus approval (at least 3 >> binding +1 votes and no binding vetoes). Though only PMC votes are >> binding, all community members are encouraged to vote. >> >> The vote will remain open until 0700 GMT Tuesday March 17 2015 (0300 EDT). >> >> Please vote one of: >> >> [ ] +1: Establish the 'accumulo-upgrade-tests' contrib by adopting the >> codebase as described >> [ ] -1: Do not adopt the codebase because ... >> >> >> [1]: http://s.apache.org/MsR >> [2]: https://github.com/cloudera/accumulo-upgrade-test/ >> [3]: http://incubator.apache.org/ip-clearance/ >> >> -- >> Sean >> > -- Sean
