[infinispan-dev] CR1, BETA2 and Branching trunk

[Philippe Van Dyck]

A-mazing...

FYI, with 4.1.0.BETA1 and jclouds 1.0-beta-5, when S3 resets the connection,
I have the same behavior we talked about about the lock not being released.

The issue is reported here :
http://code.google.com/p/jclouds/issues/detail?id=268

Can't wait to test your fix Manik !

Cheers,

Phil

P.S.: BTW, there is a snapshot (???) in the release maven repository ...
shouldn't it be in the ... snapshot repo ?

On Wed, May 26, 2010 at 11:08 PM, Manik Surtani <manik at jboss.org> wrote:

>
> On 26 May 2010, at 17:58, Philippe Van Dyck wrote:
>
> Is it still possible to upgrade to jclouds beta 6 before the release ?
>
>
> Yup jclouds beta6 is in trunk already.
>
>
> cheers,
>
> philippe
>
> On Wed, May 26, 2010 at 4:04 PM, Manik Surtani <manik at jboss.org> wrote:
>
>>
>> On 26 May 2010, at 14:49, Mircea Markus wrote:
>>
>> >
>> > On 26 May 2010, at 15:29, Manik Surtani wrote:
>> >
>> >> Guys,
>> >>
>> >> So we've decided to release Radegast BETA2 tomorrow rather than CR1, as
>> it gives folks more time to feed back stuff.  Hopefully there won't be any
>> work done on Radegast between BETA2 and CR1 except fixing issues people may
>> report.
>> >>
>> >> And for this purpose, I propose branching trunk to a 4.1 branch, after
>> we tag BETA2:
>> >>
>> >>      http://anonsvn.jboss.org/repos/infinispan/branches/4.1.x
>> >>
>> >> This way trunk can contain the 5.0 codebase, and people can start
>> working on 5.0 features.
>> >>
>> > so that we release from 4.1.x and after releasing merge into trunk? or
>> merge into trunk before releasing?
>>
>> I presume you are referring to post-BETA2 releases - in that case, merge
>> to trunk first (since commits/changes for 4.1.x releases will be on that
>> branch)
>>
>> >> Thoughts, opinions?
>> >>
>> >> Cheers,
>> >> Manik
>> >> --
>> >> Manik Surtani
>> >> manik at jboss.org
>> >> Lead, Infinispan
>> >> Lead, JBoss Cache
>> >> http://www.infinispan.org
>> >> http://www.jbosscache.org
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> _______________________________________________
>> >> infinispan-dev mailing list
>> >> infinispan-dev at lists.jboss.org
>> >> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>> >
>> >
>> > _______________________________________________
>> > infinispan-dev mailing list
>> > infinispan-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/infinispan-dev
>>
>> --
>> Manik Surtani
>> manik at jboss.org
>> Lead, Infinispan
>> Lead, JBoss Cache
>> http://www.infinispan.org
>> http://www.jbosscache.org
>>
>>
>>
>>
>>
>> _______________________________________________
>> infinispan-dev mailing list
>> infinispan-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>>
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>
>
> --
> Manik Surtani
> manik at jboss.org
> Lead, Infinispan
> Lead, JBoss Cache
> http://www.infinispan.org
> http://www.jbosscache.org
>
>
>
>
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/infinispan-dev/attachments/20100526/9bd8d9d0/attachment-0001.html