You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mrunit.apache.org by Brock Noland <br...@cloudera.com> on 2012/04/04 03:09:04 UTC
[VOTE] Release MRUnit version 0.9.0-incubating
This is an incubator release for Apache MRUnit, version 0.9.0-incubating.
It fixes the following issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311292&version=12316360
*** Please download, test and vote by [3 working days after sending].
Note that we are voting upon the source (tag), binaries are provided
for convenience.
Source and binary files:
http://people.apache.org/~brock/mrunit-0.9.0-incubating-candidate-0
Maven staging repo:
https://repository.apache.org/content/repositories/orgapachemrunit-012/
The tag to be voted upon:
http://svn.apache.org/repos/asf/incubator/mrunit/tags/release-0.9.0-incubating/
MRUnit's KEYS file containing PGP keys we use to sign the release:
http://svn.apache.org/repos/asf/incubator/mrunit/dist/KEYS
Note that the Incubator PMC needs to vote upon the release after a
successful PPMC vote before any release can be made official.
Re: [VOTE] Release MRUnit version 0.9.0-incubating
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hi Jim,
You sure can: just file an ASF INFRA issue here [1]. You can request Nexus
access via your ASF account.
Cheers,
Chris
[1] https://issues.apache.org/jira/browse/INFRA
On Apr 4, 2012, at 6:27 PM, Jim Donofrio wrote:
> Can I get access to NEXUS to test my changes?
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: [VOTE] Release MRUnit version 0.9.0-incubating
Posted by Brock Noland <br...@cloudera.com>.
Yep, just file an INFRA ticket:
"While the project is still in the incubator you will also need
permissions (mrunit deployer role) on Nexus. You should be able to see
the Staging Repositories in the left panel and if this is not possible
ask the INFRA guys to give you the needed permissions (e.g.
INFRA-3482)."
from https://cwiki.apache.org/confluence/display/MRUNIT/How+to+Release
On Wed, Apr 4, 2012 at 9:27 PM, Jim Donofrio <do...@gmail.com> wrote:
> Can I get access to NEXUS to test my changes?
>
>
> On 04/04/2012 09:08 PM, Brock Noland wrote:
>>
>> I think this is probably OK, it seems like these rules are not hard and
>> fast.
>>
>> On Wed, Apr 4, 2012 at 9:05 PM, Jim Donofrio<do...@gmail.com>
>> wrote:
>>>
>>> Ok I will make the file NOTICE.txt contain the NOTICE.txt for the source
>>> distribution. I will leave the notice for the convenience binary at the
>>> root
>>> of the svn but call it BIN-NOTICE.txt to be clear that it is for the
>>> binary
>>> distribution. Is this ok?
>>>
>>> I took this example from Whirr, so maybe someone should let them know to
>>> also fix their distributions.
>>>
>>>
>>> On 04/04/2012 07:30 PM, sebb wrote:
>>>>
>>>> On 4 April 2012 15:33, Marvin Humphrey<ma...@rectangular.com> wrote:
>>>>>
>>>>> On Wed, Apr 4, 2012 at 4:13 AM, Brock Noland<br...@cloudera.com>
>>>>> wrote:
>>>>>>
>>>>>> On Wed, Apr 4, 2012 at 4:33 AM, sebb<se...@gmail.com> wrote:
>>>>>>>>
>>>>>>>> The tag to be voted upon:
>>>>>>>>
>>>>>>>>
>>>>>>>> http://svn.apache.org/repos/asf/incubator/mrunit/tags/release-0.9.0-incubating/
>>>>>>>
>>>>>>> There's a NOTICE.txt and NOTICE-src.txt at the top level.
>>>>>>>
>>>>>>> IMO the primary NOTICE file should be for the source.
>>>>>>>
>>>>>> So there would be a NOTICE-bin.txt and a NOTICE.txt?
>>>>>
>>>>> The Apache License 2.0 only makes mention of a "NOTICE" file, not
>>>>> "NOTICE-bin"
>>>>> (or "NOTICE-src").
>>>>>
>>>>> The top priority is that the NOTICE[.txt] file in the canonical source
>>>>> release
>>>>> be correct and complete. That's what we're voting on and what the ASF
>>>>> is
>>>>> endorsing.
>>>>
>>>> +1
>>>>
>>>>> I haven't yet arrived at a position regarding the -bin/-deps situation.
>>>>> At
>>>>> this point, I wouldn't -1 a source release that contains irrelevant and
>>>>> misleading information in a file called "NOTICE-bin.txt" about
>>>>> dependencies
>>>>> which are not present, but that could change.
>>>>
>>>> So long as the file is called NOTICE.txt (or NOTICE) and is at the
>>>> top-level of a binary archive, it does not matter what it is called in
>>>> SVN. To avoid confusion, probably best to rename or move the version
>>>> of the NOTICE file for binary releases. Since the binary file is just
>>>> an extended version of the source NOTICE file (at least in this case),
>>>> the binary version could be generated by concatenation.
>>>>
>>>>> Marvin Humphrey
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>
>>
>>
>
--
Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/
Re: [VOTE] Release MRUnit version 0.9.0-incubating
Posted by Jim Donofrio <do...@gmail.com>.
Can I get access to NEXUS to test my changes?
On 04/04/2012 09:08 PM, Brock Noland wrote:
> I think this is probably OK, it seems like these rules are not hard and fast.
>
> On Wed, Apr 4, 2012 at 9:05 PM, Jim Donofrio<do...@gmail.com> wrote:
>> Ok I will make the file NOTICE.txt contain the NOTICE.txt for the source
>> distribution. I will leave the notice for the convenience binary at the root
>> of the svn but call it BIN-NOTICE.txt to be clear that it is for the binary
>> distribution. Is this ok?
>>
>> I took this example from Whirr, so maybe someone should let them know to
>> also fix their distributions.
>>
>>
>> On 04/04/2012 07:30 PM, sebb wrote:
>>> On 4 April 2012 15:33, Marvin Humphrey<ma...@rectangular.com> wrote:
>>>> On Wed, Apr 4, 2012 at 4:13 AM, Brock Noland<br...@cloudera.com> wrote:
>>>>> On Wed, Apr 4, 2012 at 4:33 AM, sebb<se...@gmail.com> wrote:
>>>>>>> The tag to be voted upon:
>>>>>>>
>>>>>>> http://svn.apache.org/repos/asf/incubator/mrunit/tags/release-0.9.0-incubating/
>>>>>> There's a NOTICE.txt and NOTICE-src.txt at the top level.
>>>>>>
>>>>>> IMO the primary NOTICE file should be for the source.
>>>>>>
>>>>> So there would be a NOTICE-bin.txt and a NOTICE.txt?
>>>> The Apache License 2.0 only makes mention of a "NOTICE" file, not
>>>> "NOTICE-bin"
>>>> (or "NOTICE-src").
>>>>
>>>> The top priority is that the NOTICE[.txt] file in the canonical source
>>>> release
>>>> be correct and complete. That's what we're voting on and what the ASF is
>>>> endorsing.
>>> +1
>>>
>>>> I haven't yet arrived at a position regarding the -bin/-deps situation.
>>>> At
>>>> this point, I wouldn't -1 a source release that contains irrelevant and
>>>> misleading information in a file called "NOTICE-bin.txt" about
>>>> dependencies
>>>> which are not present, but that could change.
>>> So long as the file is called NOTICE.txt (or NOTICE) and is at the
>>> top-level of a binary archive, it does not matter what it is called in
>>> SVN. To avoid confusion, probably best to rename or move the version
>>> of the NOTICE file for binary releases. Since the binary file is just
>>> an extended version of the source NOTICE file (at least in this case),
>>> the binary version could be generated by concatenation.
>>>
>>>> Marvin Humphrey
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>
>
>
Re: [VOTE] Release MRUnit version 0.9.0-incubating
Posted by Brock Noland <br...@cloudera.com>.
I think this is probably OK, it seems like these rules are not hard and fast.
On Wed, Apr 4, 2012 at 9:05 PM, Jim Donofrio <do...@gmail.com> wrote:
> Ok I will make the file NOTICE.txt contain the NOTICE.txt for the source
> distribution. I will leave the notice for the convenience binary at the root
> of the svn but call it BIN-NOTICE.txt to be clear that it is for the binary
> distribution. Is this ok?
>
> I took this example from Whirr, so maybe someone should let them know to
> also fix their distributions.
>
>
> On 04/04/2012 07:30 PM, sebb wrote:
>>
>> On 4 April 2012 15:33, Marvin Humphrey<ma...@rectangular.com> wrote:
>>>
>>> On Wed, Apr 4, 2012 at 4:13 AM, Brock Noland<br...@cloudera.com> wrote:
>>>>
>>>> On Wed, Apr 4, 2012 at 4:33 AM, sebb<se...@gmail.com> wrote:
>>>>>>
>>>>>> The tag to be voted upon:
>>>>>>
>>>>>> http://svn.apache.org/repos/asf/incubator/mrunit/tags/release-0.9.0-incubating/
>>>>>
>>>>> There's a NOTICE.txt and NOTICE-src.txt at the top level.
>>>>>
>>>>> IMO the primary NOTICE file should be for the source.
>>>>>
>>>> So there would be a NOTICE-bin.txt and a NOTICE.txt?
>>>
>>> The Apache License 2.0 only makes mention of a "NOTICE" file, not
>>> "NOTICE-bin"
>>> (or "NOTICE-src").
>>>
>>> The top priority is that the NOTICE[.txt] file in the canonical source
>>> release
>>> be correct and complete. That's what we're voting on and what the ASF is
>>> endorsing.
>>
>> +1
>>
>>> I haven't yet arrived at a position regarding the -bin/-deps situation.
>>> At
>>> this point, I wouldn't -1 a source release that contains irrelevant and
>>> misleading information in a file called "NOTICE-bin.txt" about
>>> dependencies
>>> which are not present, but that could change.
>>
>> So long as the file is called NOTICE.txt (or NOTICE) and is at the
>> top-level of a binary archive, it does not matter what it is called in
>> SVN. To avoid confusion, probably best to rename or move the version
>> of the NOTICE file for binary releases. Since the binary file is just
>> an extended version of the source NOTICE file (at least in this case),
>> the binary version could be generated by concatenation.
>>
>>> Marvin Humphrey
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>
--
Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/
Re: [VOTE] Release MRUnit version 0.9.0-incubating
Posted by Jim Donofrio <do...@gmail.com>.
Ok I will make the file NOTICE.txt contain the NOTICE.txt for the source
distribution. I will leave the notice for the convenience binary at the
root of the svn but call it BIN-NOTICE.txt to be clear that it is for
the binary distribution. Is this ok?
I took this example from Whirr, so maybe someone should let them know to
also fix their distributions.
On 04/04/2012 07:30 PM, sebb wrote:
> On 4 April 2012 15:33, Marvin Humphrey<ma...@rectangular.com> wrote:
>> On Wed, Apr 4, 2012 at 4:13 AM, Brock Noland<br...@cloudera.com> wrote:
>>> On Wed, Apr 4, 2012 at 4:33 AM, sebb<se...@gmail.com> wrote:
>>>>> The tag to be voted upon:
>>>>> http://svn.apache.org/repos/asf/incubator/mrunit/tags/release-0.9.0-incubating/
>>>> There's a NOTICE.txt and NOTICE-src.txt at the top level.
>>>>
>>>> IMO the primary NOTICE file should be for the source.
>>>>
>>> So there would be a NOTICE-bin.txt and a NOTICE.txt?
>> The Apache License 2.0 only makes mention of a "NOTICE" file, not "NOTICE-bin"
>> (or "NOTICE-src").
>>
>> The top priority is that the NOTICE[.txt] file in the canonical source release
>> be correct and complete. That's what we're voting on and what the ASF is
>> endorsing.
> +1
>
>> I haven't yet arrived at a position regarding the -bin/-deps situation. At
>> this point, I wouldn't -1 a source release that contains irrelevant and
>> misleading information in a file called "NOTICE-bin.txt" about dependencies
>> which are not present, but that could change.
> So long as the file is called NOTICE.txt (or NOTICE) and is at the
> top-level of a binary archive, it does not matter what it is called in
> SVN. To avoid confusion, probably best to rename or move the version
> of the NOTICE file for binary releases. Since the binary file is just
> an extended version of the source NOTICE file (at least in this case),
> the binary version could be generated by concatenation.
>
>> Marvin Humphrey
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
Re: [VOTE] Release MRUnit version 0.9.0-incubating
Posted by sebb <se...@gmail.com>.
On 4 April 2012 15:33, Marvin Humphrey <ma...@rectangular.com> wrote:
> On Wed, Apr 4, 2012 at 4:13 AM, Brock Noland <br...@cloudera.com> wrote:
>> On Wed, Apr 4, 2012 at 4:33 AM, sebb <se...@gmail.com> wrote:
>>>> The tag to be voted upon:
>>>> http://svn.apache.org/repos/asf/incubator/mrunit/tags/release-0.9.0-incubating/
>>>
>>> There's a NOTICE.txt and NOTICE-src.txt at the top level.
>>>
>>> IMO the primary NOTICE file should be for the source.
>>>
>>
>> So there would be a NOTICE-bin.txt and a NOTICE.txt?
>
> The Apache License 2.0 only makes mention of a "NOTICE" file, not "NOTICE-bin"
> (or "NOTICE-src").
>
> The top priority is that the NOTICE[.txt] file in the canonical source release
> be correct and complete. That's what we're voting on and what the ASF is
> endorsing.
+1
> I haven't yet arrived at a position regarding the -bin/-deps situation. At
> this point, I wouldn't -1 a source release that contains irrelevant and
> misleading information in a file called "NOTICE-bin.txt" about dependencies
> which are not present, but that could change.
So long as the file is called NOTICE.txt (or NOTICE) and is at the
top-level of a binary archive, it does not matter what it is called in
SVN. To avoid confusion, probably best to rename or move the version
of the NOTICE file for binary releases. Since the binary file is just
an extended version of the source NOTICE file (at least in this case),
the binary version could be generated by concatenation.
> Marvin Humphrey
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release MRUnit version 0.9.0-incubating
Posted by sebb <se...@gmail.com>.
On 4 April 2012 15:33, Marvin Humphrey <ma...@rectangular.com> wrote:
> On Wed, Apr 4, 2012 at 4:13 AM, Brock Noland <br...@cloudera.com> wrote:
>> On Wed, Apr 4, 2012 at 4:33 AM, sebb <se...@gmail.com> wrote:
>>>> The tag to be voted upon:
>>>> http://svn.apache.org/repos/asf/incubator/mrunit/tags/release-0.9.0-incubating/
>>>
>>> There's a NOTICE.txt and NOTICE-src.txt at the top level.
>>>
>>> IMO the primary NOTICE file should be for the source.
>>>
>>
>> So there would be a NOTICE-bin.txt and a NOTICE.txt?
>
> The Apache License 2.0 only makes mention of a "NOTICE" file, not "NOTICE-bin"
> (or "NOTICE-src").
>
> The top priority is that the NOTICE[.txt] file in the canonical source release
> be correct and complete. That's what we're voting on and what the ASF is
> endorsing.
+1
> I haven't yet arrived at a position regarding the -bin/-deps situation. At
> this point, I wouldn't -1 a source release that contains irrelevant and
> misleading information in a file called "NOTICE-bin.txt" about dependencies
> which are not present, but that could change.
So long as the file is called NOTICE.txt (or NOTICE) and is at the
top-level of a binary archive, it does not matter what it is called in
SVN. To avoid confusion, probably best to rename or move the version
of the NOTICE file for binary releases. Since the binary file is just
an extended version of the source NOTICE file (at least in this case),
the binary version could be generated by concatenation.
> Marvin Humphrey
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
Re: [VOTE] Release MRUnit version 0.9.0-incubating
Posted by Marvin Humphrey <ma...@rectangular.com>.
On Wed, Apr 4, 2012 at 4:13 AM, Brock Noland <br...@cloudera.com> wrote:
> On Wed, Apr 4, 2012 at 4:33 AM, sebb <se...@gmail.com> wrote:
>>> The tag to be voted upon:
>>> http://svn.apache.org/repos/asf/incubator/mrunit/tags/release-0.9.0-incubating/
>>
>> There's a NOTICE.txt and NOTICE-src.txt at the top level.
>>
>> IMO the primary NOTICE file should be for the source.
>>
>
> So there would be a NOTICE-bin.txt and a NOTICE.txt?
The Apache License 2.0 only makes mention of a "NOTICE" file, not "NOTICE-bin"
(or "NOTICE-src").
The top priority is that the NOTICE[.txt] file in the canonical source release
be correct and complete. That's what we're voting on and what the ASF is
endorsing.
I haven't yet arrived at a position regarding the -bin/-deps situation. At
this point, I wouldn't -1 a source release that contains irrelevant and
misleading information in a file called "NOTICE-bin.txt" about dependencies
which are not present, but that could change.
Marvin Humphrey
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release MRUnit version 0.9.0-incubating
Posted by Brock Noland <br...@cloudera.com>.
Hi,
On Wed, Apr 4, 2012 at 4:33 AM, sebb <se...@gmail.com> wrote:
>> The tag to be voted upon:
>> http://svn.apache.org/repos/asf/incubator/mrunit/tags/release-0.9.0-incubating/
>
> There's a NOTICE.txt and NOTICE-src.txt at the top level.
>
> IMO the primary NOTICE file should be for the source.
>
So there would be a NOTICE-bin.txt and a NOTICE.txt?
Brock
Re: [VOTE] Release MRUnit version 0.9.0-incubating
Posted by Brock Noland <br...@cloudera.com>.
Hi,
On Wed, Apr 4, 2012 at 4:33 AM, sebb <se...@gmail.com> wrote:
>> The tag to be voted upon:
>> http://svn.apache.org/repos/asf/incubator/mrunit/tags/release-0.9.0-incubating/
>
> There's a NOTICE.txt and NOTICE-src.txt at the top level.
>
> IMO the primary NOTICE file should be for the source.
>
So there would be a NOTICE-bin.txt and a NOTICE.txt?
Brock
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release MRUnit version 0.9.0-incubating
Posted by sebb <se...@gmail.com>.
On 4 April 2012 02:09, Brock Noland <br...@cloudera.com> wrote:
> This is an incubator release for Apache MRUnit, version 0.9.0-incubating.
>
> It fixes the following issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311292&version=12316360
>
> *** Please download, test and vote by [3 working days after sending].
>
> Note that we are voting upon the source (tag), binaries are provided
> for convenience.
>
> Source and binary files:
> http://people.apache.org/~brock/mrunit-0.9.0-incubating-candidate-0
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachemrunit-012/
>
> The tag to be voted upon:
> http://svn.apache.org/repos/asf/incubator/mrunit/tags/release-0.9.0-incubating/
There's a NOTICE.txt and NOTICE-src.txt at the top level.
IMO the primary NOTICE file should be for the source.
> MRUnit's KEYS file containing PGP keys we use to sign the release:
> http://svn.apache.org/repos/asf/incubator/mrunit/dist/KEYS
>
> Note that the Incubator PMC needs to vote upon the release after a
> successful PPMC vote before any release can be made official.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release MRUnit version 0.9.0-incubating
Posted by Jim Donofrio <do...@gmail.com>.
Ok lets call off the vote.
We can remove the site plugin and delete the site folder now that we are
going to the CMS.
We can use deploy-file to avoid deploying the tar.gz since if we dont
attach them to the build, the gpg plugin wont sign them.
We can edit the clean plugin to not delete jar's so that the other jar's
will get included in the final binary distribution.
One question, why did we make a separate profile for hadoop 1.0.0, that
jar is exactly the same as the one for 0.20? Since hadoop is changing
hadoop 0.23 to 2.0, maybe it would be better to have only 2 jar's, one
would be hadoop1 and the other hadoop2?
On 04/03/2012 10:43 PM, Brock Noland wrote:
> Hi,
>
> The vote itself is on the source tarball. With that said, I agree
> with both of your thoughts.
>
> On Tue, Apr 3, 2012 at 9:52 PM, Jim Donofrio<do...@gmail.com> wrote:
>> I dont think it makes sense to deploy the 2 distribution tar.gz files or the
>> site.xml to Nexus.
> The tar.gz files are deployed to Nexus by maven. I can delete them
> afterwards. Do you know if there is a way to exclude them from being
> deployed?
>
>> I also see that you only included the hadoop 1.0.0 in the dist, which only
>> includes the jar for hadoop 1.0.0. Do you think it would be better to have
>> one binary distribution that includes all 3 jars for the 3 versions?
> I'd like to see all three versions in the binary tar.gz but that is
> file generated by:
>
> mvn -Dhadoop.version=0.20 clean deploy -Pdeploy
> mvn -Dhadoop.version=0.23 clean deploy -Pdeploy
> mvn clean deploy -Pdeploy
>
> Is there a way to make maven do this?
>
>>
>> On 04/03/2012 09:09 PM, Brock Noland wrote:
>>> This is an incubator release for Apache MRUnit, version 0.9.0-incubating.
>>>
>>> It fixes the following issues:
>>>
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311292&version=12316360
>>>
>>> *** Please download, test and vote by [3 working days after sending].
>>>
>>> Note that we are voting upon the source (tag), binaries are provided
>>> for convenience.
>>>
>>> Source and binary files:
>>> http://people.apache.org/~brock/mrunit-0.9.0-incubating-candidate-0
>>>
>>> Maven staging repo:
>>> https://repository.apache.org/content/repositories/orgapachemrunit-012/
>>>
>>> The tag to be voted upon:
>>>
>>> http://svn.apache.org/repos/asf/incubator/mrunit/tags/release-0.9.0-incubating/
>>>
>>> MRUnit's KEYS file containing PGP keys we use to sign the release:
>>> http://svn.apache.org/repos/asf/incubator/mrunit/dist/KEYS
>>>
>>> Note that the Incubator PMC needs to vote upon the release after a
>>> successful PPMC vote before any release can be made official.
>>>
>
>
Re: [VOTE] Release MRUnit version 0.9.0-incubating
Posted by Brock Noland <br...@cloudera.com>.
Hi,
The vote itself is on the source tarball. With that said, I agree
with both of your thoughts.
On Tue, Apr 3, 2012 at 9:52 PM, Jim Donofrio <do...@gmail.com> wrote:
> I dont think it makes sense to deploy the 2 distribution tar.gz files or the
> site.xml to Nexus.
The tar.gz files are deployed to Nexus by maven. I can delete them
afterwards. Do you know if there is a way to exclude them from being
deployed?
>
> I also see that you only included the hadoop 1.0.0 in the dist, which only
> includes the jar for hadoop 1.0.0. Do you think it would be better to have
> one binary distribution that includes all 3 jars for the 3 versions?
I'd like to see all three versions in the binary tar.gz but that is
file generated by:
mvn -Dhadoop.version=0.20 clean deploy -Pdeploy
mvn -Dhadoop.version=0.23 clean deploy -Pdeploy
mvn clean deploy -Pdeploy
Is there a way to make maven do this?
>
>
> On 04/03/2012 09:09 PM, Brock Noland wrote:
>>
>> This is an incubator release for Apache MRUnit, version 0.9.0-incubating.
>>
>> It fixes the following issues:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311292&version=12316360
>>
>> *** Please download, test and vote by [3 working days after sending].
>>
>> Note that we are voting upon the source (tag), binaries are provided
>> for convenience.
>>
>> Source and binary files:
>> http://people.apache.org/~brock/mrunit-0.9.0-incubating-candidate-0
>>
>> Maven staging repo:
>> https://repository.apache.org/content/repositories/orgapachemrunit-012/
>>
>> The tag to be voted upon:
>>
>> http://svn.apache.org/repos/asf/incubator/mrunit/tags/release-0.9.0-incubating/
>>
>> MRUnit's KEYS file containing PGP keys we use to sign the release:
>> http://svn.apache.org/repos/asf/incubator/mrunit/dist/KEYS
>>
>> Note that the Incubator PMC needs to vote upon the release after a
>> successful PPMC vote before any release can be made official.
>>
>
--
Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/
Re: [VOTE] Release MRUnit version 0.9.0-incubating
Posted by Jim Donofrio <do...@gmail.com>.
I dont think it makes sense to deploy the 2 distribution tar.gz files or
the site.xml to Nexus.
I also see that you only included the hadoop 1.0.0 in the dist, which
only includes the jar for hadoop 1.0.0. Do you think it would be better
to have one binary distribution that includes all 3 jars for the 3 versions?
On 04/03/2012 09:09 PM, Brock Noland wrote:
> This is an incubator release for Apache MRUnit, version 0.9.0-incubating.
>
> It fixes the following issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311292&version=12316360
>
> *** Please download, test and vote by [3 working days after sending].
>
> Note that we are voting upon the source (tag), binaries are provided
> for convenience.
>
> Source and binary files:
> http://people.apache.org/~brock/mrunit-0.9.0-incubating-candidate-0
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachemrunit-012/
>
> The tag to be voted upon:
> http://svn.apache.org/repos/asf/incubator/mrunit/tags/release-0.9.0-incubating/
>
> MRUnit's KEYS file containing PGP keys we use to sign the release:
> http://svn.apache.org/repos/asf/incubator/mrunit/dist/KEYS
>
> Note that the Incubator PMC needs to vote upon the release after a
> successful PPMC vote before any release can be made official.
>
Re: [VOTE] Release MRUnit version 0.9.0-incubating
Posted by sebb <se...@gmail.com>.
On 4 April 2012 02:09, Brock Noland <br...@cloudera.com> wrote:
> This is an incubator release for Apache MRUnit, version 0.9.0-incubating.
>
> It fixes the following issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311292&version=12316360
>
> *** Please download, test and vote by [3 working days after sending].
>
> Note that we are voting upon the source (tag), binaries are provided
> for convenience.
>
> Source and binary files:
> http://people.apache.org/~brock/mrunit-0.9.0-incubating-candidate-0
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachemrunit-012/
>
> The tag to be voted upon:
> http://svn.apache.org/repos/asf/incubator/mrunit/tags/release-0.9.0-incubating/
There's a NOTICE.txt and NOTICE-src.txt at the top level.
IMO the primary NOTICE file should be for the source.
> MRUnit's KEYS file containing PGP keys we use to sign the release:
> http://svn.apache.org/repos/asf/incubator/mrunit/dist/KEYS
>
> Note that the Incubator PMC needs to vote upon the release after a
> successful PPMC vote before any release can be made official.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>