Re: [QVote] Release 2.1.5 on May 14th
Joerg Heinicke wrote: > David Crossley wrote: > > The FirstFriday was a little bit active and some Bugzilla > > issues were addressed. The Roadmap shows that there are some > > major problems still: > > http://nagoya.apache.org/bugzilla/showdependencytree.cgi?id=25321 > > > > Do we really want to release in this state? > > Yes, we should IMO. Open issues are > > 22842 > flow: importPackage/importClass problems creating InitialContext() > => bug is half a year old, we released it already > > 25083 > JXTemplate evaluates expressions in comments, need jx:comment? > => minor issue > > 25285 > Processing pipelines from within flowscript and get various results objects > => assigned to Sylvain ;-) Sylvain reminded that it is now closed. > 25203 > SQLTransformer: duplicate namespace declaration when serializing XML > => extremely old, I tried to reproduce it on Friday and did not get it > > 26753 > Persistent store or cache corruption? > => For that one we might change the default store. That was one of the options that was discussed at last FirstFriday on IRC. However, no-one has done anything and now we are in a code freeze. > 27467 > Upgrade all source files to ASF 2.0 license > => That's of course a *must*. There are various outstanding issues. IIRC the community decided to release anyway. > 28680 > HTML serialization has no space between publicId and systemId > => Don't know about it, but it seems Xalan related - though you > wrote it does not happen on command line. It seems silly to release something that we know will produce broken output. --David
RE: [QVote] Release 2.1.5 on May 14th
Is there a real blocker in it? Sorry - I have only access to mails currently (I can't access CVS or web until friday morning...). The last time I looked there weren't real blockers - or they were in 2.1.4 already. Carsten > -Original Message- > From: David Crossley [mailto:[EMAIL PROTECTED] > Sent: Monday, May 10, 2004 6:13 AM > To: [EMAIL PROTECTED] > Subject: RE: [QVote] Release 2.1.5 on May 14th > > Carsten Ziegeler wrote: > > Bertrand Delacretaz wrote: > > > Sylvain Wallez a écrit : > > > > ...There are still many little things to solidify in the CForms > > > > API until it can be marked stable, and therefore Cocoon > 2.1.5 will > > > > not contain a stable CForms > > > > > > +1, let's not forget to release early, release often. > > > CForms can still mature after 2.1.5. > > > > Exactly. > > > > We shouldn't get into the trap of "we have to finish XYZ > before we can > > release" again. > > The FirstFriday was a little bit active and some Bugzilla > issues were addressed. The Roadmap shows that there are some > major problems still: > http://nagoya.apache.org/bugzilla/showdependencytree.cgi?id=25321 > > Do we really want to release in this state? > > --David > > >
Re: [QVote] Release 2.1.5 on May 14th
On 10.05.2004 11:15, Sylvain Wallez wrote: Processing pipelines from within flowscript and get various results objects => assigned to Sylvain ;-) Doh! This has been implemented for a long time now in PipelineUtil. Bug closed!! Of course! I use it myself already in my current project (CSV-upload with CForms, processPipelineToDOM, chaperon, back to CForms). I only read the bug summary and did not relate this to processPipelineTo***(). Joerg
Re: [QVote] Release 2.1.5 on May 14th
Joerg Heinicke wrote:
On 10.05.2004 06:12, David Crossley wrote:
The FirstFriday was a little bit active and some Bugzilla
issues were addressed. The Roadmap shows that there are some
major problems still:
http://nagoya.apache.org/bugzilla/showdependencytree.cgi?id=25321
Do we really want to release in this state?
Yes, we should IMO. Open issues are
Processing pipelines from within flowscript and get various results
objects
=> assigned to Sylvain ;-)
Doh! This has been implemented for a long time now in PipelineUtil. Bug
closed!!
Sylvain
--
Sylvain Wallez Anyware Technologies
http://www.apache.org/~sylvain http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
Re: [QVote] Release 2.1.5 on May 14th
Joerg Heinicke wrote: JXTemplate evaluates expressions in comments, need jx:comment? => minor issue Also present in previous releases. Ugo
Re: [QVote] Release 2.1.5 on May 14th
On 10.05.2004 06:12, David Crossley wrote: The FirstFriday was a little bit active and some Bugzilla issues were addressed. The Roadmap shows that there are some major problems still: http://nagoya.apache.org/bugzilla/showdependencytree.cgi?id=25321 Do we really want to release in this state? Yes, we should IMO. Open issues are flow: importPackage/importClass problems creating InitialContext() => bug is half a year old, we released it already JXTemplate evaluates expressions in comments, need jx:comment? => minor issue Processing pipelines from within flowscript and get various results objects => assigned to Sylvain ;-) SQLTransformer: duplicate namespace declaration when serializing XML => extremely old, I tried to reproduce it on Friday and did not get it Persistent store or cache corruption? => For that one we might change the default store. Upgrade all source files to ASF 2.0 license => That's of course a *must*. HTML serialization has no space between publicId and systemId => Don't know about it, but it seems Xalan related - though you wrote it does not happen on command line. Joerg
RE: [QVote] Release 2.1.5 on May 14th
Carsten Ziegeler wrote: > Bertrand Delacretaz wrote: > > Sylvain Wallez a écrit : > > > ...There are still many little things to solidify in the CForms API > > > until it can be marked stable, and therefore Cocoon 2.1.5 will not > > > contain a stable CForms > > > > +1, let's not forget to release early, release often. > > CForms can still mature after 2.1.5. > > Exactly. > > We shouldn't get into the trap of "we have to finish XYZ before we > can release" again. The FirstFriday was a little bit active and some Bugzilla issues were addressed. The Roadmap shows that there are some major problems still: http://nagoya.apache.org/bugzilla/showdependencytree.cgi?id=25321 Do we really want to release in this state? --David
Re: [QVote] Release 2.1.5 on May 14th (Cform API Convergence scheduled > 2.1.6?)
On Wed, 2004-05-05 at 20:28, leo leonid wrote: > Hi, > Not that I'm strictly against a release, but I thought, that the new > 2.1.5 release should mean something like officially launching CForms, > after it's stabilization, in respect of the 'final' API. Don't know where you got that idea from :-) > Actually we > have two APIs, one widely deprecated, the other is looked at as an > aging prototype. Bruno seems to be the only one concerned about the > current situation, I'm still wondering why his v3 proposal didn't find > any resonance? Everybody's too busy... but I can warmly recommend it (the v3 API). It's nothing revolutionary or so, just a combination of aspects from both other API's, so that you don't have to choose between them. That, and some added focus that the sendPageAndWait loop should be easily overridable. -- Bruno Dumon http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center [EMAIL PROTECTED] [EMAIL PROTECTED]
RE: [QVote] Release 2.1.5 on May 14th (Cform API Convergence scheduled > 2.1.6?)
A plea from a non-comitter ... Sorry if this is out of place. I keep having to update woody-cforms stuff at each release :( It's a great forms framework, especially with flow, so I like to try out the new stuff when each release comes out. It would be good to have a stable Cforms in a released version soon. If not in 2.1.5, might it be possible to have a 2.1.6 where it is stable, released at the first possible first Friday ? (As per the original proposal in this Qvote.) Oh and some docs on what would have to be changed in Cforms apps from 2.1.5 -> 2.1.6 :) For what it's worth I'd still vote +1 for 'immature' (but not premature) Cforms in 2.1.5 Christopher > -Original Message- > From: Carsten Ziegeler [mailto:[EMAIL PROTECTED] > Sent: 06 May 2004 08:12 > To: [EMAIL PROTECTED] > Subject: RE: [QVote] Release 2.1.5 on May 14th (Cform API > Convergence scheduled > 2.1.6?) > > > Bertrand Delacretaz wrote: > > > > Le 5 mai 04, à 23:37, Sylvain Wallez a écrit : > > > ...There are still many little things to solidify in the > CForms API > > > until it can be marked stable, and therefore Cocoon 2.1.5 > will not > > > contain a stable CForms > > > > +1, let's not forget to release early, release often. > > CForms can still mature after 2.1.5. > > > Exactly. > > We shouldn't get into the trap of "we have to finish XYZ > before we can release" again. > > Carsten > >
RE: [QVote] Release 2.1.5 on May 14th (Cform API Convergence scheduled > 2.1.6?)
Bertrand Delacretaz wrote: > > Le 5 mai 04, à 23:37, Sylvain Wallez a écrit : > > ...There are still many little things to solidify in the CForms API > > until it can be marked stable, and therefore Cocoon 2.1.5 will not > > contain a stable CForms > > +1, let's not forget to release early, release often. > CForms can still mature after 2.1.5. > Exactly. We shouldn't get into the trap of "we have to finish XYZ before we can release" again. Carsten
Re: [QVote] Release 2.1.5 on May 14th (Cform API Convergence scheduled > 2.1.6?)
Le 5 mai 04, à 23:37, Sylvain Wallez a écrit : ...There are still many little things to solidify in the CForms API until it can be marked stable, and therefore Cocoon 2.1.5 will not contain a stable CForms +1, let's not forget to release early, release often. CForms can still mature after 2.1.5. -Bertrand
Re: [QVote] Release 2.1.5 on May 14th (Cform API Convergence scheduled > 2.1.6?)
Bertrand Delacretaz wrote: Le 5 mai 04, à 20:28, leo leonid a écrit : ...Bruno seems to be the only one concerned about the current situation, I'm still wondering why his v3 proposal didn't find any resonance? Don't know about others obviously, but I have a very hard time keeping up with all that's happening here currently. It's good that many things are happening but it's hard to follow the pace ;-) -Bertrand Same here. I'm still not satisfied with the Flowscript API of CocoonForms because IMO we have to find a simple way to have to support - multi-forms per page - multi-page form wizards in a simple way. Additionally also binding multiple sources in both scenarios should be simple too. But I haven't had enough time to think it through and come up with my own proposal yet. -- Reinhard
Re: [QVote] Release 2.1.5 on May 14th (Cform API Convergence scheduled > 2.1.6?)
Bertrand Delacretaz wrote:
Le 5 mai 04, à 20:28, leo leonid a écrit :
...Bruno seems to be the only one concerned about the current
situation, I'm still wondering why his v3 proposal didn't find any
resonance?
Don't know about others obviously, but I have a very hard time keeping
up with all that's happening here currently. It's good that many
things are happening but it's hard to follow the pace ;-)
Same here. There are still many little things to solidify in the CForms
API until it can be marked stable, and therefore Cocoon 2.1.5 will not
contain a stable CForms.
Note however than in our Cocoon jargon, "stable" means "APIs won't
change", but doesn't mean "buggy". There are already a number of
projects using CForms successfully.
Sylvain
--
Sylvain Wallez Anyware Technologies
http://www.apache.org/~sylvain http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
Re: [QVote] Release 2.1.5 on May 14th (Cform API Convergence scheduled > 2.1.6?)
Le 5 mai 04, à 20:28, leo leonid a écrit : ...Bruno seems to be the only one concerned about the current situation, I'm still wondering why his v3 proposal didn't find any resonance? Don't know about others obviously, but I have a very hard time keeping up with all that's happening here currently. It's good that many things are happening but it's hard to follow the pace ;-) -Bertrand
Re: [QVote] Release 2.1.5 on May 14th (Cform API Convergence scheduled > 2.1.6?)
Hi, Not that I'm strictly against a release, but I thought, that the new 2.1.5 release should mean something like officially launching CForms, after it's stabilization, in respect of the 'final' API. Actually we have two APIs, one widely deprecated, the other is looked at as an aging prototype. Bruno seems to be the only one concerned about the current situation, I'm still wondering why his v3 proposal didn't find any resonance? /leo On 03.05.2004, at 14:02, Carsten Ziegeler wrote: As suggested last week, I'm planning to do the 2.1.5 release on friday, 14th of May. So we can use the first friday (May, 7th) for any open issues and start with the code freeze on saturday. This is a quick vote, so please vote only if you're against it :) Thanks Carsten Carsten Ziegeler Open Source Group, S&N AG http://www.osoco.net/weblogs/rael/
[QVote] Release 2.1.5 on May 14th
As suggested last week, I'm planning to do the 2.1.5 release on friday, 14th of May. So we can use the first friday (May, 7th) for any open issues and start with the code freeze on saturday. This is a quick vote, so please vote only if you're against it :) Thanks Carsten Carsten Ziegeler Open Source Group, S&N AG http://www.osoco.net/weblogs/rael/
