+1 for new release

1) I committed GoraCompiler.java for GORA-143-v2.patch last night.
  Since this is my first svn commit, I think it should be reviewed.

2) I have not committed GORA-142 patch for gora-cassandra yet.
  Before that, I'd like to ask the team about serialization spec, so I
will send another e-mail on this matter.
  I am OK for new release without GORA-142 patch.
  Depending on the discussion, I will commit GORA-142 before or after
new release.

-Kaz


On 7/6/12 10:29 AM, Henry Saputra wrote:
> +1 for new release, there are a lot fixes for Cassandra support so
> should be good time for new release.
>
> 0.3 or 0.2.1?
>
> - Henry
>
> On Thu, Jul 5, 2012 at 11:06 PM, Mattmann, Chris A (388J)
> <[email protected]> wrote:
>> +1 to roll release and I'll also throw my name into the hat to release it.
>>
>> Let me know.
>>
>> Thanks!
>>
>> Cheers,
>> Chris
>>
>> On Jul 5, 2012, at 12:30 PM, Lewis John Mcgibbney wrote:
>>
>>> Hi,
>>>
>>> As the GSoC project is moving along nicely and it's been some 3 or so
>>> months since the 0.2 release I was thinking about drumming up support
>>> for another (possibly even 0.2.1) release?
>>>
>>> We have some 15 issues which have been addressed in the development
>>> drive since 0.2 was released and I for one have not had quite as much
>>> time as I would have liked recently to put serious time into Gora.
>>>
>>> What do you guys think? I am more than happy to work as RM again if 
>>> required.
>>>
>>> Thank you in advance
>>>
>>> Lewis
>>>
>>> --
>>> Lewis
>>
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 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/
>> Phone: +1 (818) 354-8810
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Adjunct Assistant Professor, Computer Science Department
>> University of Southern California, Los Angeles, CA 90089 USA
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>


Reply via email to