On 02/02/2012 04:15 AM, Lahiru Gunathilake wrote:
Hi Ate,
On Wed, Feb 1, 2012 at 6:40 PM, Ate Douma<[email protected]> wrote:
On 02/02/2012 12:27 AM, Suresh Marru wrote:
On Feb 1, 2012, at 6:26 PM, Mattmann, Chris A (388J) wrote:
Hi Ate,
On Feb 1, 2012, at 3:12 PM, Ate Douma wrote:
PERFECT. This is what I was looking for. So, to confirm, the process
is, if the VOTE passes, you will
copy these artifacts to the minotaur:/www/www.apache.org/**
dist/incubator/airavata/<http://www.apache.org/dist/incubator/airavata/>area,
correct?
Thats right Chris. If the vote passes, we will copy this to
http://www.apache.org/dist/**incubator/airavata/<http://www.apache.org/dist/incubator/airavata/>which
I assume automatically gets mirrored.
Guys, while I think the above discussion all makes sense, I'm not sure
why you
expect the vote on *this* release candidate will pass?
Although my earlier comments *and* -1 vote may be ignored here and now,
I doubt
the vote will pass the scrutiny of reviewers on general@incubator.
No worries, not ignoring your VOTE. Just trying to get my comments in
regarding what I think
should be addressed as well, get what I mean? Otherwise there can be 2
-1s :)
Absolutely.
As I meant to say above, those definitely are important points as well,
and good to get tackled right away too. I only had time to review one entry
point (so far), you've picked another. Good stuff!
Ate, if you can do a full test and get back to this thread if there are
more blockers for the release candidate that would be a great help for us,
I don't think its a good idea to find blockers one by one in each RC.
Luckily there are more and good pairs of eyes to do the review.
I'd like to explain though that my time *and* focus as a Mentor to help out a
podling is and will be primarily on the more formal rules and process
management, like the release procedures and LEGAL stuff, and about 'the Apache
Way' of doing stuff, community building, etc.
Project specifics like testing if certain technical functionality is working as
expected or fulfilling expectations is secondary and 'extra' to that, time
permitted.
Those things however (IMO) are not critical tasks for a Mentor to review: you
really can and should rely on your own community to provide you with the needed
feedback. In the end, that is or will be your audience once you've graduated
from the Incubator, and the sooner you learn to rely and make use of it the
better. What a release 'blocker' is on technical or functional level really is
something a project community needs to define itself. There are no common rules
for that.
What I'm trying to say is: full technical testing of a release candidate
(besides the basics like: can I actually startup the application) isn't really
my interest, although it might depend on the podling and my personal
interest/involvement. For this level of review you should be looking at the
committers and other direct community members, not so much the Mentors.
Kind regards, Ate
Lahiru
Thats right Ate.
Did not ignore your comments, tried to address Chris's concerns while
looking at the missing LICENSE issues. Will get back for your feedback soon.
Cool, no worries then :)
Ate
Suresh
Cheers,
Chris
Suresh
KEYS:
https://svn.apache.org/repos/**asf/incubator/airavata/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<https://svn.apache.org/repos/asf/incubator/airavata/tags/airavata-0.2-incubating/RELEASE_NOTES>
Cool, perfect. I'll review shortly and cast my VOTE.
Thanks!
Cheers,
Chris
++++++++++++++++++++++++++++++**++++++++++++++++++++++++++++++**
++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: [email protected]
WWW: http://sunset.usc.edu/~**mattmann/<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: [email protected]
WWW: http://sunset.usc.edu/~**mattmann/<http://sunset.usc.edu/~mattmann/>
++++++++++++++++++++++++++++++**++++++++++++++++++++++++++++++**++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++**++++++++++++++++++++++++++++++**++++++
