gora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mattmann, Chris A (388J)" <chris.a.mattm...@jpl.nasa.gov>
Subject Re: Version on trunk
Date Fri, 11 Mar 2011 06:47:20 GMT
Hey Henry,

Thanks. I'm helping to speed up the VOTE via the cross post. In doing so, we don't need to
wait an additional 72 hours now, if we get 3 IPMC +1s (even if it's just Gora mentors who
are on the IPMC)...

Cheers,
Chris

On Mar 10, 2011, at 10:13 PM, Henry Saputra wrote:

> Hi Chris,
> 
> Thanks for the crosspost rc3 announcement to @general list.
> I didnt do cross post because I thought 72 hours has not passed since
> I announced it to @general.
> 
> - Henry
> 
> On Wed, Mar 9, 2011 at 7:02 PM, Mattmann, Chris A (388J)
> <chris.a.mattmann@jpl.nasa.gov> wrote:
>>> 
>>> I guess we dont need to VOTE again within Gora community, right?
>> 
>> Unfortunately, we do :(
>> 
>> But what I'd do is just cross-post the VOTE to gora-dev@incubator.a.o and general@incubator.a.o,
indicating this is RC #3, and what has been addressed.
>> 
>> Keep up the good work Henry!
>> 
>> Cheers,
>> Chris
>> 
>>> 
>>> - Henry
>>> 
>>> On Wed, Mar 9, 2011 at 2:40 PM, Andrzej Bialecki <ab@getopt.org> wrote:
>>>> On 3/9/11 10:11 PM, Andrzej Bialecki wrote:
>>>>> 
>>>>> On 3/9/11 9:32 PM, Henry Saputra wrote:
>>>>>> 
>>>>>> Since Andrzej already check in to trunk, any changes for 0.1 release
>>>>>> need to be double fixed in both trunk and branch, right?
>>>>> 
>>>>> Yes. My check-in to trunk is not relevant - the next RC should be done
>>>>> from branches/0.1-incubating.
>>>>> 
>>>>>> I dont want to merge trunk to branch with new changes for next release.
>>>>> 
>>>>> If we can avoid it - sure. But occasionally this happens and it's not
a
>>>>> big deal to do so.
>>>>> 
>>>>>> 
>>>>>> Also I have sent email to @general list and got some feedbacks about
>>>>>> our release. Maybe Andrzej or Chris could help response to the
>>>>>> comment?
>>>>> 
>>>>> I need to subscribe first .. ;) I looked at the archive, and indeed we
>>>>> need to fix these issues.
>>>>> 
>>>>> In any case, as I wrote above, the standard procedure is that the next
>>>>> RC should be created from branch 0.1 - if you guys can add the missing
>>>>> NOTICE and DISCLAIMER there and fix the headers I will gladly port these
>>>>> changes back to trunk.
>>>> 
>>>> I found myself with a few minutes to spare, so I started fixing this, it
>>>> should be ready in a moment. I'll apply the change on
>>>> branches/0.1-incubating, and the next RC should be generated from this.
>>>> 
>>>> 
>>>> --
>>>> Best regards,
>>>> Andrzej Bialecki     <><
>>>>  ___. ___ ___ ___ _ _   __________________________________
>>>> [__ || __|__/|__||\/|  Information Retrieval, Semantic Web
>>>> ___|||__||  \|  ||  |  Embedded Unix, System Integration
>>>> http://www.sigram.com  Contact: info at sigram dot com
>>>> 
>>>> 
>>> 
>>> 
>>> 
>>> --
>>> Thanks,
>>> Henry
>> 
>> 
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 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
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 
>> 
> 
> 
> 
> -- 
> Thanks,
> Henry


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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