Re: [VOTE] Release on monday

2004-05-20 Thread Upayavira
Ugo Cei wrote: Upayavira wrote: I need to remove the test-suite and use samples/test, and confirm that Ugo's fixes have made the CocoonBeanTestCase work, and then re-enable it. A word of caution. My fixes add the blocks directory and block-provided jars to the classpath for tests and make the

Re: [VOTE] Release on monday

2004-05-20 Thread Ugo Cei
Upayavira wrote: It is there somewhat more akin to an anteater test. Therefore, given these facts, I propose to leave the CocoonBeanTestCase disabled, and simply remove the test suite (as it isn't needed anyway.). I will continue to use the test case locally on my own testing, and will reflect

RE: [VOTE] Release on monday

2004-05-20 Thread Carsten Ziegeler
Antonio Gallardo wrote: I hope we soon will get rid of jisp. What about to deprecate current JISP support? If someone want to use JISP there is still a posibility using JCS. +1 Carsten

Re: [VOTE] Release on monday

2004-05-19 Thread Ugo Cei
Carsten Ziegeler wrote: Or is there anything serious that I did oversee? Nothing, apart a few failing anteater tests. I think those are due to faulty testcases more than to faulty code. Or maybe it's just wishful thinking. Anyway, +1 for a release on Monday. Hopefully I'll find some time to

Re: [VOTE] Release on monday

2004-05-19 Thread Bertrand Delacretaz
Le 19 mai 04, à 10:49, Carsten Ziegeler a écrit : ...If noone objects I will release the current state on monday, 24th of May +1, but won't be able to help (once again), leaving for a holiday tomorrow till Sunday. -Bertrand

Re: [VOTE] Release on monday

2004-05-19 Thread Joerg Heinicke
On 19.05.2004 10:49, Carsten Ziegeler wrote: I think we fixed the most serious problems for 2.1.5 now. Can you sum up the status of the store issues? There were hundreds of mail on it especially on Monday. Before this week we had a non-working persistent store, now we have no longer a

RE: [VOTE] Release on monday

2004-05-19 Thread Carsten Ziegeler
Joerg Heinicke wrote: On 19.05.2004 10:49, Carsten Ziegeler wrote: I think we fixed the most serious problems for 2.1.5 now. Can you sum up the status of the store issues? No, I lost track of it... There were hundreds of mail on it especially on Monday. Before this week we had a

Re: [VOTE] Release on monday

2004-05-19 Thread Upayavira
Carsten Ziegeler wrote: I think we fixed the most serious problems for 2.1.5 now. If noone objects I will release the current state on monday, 24th of May. So the code freeze will continue until then. This gives us some more days to test and possibly fix bugs. Or is there anything serious that I

RE: [VOTE] Release on monday

2004-05-19 Thread Carsten Ziegeler
Upayavira wrote: I need to remove the test-suite and use samples/test, and confirm that Ugo's fixes have made the CocoonBeanTestCase work, and then re-enable it. But, as that test is currently disabled, releasing with it in its current state is not a major problem. I'd just like to

Re: [VOTE] Release on monday

2004-05-19 Thread Joerg Heinicke
On 19.05.2004 13:02, Carsten Ziegeler wrote: Before this week we had a non-working persistent store, now we have no longer a persistent store, but a two-stage caching system with both JCS and EHCache? What about the Serializable issues? Ok, let me try it: - Between 2.1.4 and 2.1.5 we had the

Re: [VOTE] Release on monday

2004-05-19 Thread Sylvain Wallez
Joerg Heinicke wrote: On 19.05.2004 13:02, Carsten Ziegeler wrote: Before this week we had a non-working persistent store, now we have no longer a persistent store, but a two-stage caching system with both JCS and EHCache? What about the Serializable issues? Ok, let me try it: - Between 2.1.4

Re: [VOTE] Release on monday

2004-05-19 Thread Ugo Cei
Upayavira wrote: I need to remove the test-suite and use samples/test, and confirm that Ugo's fixes have made the CocoonBeanTestCase work, and then re-enable it. A word of caution. My fixes add the blocks directory and block-provided jars to the classpath for tests and make the junit-tests

RE: [VOTE] Release on monday

2004-05-19 Thread Carsten Ziegeler
Vadim Gritsenko wrote: Let's clarify something here about all those stores: Transient store: MUST hold NON Serializable objects, MUST NOT persist objects. Persistent store: MUST reject NON Serializable objects, MUST persist objects. Store: MUST hold NON Serializable

Re: [VOTE] Release on monday

2004-05-19 Thread leo leonid
On 19.05.2004, at 14:52, Vadim Gritsenko wrote: I'm +1 on release, if and only if, we note these above bugs in the known issues list. Vadim Please give me that list!!! I updated a server hosting a bunch of XSPs to current CVS. Using the default cocoon.xconf settings, first everything is fine,

Re: [VOTE] Release on monday

2004-05-19 Thread Tim Larson
On Wed, May 19, 2004 at 08:52:52AM -0400, Vadim Gritsenko wrote: snip/ For those who have not followed - this was the behavior of the stores in previous releases of Cocoon (before refactoring we had only two stores, IIRC, but same behavior). Given terminology above, we can have a working

Re: [VOTE] Release on monday

2004-05-19 Thread Antonio Gallardo
Carsten Ziegeler dijo: I think we fixed the most serious problems for 2.1.5 now. If noone objects I will release the current state on monday, 24th of May. So the code freeze will continue until then. This gives us some more days to test and possibly fix bugs. Or is there anything serious