incubator-airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Suresh Marru <sma...@apache.org>
Subject Re: [DISCUSS] Apache Airavata 0.2-Incubating Release Candidate
Date Wed, 01 Feb 2012 22:23:19 GMT

On Feb 1, 2012, at 5:00 PM, Mattmann, Chris A (388J) wrote:

> Hi Suresh,
> 
> Thanks, my replies inline below:
> 
> On Feb 1, 2012, at 1:51 PM, Suresh Marru wrote:
> 
>> Hi Chris,
>> 
>> I wanted to verify the pros and cons of putting release candidate on mirrored location
before the vote is passed. So far what I can see, the RC is put on a non-mirrored location
and only moved to mirrored location after the vote is passed.
> 
> The advantage is that we VOTE on the bits that are actually those that are published
out to the mirrors 
> by a move command on UNIX. You can publish sources to Nexus all we want and then click
"release" but that
> publishes and syncs them to Maven central, not the Apache mirroring system where the
bits must live.
> 
> I'd also prefer to not have to traverse so many links and so forth when evaluating an
RC. I think 
> it's super simple to just co-locate the release artifacts (what we're VOTE'ing on) on
your people.a.o
> public_html directory, throw up a single URL and ask folks to check them, with the understanding
> those are the bits you copy to the dist area when it's successfully VOTEd on and released.
Sure, 
> this adds an extra, outside of Nexus step, but Nexus is just a tool we are using -- it's
not the Foundation's
> official repository, nor is it mirrored like the Foundation requires of its software
releases.

Hi Chris,

This explains and I see your concerns on multiple URL's in the nexus area, I can certainly
move them to one location as you suggest. Here is the location of all source and binaries:
SOURCE and BINARIES - http://people.apache.org/builds/incubator/airavata/0.2-incubating/
KEYS: https://svn.apache.org/repos/asf/incubator/airavata/KEYS
CHANGEME - https://svn.apache.org/repos/asf/incubator/airavata/tags/airavata-0.2-incubating/RELEASE_NOTES

Please let me know if this helps.

Thanks,
Suresh

> 
>> I will see if the process is documented and will get back to you answering remaining
questions as well. 
> 
> Thanks buddy. I will happily VOTE +1 (and am sure everything will look good) but I'd
like to discuss
> the process above first and gauge your opinions. I think it's simpler and the way to
go.
> 
> Take care!
> 
> Cheers,
> Chris
> 
>> 
>>> Guys, sorry to prod, but without answers to the questions below, I'm not
>>> exactly sure on how to proceed reviewing the candidate. 
>>> 
>>> Let me know what you think.
>>> 
>>> Cheers,
>>> Chris
>>> 
>>> On Jan 31, 2012, at 8:34 AM, Mattmann, Chris A (388J) wrote:
>>> 
>>>> Hi Suresh,
>>>> 
>>>> On Jan 29, 2012, at 7:17 PM, Suresh Marru wrote:
>>>> 
>>>>> Hi Chris,
>>>>> 
>>>>> Thank you very much for your time to review the release, we really need
help getting this one right and will greatly appreciate your time in letting us jump these
initial barriers. Please see my answered embedded below:
>>>> 
>>>> Thanks and no problem at all.
>>>> 
>>>>> 
>>>>> On Jan 29, 2012, at 12:56 PM, Mattmann, Chris A (388J) wrote:
>>>>> 
>>>>>> Hi Suresh,
>>>>>> 
>>>>>> First off, thanks for the work in putting this together! What a great
job.
>>>>>> 
>>>>>> That being said: how would I do a gpg key and verification check?
And, 
>>>>> 
>>>>> The signed GPG key is at - https://svn.apache.org/repos/asf/incubator/airavata/KEYS
>>>> 
>>>> gotcha, that's the right place for it, +1.
>>>> 
>>>>> 
>>>>>> how would I verify the MD5 checksums? Typically, we put up a copy
of
>>>>>> the dist artifacts that will end up on minotaur:/www/www.apache.org/dist/incubator/airavata

>>>>>> in someone's people.a.o/~<user>/apache-airavata-<version>-rc-<num>/
folder, 
>>>>>> with:
>>>>>> 
>>>>>> 1. source releases
>>>>>> 2. MD5s and SHA1 and ASC files
>>>>> 
>>>>> 1 and 2 are in https://repository.apache.org/content/repositories/orgapacheairavata-152/org/apache/airavata/airavata/0.2-incubating/
 Please let me know if this is not what you are looking for. 
>>>> 
>>>> That's definitely what I'm looking for, but the fact that they are in repository.apache.org
is my issue. I'll read on 
>>>> below but to preview it here: the source releases need to be distributed
from ASF hardware, in the www.apache.org/dist/
>>>> area so that the dyncloser script can be used to provide proper mirroring
around the world.
>>>> 
>>>>> 
>>>>>> 3. (optional) binaries
>>>>> 
>>>>> The binaries and MD5, SHA1, and ASC files for binaries are at - http://people.apache.org/builds/incubator/airavata/0.2-incubating/
>>>> 
>>>> Hmmm, OK. But this is indicative of my larger issue with the release: why
put this stuff in so many places?
>>>> 
>>>>> 
>>>>>> 4. (optional) CHANGES.txt file
>>>>> 
>>>>> The changes.txt files is same as release notes in this case and it is
at - https://svn.apache.org/repos/asf/incubator/airavata/tags/airavata-0.2-incubating/RELEASE_NOTES,
let me know if it has to be named CHANGES.txt.
>>>> 
>>>> Nah that's just my preference, nothing to change anything on your part (the
guy who is 
>>>> actually doing the work) :) I'll just know to look for it there.
>>>> 
>>>>> 
>>>>>> 
>>>>>> Then, 1-4 are what get copied to /www/www.apache.org/dist/incubator/airavata

>>>>>> on successful VOTE completion. With your existing setup, I'm not
sure 
>>>>>> how I would execute steps 1-2 to do checksum and signature verification.
>>>>> 
>>>>> I am following at the Rave incubator project in this case, where once
passed the release, we will publish the nexus repo for source and move the binaries to http://www.apache.org/dist/incubator/
area. 
>>>> 
>>>> Hmmm. It's more important to move the source to the dist area. In fact, it's
required. The binaries 
>>>> are the optional part.
>>>> 
>>>> Let me know what you think. Thanks!
>>>> 
>>>> Cheers,
>>>> Chris
>>>> 
>>>>> 
>>>>>> 
>>>>>> Let me know and I'd be happy to spend time reviewing the release.
>>>>>> 
>>>>>> Cheers,
>>>>>> Chris
>>>>>> 
>>>>>> On Jan 29, 2012, at 12:47 AM, Suresh Marru wrote:
>>>>>> 
>>>>>>> Discussion thread for vote on airavata 0.2-incubating release
candidate 2.
>>>>>>> 
>>>>>>> If you have any questions or feedback or to post results of validating
the release, please reply to this thread. 
>>>>>>> 
>>>>>>> For reference, the Apache release guide  - http://www.apache.org/dev/release.html
>>>>>>> Incubator specific release guidelines - http://incubator.apache.org/guides/releasemanagement.html
>>>>>>> 
>>>>>>> Some tips to validate the release before you vote:
>>>>>>> 
>>>>>>> * Download the binary version and run the 5 minute or 10 minute
tutorial as described in README and website.
>>>>>>> * Download the source files from compressed files and release
tag and build (which includes tests). 
>>>>>>> * Verify the distributon for the required LICENSE, NOTICE and
DISCLAIMER files
>>>>>>> * Verify if all the staged files are signed and the signature
is verifiable. 
>>>>>>> * Verify if the signing key in the project's KEYS file is hosted
on a public server
>>>>>>> 
>>>>>>> Thanks for your time in validating the release and voting,
>>>>>>> Suresh
>>>>>> 
>>>>>> 
>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>> 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/
>>>> Phone: +1 (818) 354-8810
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>> 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
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>> 
>> 
> 
> 
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 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