Re: Releasing 2.1.4?
Carsten Ziegeler wrote: Great, especially if you do the work :) Ok, I've committed the script into tools/bin/create-repository-jars.sh (havn't seen the commit mail poping up in my mailbox so far ??) and also put the 2.1.3 jars in place. Feedback is welcome. -- Giacomo Pati Otego AG, Switzerland - http://www.otego.com Orixo, the XML business alliance - http://www.orixo.com
Re: Releasing 2.1.4?
Ralph Goers wrote: I too use maven and would be interested in knowing how you will be organizing this. I currently have all the Cocoon jars in a single cocoon group and all the jars have 2.1.3 in their names. Likewise, all the excalbur stuff is in one group as well. Exactly. After running the script you can define Maven dependencies in your cocoon project as follows: cocoon cocoon 2.1.2 jar cocoon cocoon-cron 2.1.2 jar cocoon cocoon-mail 2.1.2 jar but also cocoon cocoon-war 2.1.2 war -- Giacomo Pati Otego AG, Switzerland - http://www.otego.com Orixo, the XML business alliance - http://www.orixo.com
RE: Releasing 2.1.4?
Giacomo Pati wrote: > > Giacomo Pati wrote: > > > > > > Carsten Ziegeler wrote: > > > >> But: I see a sense in putting our jars there, I'm not so sure what the > >> use > >> in putting also the distribution (the src) there is? > > > > > > If you look at the repository structure proposed there you'll have > > distributions directory as well (BTW: IIRC Avalon has put all their > > dists there). It's just a (more or less) normed place to put dists at > > (probably in respect to what Maven has proposed) > > After thinking a while I don't know if the mirror mechanism is up for > these paths as well, so forget it for now. > Yes, this was my concern as well. I think we should just put the jars there for now. Carsten
Re: Releasing 2.1.4?
Giacomo Pati wrote: Carsten Ziegeler wrote: But: I see a sense in putting our jars there, I'm not so sure what the use in putting also the distribution (the src) there is? If you look at the repository structure proposed there you'll have distributions directory as well (BTW: IIRC Avalon has put all their dists there). It's just a (more or less) normed place to put dists at (probably in respect to what Maven has proposed) After thinking a while I don't know if the mirror mechanism is up for these paths as well, so forget it for now. -- Giacomo Pati Otego AG, Switzerland - http://www.otego.com Orixo, the XML business alliance - http://www.orixo.com
Re: Releasing 2.1.4?
Carsten Ziegeler wrote: Giacomo Pati wrote: +1 for me I'd also like to know your oppinions about using the new http://www.apache.org/dist/java-repository/... location to (maybe in addition for the 2.1.4 release) place the dist (would be /www/www.apache.org/dist/java-repository/cocoon/distributions/ on minotaur.apache.org). I use a script to place all the cocoon block, and the cocoon core jars as well as the war and dist files into such repositories (yes, we use Maven for our project builds and such a remote repository comes in handy for us). What do you think about placing such jars there as well (I'd voloteer for this)? Great, especially if you do the work :) :) I'll make a bin dir in the root (or should I use the tools/bin dir) to put the script into so everybody can have a look at it and do whatever they like to do with it for their personal us. But: I see a sense in putting our jars there, I'm not so sure what the use in putting also the distribution (the src) there is? If you look at the repository structure proposed there you'll have distributions directory as well (BTW: IIRC Avalon has put all their dists there). It's just a (more or less) normed place to put dists at (probably in respect to what Maven has proposed) -- Giacomo Pati Otego AG, Switzerland - http://www.otego.com Orixo, the XML business alliance - http://www.orixo.com
RE: Releasing 2.1.4?
Giacomo Pati wrote: > +1 for me > > I'd also like to know your oppinions about using the new > http://www.apache.org/dist/java-repository/... location to (maybe in > addition for the 2.1.4 release) place the dist (would be > /www/www.apache.org/dist/java-repository/cocoon/distributions/ on > minotaur.apache.org). > > I use a script to place all the cocoon block, and the cocoon core jars > as well as the war and dist files into such repositories (yes, we use > Maven for our project builds and such a remote repository comes in handy > for us). What do you think about placing such jars there as well (I'd > voloteer for this)? > Great, especially if you do the work :) But: I see a sense in putting our jars there, I'm not so sure what the use in putting also the distribution (the src) there is? Carsten
RE: Releasing 2.1.4?
I too use maven and would be interested in knowing how you will be organizing this. I currently have all the Cocoon jars in a single cocoon group and all the jars have 2.1.3 in their names. Likewise, all the excalbur stuff is in one group as well. Ralph -Original Message- From: Giacomo Pati To: [EMAIL PROTECTED] Sent: 2/1/2004 1:21 PM Subject: Re: Releasing 2.1.4? Carsten Ziegeler wrote: > WDYAT? +1 for me I'd also like to know your oppinions about using the new http://www.apache.org/dist/java-repository/... location to (maybe in addition for the 2.1.4 release) place the dist (would be /www/www.apache.org/dist/java-repository/cocoon/distributions/ on minotaur.apache.org). I use a script to place all the cocoon block, and the cocoon core jars as well as the war and dist files into such repositories (yes, we use Maven for our project builds and such a remote repository comes in handy for us). What do you think about placing such jars there as well (I'd voloteer for this)? -- Giacomo Pati Otego AG, Switzerland - http://www.otego.com Orixo, the XML business alliance - http://www.orixo.com
Re: Releasing 2.1.4?
On 30 Jan 2004, at 09:54, Carsten Ziegeler wrote: What do you all think about releasing 2.1.4? :) +1. Can you also name the archives cocoon-2.1.4.tar.gz and cocoon-2.1.4.zip, to make it obvious what file people have downloaded? Thanks, Andrew. -- Andrew Savory, Managing Director, Luminas Limited Tel: +44 (0)870 741 6658 Fax: +44 (0)700 598 1135 Web: http://www.luminas.co.uk/ Orixo alliance: http://www.orixo.com/
RE: Releasing 2.1.4?
Giacomo Pati wrote: > > Carsten Ziegeler wrote: > > WDYAT? > > +1 for me > > I'd also like to know your oppinions about using the new > http://www.apache.org/dist/java-repository/... location to (maybe in > addition for the 2.1.4 release) place the dist (would be > /www/www.apache.org/dist/java-repository/cocoon/distributions/ on > minotaur.apache.org). > > I use a script to place all the cocoon block, and the cocoon > core jars > as well as the war and dist files into such repositories > (yes, we use > Maven for our project builds and such a remote repository > comes in handy > for us). What do you think about placing such jars there as well (I'd > voloteer for this)? > Cool +100! I do exactly that! Unico
Re: Releasing 2.1.4?
Carsten Ziegeler wrote: WDYAT? +1 for me I'd also like to know your oppinions about using the new http://www.apache.org/dist/java-repository/... location to (maybe in addition for the 2.1.4 release) place the dist (would be /www/www.apache.org/dist/java-repository/cocoon/distributions/ on minotaur.apache.org). I use a script to place all the cocoon block, and the cocoon core jars as well as the war and dist files into such repositories (yes, we use Maven for our project builds and such a remote repository comes in handy for us). What do you think about placing such jars there as well (I'd voloteer for this)? -- Giacomo Pati Otego AG, Switzerland - http://www.otego.com Orixo, the XML business alliance - http://www.orixo.com
RE: Releasing 2.1.4?
> From: Upayavira [mailto:[EMAIL PROTECTED] > > > Sylvain Wallez wrote: > > > Carsten Ziegeler wrote: > > > >> What do you all think about releasing 2.1.4? :) > >> > >> There are some open issues from our "management" list: > >> http://nagoya.apache.org/bugzilla/showdependencytree.cgi?id=25320 > >> > >> And next friday is our first "first friday" for this year. > So I would > >> propose to start the code freeze right after the "first > friday" and > >> release one week later. > >> > >> > > > > +1 > > Big +1 (if 1.3 compatibility is okay) +1 too if - 1.3 compatibility is okay - and if Michael has confirmed the fix for http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26186) - all problems with redirecting and cascading calls of internal pipelines in flows are solved (sorry for the noise of all problems are solved but I haven't followed the discussion very close but I consider it as important that everything works well) -- Reinhard
Re: Releasing 2.1.4?
Sylvain Wallez wrote: Carsten Ziegeler wrote: What do you all think about releasing 2.1.4? :) There are some open issues from our "management" list: http://nagoya.apache.org/bugzilla/showdependencytree.cgi?id=25320 And next friday is our first "first friday" for this year. So I would propose to start the code freeze right after the "first friday" and release one week later. +1 Big +1 (if 1.3 compatibility is okay) Regards, Upayavira
Re: Releasing 2.1.4?
On 30.01.2004 16:38, Geoff Howard wrote: Appears it's properly blocking in the release plan for next release: http://nagoya.apache.org/bugzilla/showdependencytree.cgi?id=25321 Yes, I changed it today shortly before all the other buzilla mails were sent to the list. I don't know if no mail is sent on adding dependencies or if those mails still haven't arrived the list as often in the last days. I only do not expect this as the other mails arrived immediately. Where are the bugzilla admins (Bertrand?), maybe they can have a look whether mails are sent on changes on dependencies? Joerg
Re: Releasing 2.1.4?
Bertrand Delacretaz wrote: Le Vendredi, 30 jan 2004, à 14:30 Europe/Zurich, Geoff Howard a écrit : On 30.01.2004 10:54, Carsten Ziegeler wrote: ...I propose the 12th of february as the release date for 2.1.4 - regardless if we have solved all the open issues (RORE - Release often, release early). WDYAT? +1 +1 - The 1.3 runtime incompatibility recently reported should be a blocker though (not sure if it's in bugzilla or not). Still, I'd say it could be fixed by then. +1, also for the 1.3 problem. Appears it's properly blocking in the release plan for next release: http://nagoya.apache.org/bugzilla/showdependencytree.cgi?id=25321 Am I interpreting that right? Geoff
Re: Releasing 2.1.4?
Carsten Ziegeler wrote: What do you all think about releasing 2.1.4? :) There are some open issues from our "management" list: http://nagoya.apache.org/bugzilla/showdependencytree.cgi?id=25320 And next friday is our first "first friday" for this year. So I would propose to start the code freeze right after the "first friday" and release one week later. Now, I'm not really superstitious but as I don't want to do a release on a friday, 13th and as I'm not able to do the release between the 14th and the 21th of february, I propose the 12th of february as the release date for 2.1.4 - regardless if we have solved all the open issues (RORE - Release often, release early). Dang, imagine the karma of releasing 2.1.4 on Feb 14 :) Tony
Re: Releasing 2.1.4?
Carsten Ziegeler wrote:
What do you all think about releasing 2.1.4? :)
There are some open issues from our "management" list:
http://nagoya.apache.org/bugzilla/showdependencytree.cgi?id=25320
And next friday is our first "first friday" for this year. So I
would propose to start the code freeze right after the "first friday"
and release one week later.
+1
Sylvain
--
Sylvain Wallez Anyware Technologies
http://www.apache.org/~sylvain http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
Orixo, the opensource XML business alliance - http://www.orixo.com
Re: Releasing 2.1.4?
Ugo Cei wrote: Carsten Ziegeler wrote: WDYAT? +1 Ugo +1 here, too. Tony
Re: Releasing 2.1.4?
Le Vendredi, 30 jan 2004, à 14:30 Europe/Zurich, Geoff Howard a écrit : On 30.01.2004 10:54, Carsten Ziegeler wrote: ...I propose the 12th of february as the release date for 2.1.4 - regardless if we have solved all the open issues (RORE - Release often, release early). WDYAT? +1 +1 - The 1.3 runtime incompatibility recently reported should be a blocker though (not sure if it's in bugzilla or not). Still, I'd say it could be fixed by then. +1, also for the 1.3 problem. -Bertrand
Re: Releasing 2.1.4?
Carsten Ziegeler wrote: WDYAT? +1 Ugo
Re: Releasing 2.1.4?
Joerg Heinicke wrote: On 30.01.2004 10:54, Carsten Ziegeler wrote: What do you all think about releasing 2.1.4? :) There are some open issues from our "management" list: http://nagoya.apache.org/bugzilla/showdependencytree.cgi?id=25320 This one that is about the next release looks much better :) http://nagoya.apache.org/bugzilla/showdependencytree.cgi?id=25321 And next friday is our first "first friday" for this year. So I would propose to start the code freeze right after the "first friday" and release one week later. Now, I'm not really superstitious but as I don't want to do a release on a friday, 13th and as I'm not able to do the release between the 14th and the 21th of february, I propose the 12th of february as the release date for 2.1.4 - regardless if we have solved all the open issues (RORE - Release often, release early). WDYAT? +1 +1 - The 1.3 runtime incompatibility recently reported should be a blocker though (not sure if it's in bugzilla or not). Still, I'd say it could be fixed by then. Geoff
Re: Releasing 2.1.4?
On 30 Jan 2004, at 05:40, Joerg Heinicke wrote: On 30.01.2004 10:54, Carsten Ziegeler wrote: What do you all think about releasing 2.1.4? :) There are some open issues from our "management" list: http://nagoya.apache.org/bugzilla/showdependencytree.cgi?id=25320 This one that is about the next release looks much better :) http://nagoya.apache.org/bugzilla/showdependencytree.cgi?id=25321 And next friday is our first "first friday" for this year. So I would propose to start the code freeze right after the "first friday" and release one week later. Now, I'm not really superstitious but as I don't want to do a release on a friday, 13th and as I'm not able to do the release between the 14th and the 21th of february, I propose the 12th of february as the release date for 2.1.4 - regardless if we have solved all the open issues (RORE - Release often, release early). WDYAT? +1 +1 -- Stefano. smime.p7s Description: S/MIME cryptographic signature
Re: Releasing 2.1.4?
On 30.01.2004 10:54, Carsten Ziegeler wrote: What do you all think about releasing 2.1.4? :) There are some open issues from our "management" list: http://nagoya.apache.org/bugzilla/showdependencytree.cgi?id=25320 This one that is about the next release looks much better :) http://nagoya.apache.org/bugzilla/showdependencytree.cgi?id=25321 And next friday is our first "first friday" for this year. So I would propose to start the code freeze right after the "first friday" and release one week later. Now, I'm not really superstitious but as I don't want to do a release on a friday, 13th and as I'm not able to do the release between the 14th and the 21th of february, I propose the 12th of february as the release date for 2.1.4 - regardless if we have solved all the open issues (RORE - Release often, release early). WDYAT? +1 Joerg
