Basically we decide to do release and then follow the procedures below. Anyone interested in doing the RM role would benefit from executing the first steps under "First time release managers"
https://cwiki.apache.org/confluence/display/MRUNIT/How+to+Release The procedures seem to work well, I have tried to fix any hiccups I have had. I copied them from WHIRR. However, we do accidentally include a .jar file in our tar.gz which people note every time we do a release. As such, I'd like to get MRUNIT-61 solved beforehand. Brock On Thu, Mar 15, 2012 at 10:56 AM, Jim Donofrio <[email protected]> wrote: > Yes you can be the release manager. How does this release process work since > we may not do the release for a few weeks, it depends how long it takes to > get through the remaining issues > > > On 03/15/2012 09:18 AM, Brock Noland wrote: >> >> Hi, >> >> I am for a release, good to release early and often! Jarek, I will >> look at your patch again today. It sounds like you guys are in favor >> of 0.9 release. I am as well. >> >> Jim, you are working on MRUNIT-69, so I figure I should be the Release >> Manager? If you, or anyone else, wants to try the RM role, feel free >> to speak up!! >> >> If no one speaks up, I will send out a vote on the release + RM role. >> >> Cheers! >> Brock >> >> On Thu, Mar 15, 2012 at 4:05 AM, Jim Donofrio<[email protected]> >> wrote: >>> >>> Yes custom counter checking is not in yet but it will be for the >>> 1.0.0/0.9.0 >>> release >>> >>> >>> On 03/15/2012 04:54 AM, Jarek Jarcec Cecho wrote: >>>> >>>> I'm not Brock nor committer, but I would like submit my feedback anyway >>>> :-) >>>> >>>> Custom counter checking is still not in. I've submitted last version of >>>> my >>>> patch to JIRA (add forgotten file CounterWrapper.java) and I'm waiting >>>> for >>>> review. I'll be happy to finish the page into committable form. >>>> >>>> I would personally vote for version 0.9.0, but I don't mind using 1.0.0 >>>> either. >>>> >>>> Jarcec >>>> >>>> On Thu, Mar 15, 2012 at 04:47:58AM -0400, Jim Donofrio wrote: >>>>> >>>>> Brock, >>>>> >>>>> What is your thought on doing a 1.0.0 release? I still would like to >>>>> finish the 4 remaining unresolved JIRA's scheduled for 1.0.0 but >>>>> maybe all new JIRA's could get scheduled for a different version, >>>>> 1.0.1? or 1.1.0? I think we have enough new features/bug fixes: >>>>> mapreduce Combiner, custom counter checking, improved passing of the >>>>> conf, better support for java/other serializations, better error >>>>> messages, deprecated string methods, AssertionError's instead of >>>>> RuntimeException's, separate source, binary distributions. >>>>> >>>>> Should the version really jump up to 1.0.0, maybe 0.9.0 would be >>>>> better. There are no real massive changes, we could continue in the >>>>> 0.10, 0.11, etc versions until the new api is done which would >>>>> become 1.0.0? >> >> >> > -- Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/
