When you say "make it a contrib", do you mean create a separate contrib repo for it? If so, that seems a bit overkill for that, to me, and seems to fit well into the existing test module. However, I can see merits in independent improvements post-release.
-- Christopher L Tubbs II http://gravatar.com/ctubbsii On Tue, Apr 8, 2014 at 1:22 AM, Sean Busbey <[email protected]> wrote: > I was hoping to make it a contrib. I have tests I run pre and post upgrade > to verify correctness and currently it spans versions. They don't currently > mix well with the rig from ACCUMULO-2145, but my plan was to work that out > after 1.6 gets out. > > I could instead put up the original versions that were specific to each of > 1.4, 1.5, and 1.6. However, I like having it independent so it can improve > and easily be used to test pervious releases if needed. > > -Sean > > On Sat, Apr 5, 2014 at 6:52 AM, Christopher <[email protected]> wrote: > >> https://issues.apache.org/jira/browse/ACCUMULO-2145 does not have a >> fixVersion, but I happen to know that Keith has used the upgrade test >> to find and fix critical issues in 1.6.0 (because he described having >> done so in https://issues.apache.org/jira/browse/ACCUMULO-2520). It >> doesn't affect any Accumulo functioning, and enables better testing, >> so I don't see any reason to object to including it as tests. >> >> Does anybody have any issue committing it to 1.6.0-SNAPSHOT branch, so >> it's co-located with the version it is actually testing? >> >> -- >> Christopher L Tubbs II >> http://gravatar.com/ctubbsii >> > > > > -- > Sean
