incubator-mrunit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brock Noland <br...@cloudera.com>
Subject Re: MRUnit 0.5.0 Release Candidate Preview
Date Thu, 03 Nov 2011 03:30:19 GMT
One last question: I created the tag for 0.5.0 based on earlier
instructions but it looks like the release plugin will be creating the
tag. Is it OK for me to delete the existing tag? It's slightly out of
date in terms of the pom.xml.

Otherwise things are coming along. I should be sending out the vote tomorrow.

https://repository.apache.org/content/repositories/orgapachemrunit-149/org/apache/mrunit/mrunit/0.5.0-incubating/
http://people.apache.org/~brock/mrunit-0.5.0-incubating-candidate-0/

Brock

On Tue, Nov 1, 2011 at 10:40 PM, Patrick Hunt <phunt@apache.org> wrote:
> I've never near heard of subkeys, and afaict from this it's really
> just for emails:
> http://www.apache.org/dev/release-signing
>
> I'd recommend using a regular key for code signing. (notice this
> interesting warning at the provided link "Note that some public key
> servers do not handle sub keys correctly.")
>
> Patrick
>
> On Tue, Nov 1, 2011 at 6:32 PM, Brock Noland <brock@cloudera.com> wrote:
>> Patrick,
>>
>> I was able to push the build to a staging repo in Nexus but I am
>> having trouble `closing' that repo.
>>
>> Do you know if the Whirr guys have a key with a subkey?  It seems if
>> my key had no subkey it would resolve my problem. However, according
>> to the apache release signing document a subkey dedicated to signing
>> is normal.
>>
>> $ gpg --list-keys
>> ---------------------------------
>> pub 4096R/C89424B3 2011-10-24
>> uid Brock Noland (CODE SIGNING KEY) <brock@apache.org>
>> sub 4096R/65590375 2011-10-24
>>
>> Brock
>>
>> On Mon, Oct 31, 2011 at 1:23 PM, Patrick Hunt <phunt@apache.org> wrote:
>>> We (whirr) copied another project during bootstrap, they didn't use
>>> release plugin so we got started w/o it. Given over again I'd start
>>> with the release plugin. I have heard from some of our mvn experts
>>> that moving can be a bit painful. For example afaik the release plugin
>>> tags your source base automatically and such...
>>>
>>> Patrick
>>>
>>> On Mon, Oct 31, 2011 at 8:26 AM, Mattmann, Chris A (388J)
>>> <chris.a.mattmann@jpl.nasa.gov> wrote:
>>>> KK, cool. Well when you are ready, I suggest using the mvn release plugin.
Here
>>>> is how we use it in Tika here:
>>>>
>>>> http://grokbase.com/t/lucene.apache.org/tika-dev/2009/09/towards-tika-0-5/28a2me7xhd5s33leaevxrbpo2t3a
>>>>
>>>> Cheers,
>>>> Chris
>>>>
>>>> On Oct 31, 2011, at 6:20 AM, Brock Noland wrote:
>>>>
>>>>> Not yet.  I have been looking at whirr as an example and thus far I
>>>>> got to the nexus permissions but I am still waiting for the JIRA to
>>>>> get resolved. INFRA-4060
>>>>>
>>>>> Brock
>>>>>
>>>>> On Sun, Oct 30, 2011 at 11:33 PM, Mattmann, Chris A (388J)
>>>>> <chris.a.mattmann@jpl.nasa.gov> wrote:
>>>>>> Hey guys -- are you using the mvn release plugin? It should do the
updating
>>>>>> automatically for ya, if you are...
>>>>>>
>>>>>> Cheers,
>>>>>> Chris
>>>>>>
>>>>>> On Oct 30, 2011, at 9:26 PM, Eric Sammer wrote:
>>>>>>
>>>>>>> This has always been unclear to me. I think the only "clean"
way of doing
>>>>>>> it involves the deploy plugin. I started looking into it but
ran out of
>>>>>>> time. I think whirr is completely maven-based. Maybe we should
sneak a peek
>>>>>>> at them?
>>>>>>>
>>>>>>> On Wed, Oct 26, 2011 at 8:24 AM, Brock Noland <brock@cloudera.com>
wrote:
>>>>>>>
>>>>>>>> Great thanks, one more newb question, I think I am going
to have to
>>>>>>>> update the pom.xml after generating the tag because it's
not setup to
>>>>>>>> push to nexus. Should I follow steps 1-2 again for this change?
Or
>>>>>>>> just commit the new pom.xml to trunk for the next round?
>>>>>>>>
>>>>>>>> Brock
>>>>>>>>
>>>>>>>> On Wed, Oct 26, 2011 at 9:32 AM, Mattmann, Chris A (388J)
>>>>>>>> <chris.a.mattmann@jpl.nasa.gov> wrote:
>>>>>>>>> Hey Brock,
>>>>>>>>>
>>>>>>>>> I think you are on the right track. Once you:
>>>>>>>>>
>>>>>>>>> 1. update release notes
>>>>>>>>> 2. generate tag
>>>>>>>>> 3. export tag and create artifacts
>>>>>>>>> 4. generate the sigs
>>>>>>>>> 5. deploy to repository.apache.org (do we have a space
on Apache Nexus
>>>>>>>>> already in org.apache.mrunit? if not someone can file
a JIRA issue at:
>>>>>>>>> http://issues.apache.org/jira/browse/INFRA and take care
of this)
>>>>>>>>> 6. upload to your public_html directory, e.g., as you've
done below:
>>>>>>>>>> http://people.apache.org/~brock/mrunit/rcs/0.5.0-rc1/
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> (in that order)
>>>>>>>>>
>>>>>>>>> It's time to call for a VOTE.
>>>>>>>>>
>>>>>>>>> Thanks for pushing this forward!
>>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>> Chris
>>>>>>>>>
>>>>>>>>> On Oct 26, 2011, at 6:49 AM, Brock Noland wrote:
>>>>>>>>>
>>>>>>>>>> Hello,
>>>>>>>>>>
>>>>>>>>>> Since this is my first time build a release candidate,
I wanted to get
>>>>>>>>>> some feedback before I submit the vote.
>>>>>>>>>>
>>>>>>>>>> http://people.apache.org/~brock/mrunit/rcs/
>>>>>>>>>>
>>>>>>>>>> Anything obviously wrong?
>>>>>>>>>>
>>>>>>>>>> I still have to:
>>>>>>>>>>
>>>>>>>>>> -Generate signatures
>>>>>>>>>> -Generate tag
>>>>>>>>>> -Update release notes
>>>>>>>>>> -Deploy to maven and people.apache.org
>>>>>>>>>> -Run vote
>>>>>>>>>>
>>>>>>>>>> Brock
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>>>>> 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
>>>>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Eric Sammer
>>>>>>> twitter: esammer
>>>>>>> data: www.cloudera.com
>>>>>>
>>>>>>
>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>> 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
>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>>
>>>>>>
>>>>
>>>>
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>> 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
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>
>>>>
>>>
>>
>

Mime
View raw message