Re: generating the 2.1 Changes page (Was: [Vote] Releasing 2.1.8 tomorrow)
Le 14 nov. 05, à 04:14, David Crossley a écrit : ...As part of our ForrestFriday, Ross and i did some work on this. We can now generate the Changes as part of the 2.1 docs. If Ross can get the proper solution committed soon, then great, otherwise i will commit a workround that will be the next best solution Great! as long as the changes page can be included on the website (the release itself has status.xml, and the website is supposed to stay available), I think we're fine. -Bertrand smime.p7s Description: S/MIME cryptographic signature
Re: generating the 2.1 Changes page (Was: [Vote] Releasing 2.1.8 tomorrow)
Ross Gardler wrote: Bertrand Delacretaz wrote: David Crossley a ?crit : ...The top-level docs are now building the changes page by getting the status.xml file from the 2.1 branch svn. Not ideal, but it works Great! http://forrest.zones.apache.org/ft/build/cocoon-site/changes.html The problem is that that page will not be added to the 2.1 docs package, but at least we can update it on the website... Yes, this is a l;imitation of the quick hack solution I had to do for the URL space solution, there is a workaround for now (see below). It will be fixed shortly. However... You mean, the page will not be in the distribution? Not necessarily, add a match into the daisy-to-docs sitemap.xmap and we can have it generated by Forrest alongside the daisy docs. As part of our ForrestFriday, Ross and i did some work on this. We can now generate the Changes as part of the 2.1 docs. If Ross can get the proper solution committed soon, then great, otherwise i will commit a workround that will be the next best solution. -David
Re: generating the 2.1 Changes page (Was: [Vote] Releasing 2.1.8 tomorrow)
Bertrand Delacretaz wrote: Le 11 nov. 05, à 04:26, David Crossley a écrit : ...The top-level docs are now building the changes page by getting the status.xml file from the 2.1 branch svn. Not ideal, but it works Great! http://forrest.zones.apache.org/ft/build/cocoon-site/changes.html The problem is that that page will not be added to the 2.1 docs package, but at least we can update it on the website... Yes, this is a l;imitation of the quick hack solution I had to do for the URL space solution, there is a workaround for now (see below). It will be fixed shortly. However... You mean, the page will not be in the distribution? Not necessarily, add a match into the daisy-to-docs sitemap.xmap and we can have it generated by Forrest alongside the daisy docs. Ross
Re: recovering forrest.properties (was: [Vote] Releasing 2.1.8 tomorrow)
David Crossley wrote: Double Uh'oh ... the docs target was also removed, so that means that for someone to build the Changes they will need to go back to an old version of cocoon-2_1_X and use todays status.xml file. Need to do 'build docs' and then do 'forrest' as described at: http://wiki.apache.org/cocoon/CocoonWebsiteUpdate and set project.start-uri=changes.html in forrest.properties Hmmm, having trouble to find a working revision of the branch for this fallback for building changes.html So going to try some other ways to get Forrest to build it. -David
generating the 2.1 Changes page (Was: [Vote] Releasing 2.1.8 tomorrow)
David Crossley wrote: Bertrand Delacretaz wrote: David Crossley a ?crit : ...As i warned a long time ago, the re-arrangement of documentation should not have been done until the 2.2 release... Fully agreed, staying with the old docs for 2.1.8 seems much easier, and 2.2 is a good time to make a transition on the docs. ...If people are not going to help fix the new Daisy-based documentation for this release, then we we need to repair the old documentation building system, e.g. the index.xml file seems to be missing and various other source files have been deleted... Could we do the release and regenerate only the index and news pages? I don't think there have been much changes to other parts of the old docs. I'm strongly for releasing 2.1.8 with the old docs and take our time to improve them for 2.2. Good idea, i was wondering about that as a workaround. We can easily update the complete top-level docs, same as before. http://wiki.apache.org/cocoon/CocoonWebsiteUpdate We might be able to repair the old 2.1 docs sufficiently to get the changes.html page built and update only that page. Doing 'svn log status.xml' shows that quite a lot of changes (~130) are noted since 2.1.7 (March 23 2005). Okay i tried various ways to do that and now have one solution working. It would have been better get the cocoon-daisy-to-docs to process the Changes (since they belong with 2.1). However i cannot do that because the Forrest Daisy plugin seems to intercept everything and map it to Daisy. So the projectInfo plugin can't handle it. The top-level docs are now building the changes page by getting the status.xml file from the 2.1 branch svn. Not ideal, but it works. http://forrest.zones.apache.org/ft/build/cocoon-site/changes.html The problem is that that page will not be added to the 2.1 docs package, but at least we can update it on the website. -David
Re: generating the 2.1 Changes page (Was: [Vote] Releasing 2.1.8 tomorrow)
Le 11 nov. 05, à 04:26, David Crossley a écrit : ...The top-level docs are now building the changes page by getting the status.xml file from the 2.1 branch svn. Not ideal, but it works Great! http://forrest.zones.apache.org/ft/build/cocoon-site/changes.html The problem is that that page will not be added to the 2.1 docs package, but at least we can update it on the website... You mean, the page will not be in the distribution? The status.xml page is in there, which is good enough I think, given that the changes will be available on the website. -Bertrand
recovering forrest.properties (was: [Vote] Releasing 2.1.8 tomorrow)
Le 9 nov. 05, à 08:33, David Crossley a écrit :
...Uh'oh i see that someone has deleted
branches/BRANCH_2_1_X/forrest.properties
so i need to get that back. Can someone please explain how to find
out when that file was removed from SVN. I tried searching my local
mail archives for [EMAIL PROTECTED] but cannot find it...
With svn log you can see when it was deleted:
cd BRANCH_2_1_X
svn log --verbose -r {2005-08-01}:{2005-12-31}
Shows:
r322479 | cziegeler | 2005-10-16 17:15:04 +0200 (Sun, 16 Oct 2005) | 3
lines
D /cocoon/branches/BRANCH_2_1_X/forrest.properties
And then you can restore the file (*including* its history, thanks
SVN!) with
svn copy --revision 322478
https://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/
forrest.properties .
using the previous revision number, where the file was still there.
I haven't commited the recovered file, in case you just need it it
temporarily you can get it with the above command.
There's a good explanation at
http://svnbook.red-bean.com/en/1.0/svn-book.html#svn-ch-4-sect-4.3
-Bertrand
Re: recovering forrest.properties (was: [Vote] Releasing 2.1.8 tomorrow)
Bertrand Delacretaz wrote: With svn log you can see when it was deleted: Thanks, that is what i was looking for. I haven't commited the recovered file, in case you just need it it temporarily you can get it with the above command. Please do. I want to encourage other people to deal with documentation issues. -David
Re: recovering forrest.properties (was: [Vote] Releasing 2.1.8 tomorrow)
Le 9 nov. 05, à 09:48, David Crossley a écrit : Bertrand Delacretaz wrote: ...I haven't commited the recovered file, in case you just need it it temporarily you can get it with the above command. Please do. I want to encourage other people to deal with documentation issues... done. -Bertrand
Re: [Vote] Releasing 2.1.8 tomorrow
David Crossley wrote: Bertrand Delacretaz wrote: David Crossley a ?crit : ...As i warned a long time ago, the re-arrangement of documentation should not have been done until the 2.2 release... Fully agreed, staying with the old docs for 2.1.8 seems much easier, and 2.2 is a good time to make a transition on the docs. ...If people are not going to help fix the new Daisy-based documentation for this release, then we we need to repair the old documentation building system, e.g. the index.xml file seems to be missing and various other source files have been deleted... Could we do the release and regenerate only the index and news pages? I don't think there have been much changes to other parts of the old docs. I'm strongly for releasing 2.1.8 with the old docs and take our time to improve them for 2.2. Good idea, i was wondering about that as a workaround. We can easily update the complete top-level docs, same as before. http://wiki.apache.org/cocoon/CocoonWebsiteUpdate You can also add entries to the locationmap in the daisy-to-docs module that will retrieve the relevant content from SVN. That is, documents you want to come from the old SVN files would have an entry pointing at http://svn.a.o/... instead of at daisy. When the site is built Forrest will retrieve the content from the relevant place. Ross
Re: [Vote] Releasing 2.1.8 tomorrow
David Crossley wrote: Vadim Gritsenko wrote: David Crossley wrote: there is currently a changed URL-space which will bust links, David, What changed URLs have you noticed, so far? If there is a list, it will help fixing problems. Myself, I noticed that http://cocoon.apache.org/2.1/introduction.html became http://forrest.zones.apache.org/ft/build/cocoon-docs /2.1/documentation/introduction.html It probably can be easily fixed in the navigation document. I'm thinking of removing node ID for 'documentation' node; or setting it to '.' might do the trick. The first part of the urlspace (i.e. http://forrest.zones.apache.org/ft/build/cocoon-docs) is nt part of the generated docs. All we need to do is zip up the site built by Forrest and unzip it in the target location, so to get http://cocoon.apache.org/2.1/introduction.html Just unzip in the root locaton for cocoon.a.o (at least that is the intention of the build). Ross
Re: [Vote] Releasing 2.1.8 tomorrow
Carsten Ziegeler wrote: David Crossley wrote: Carsten Ziegeler wrote: This is another try to get 2.1.8 finally out: Please cast your votes for releasing 2.1.8 tomorrow, 8th of November. -1 ... People have not addressed the documentation side of things. See other recent email on this topic to which nobody replied. We will not be able to update the website, the documentation will not be packaged with the release nor available alongside, there is currently a changed URL-space which will bust links, and there will be no list of changes for the release. Ok, I'll wait with building the release until this problem is solved. As soon as I get a notice that all issues with the docs have been resolved I'll go ahead. Sorry, I'm a little slow responding right now. I'm travelling at present and only have intermittent access and time. However, the URL space issues are not issues, just get David or myself to zip up te built docs and there you go, you have the docs in the 2.1/... urlspace you want. This issue was raised weeks ago and was fixed weeks ago. Ross
Re: [Vote] Releasing 2.1.8 tomorrow
Ross Gardler wrote: Sorry, I'm a little slow responding right now. I'm travelling at present and only have intermittent access and time. However, the URL space issues are not issues, just get David or myself to zip up te built docs and there you go, you have the docs in the 2.1/... urlspace you want. This issue was raised weeks ago and was fixed weeks ago. Great :) Ok, so can you or David please zip up the docs and put it somewhere where I can reach them? (people.apache.org or our zone for example) Thanks Carsten -- Carsten Ziegeler - Open Source Group, SN AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
Re: [Vote] Releasing 2.1.8 tomorrow
Carsten Ziegeler wrote: Ross Gardler wrote: Sorry, I'm a little slow responding right now. I'm travelling at present and only have intermittent access and time. However, the URL space issues are not issues, just get David or myself to zip up te built docs and there you go, you have the docs in the 2.1/... urlspace you want. This issue was raised weeks ago and was fixed weeks ago. Hmm, maybe you have been missing some mails. Please see my reply to Vadim today earlier in this thread. -David Great :) Ok, so can you or David please zip up the docs and put it somewhere where I can reach them? (people.apache.org or our zone for example) Thanks Carsten -- Carsten Ziegeler - Open Source Group, SN AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
Re: [Vote] Releasing 2.1.8 tomorrow
Ross Gardler wrote: David Crossley wrote: Bertrand Delacretaz wrote: David Crossley a ?crit : ...As i warned a long time ago, the re-arrangement of documentation should not have been done until the 2.2 release... Fully agreed, staying with the old docs for 2.1.8 seems much easier, and 2.2 is a good time to make a transition on the docs. ...If people are not going to help fix the new Daisy-based documentation for this release, then we we need to repair the old documentation building system, e.g. the index.xml file seems to be missing and various other source files have been deleted... Could we do the release and regenerate only the index and news pages? I don't think there have been much changes to other parts of the old docs. I'm strongly for releasing 2.1.8 with the old docs and take our time to improve them for 2.2. Good idea, i was wondering about that as a workaround. We can easily update the complete top-level docs, same as before. http://wiki.apache.org/cocoon/CocoonWebsiteUpdate You can also add entries to the locationmap in the daisy-to-docs module that will retrieve the relevant content from SVN. That is, documents you want to come from the old SVN files would have an entry pointing at http://svn.a.o/... instead of at daisy. When the site is built Forrest will retrieve the content from the relevant place. Ahhh... no slight problem with that. The Daisy plugin does not currently support content from alternative locations (it used to until I fixed the URLspace issues for Cocoon, and I've not got around to making that work again, sorry). The above will be possible soon, but not sure when I'll have the time to tackle it. Probably better to build those pages by hand as you suggest, it's only a handful. Ross Ross
Re: [Vote] Releasing 2.1.8 tomorrow
Ross Gardler wrote: David Crossley wrote: Bertrand Delacretaz wrote: David Crossley a ?crit : ...As i warned a long time ago, the re-arrangement of documentation should not have been done until the 2.2 release... Fully agreed, staying with the old docs for 2.1.8 seems much easier, and 2.2 is a good time to make a transition on the docs. ...If people are not going to help fix the new Daisy-based documentation for this release, then we we need to repair the old documentation building system, e.g. the index.xml file seems to be missing and various other source files have been deleted... Could we do the release and regenerate only the index and news pages? I don't think there have been much changes to other parts of the old docs. I'm strongly for releasing 2.1.8 with the old docs and take our time to improve them for 2.2. Good idea, i was wondering about that as a workaround. We can easily update the complete top-level docs, same as before. http://wiki.apache.org/cocoon/CocoonWebsiteUpdate You can also add entries to the locationmap in the daisy-to-docs module that will retrieve the relevant content from SVN. That is, documents you want to come from the old SVN files would have an entry pointing at http://svn.a.o/... instead of at daisy. When the site is built Forrest will retrieve the content from the relevant place. Ahhh... slight problem with that. The Daisy plugin does not currently support content from alternative locations, it used to until I fixed the URLspace issues for Cocoon, and I've not got around to making that work again, sorry. The above will be possible soon, but not sure when I'll have the time to tackle it. Probably better to build those pages by hand as you suggest, it's only a handful. Ross Ross
license issues in Faces block (Was: [Vote] Releasing 2.1.8 tomorrow)
David Crossley wrote: David Crossley wrote: Another issue is that normally i run a program to scan for license issues, but have not found time. I will try to make some time to do that tonight. That is done now. There are SUN licenses throughout the src/blocks/faces/java/org/apache/cocoon/faces/samples/ The main issue is that some files have a SUN license header but in the org.apache.cocoon package. Don't know how that occurred, e.g. src/blocks/faces/java/org/apache/cocoon/faces/samples/components/taglib/MapTag.java -David
Re: license issues in Faces block (Was: [Vote] Releasing 2.1.8 tomorrow)
David Crossley wrote: That is done now. There are SUN licenses throughout the src/blocks/faces/java/org/apache/cocoon/faces/samples/ The main issue is that some files have a SUN license header but in the org.apache.cocoon package. Don't know how that occurred, e.g. src/blocks/faces/java/org/apache/cocoon/faces/samples/components/taglib/MapTag.java Arrrggg, it seems that releasing 2.1.8 will be one of the most problematic releases ever. Ok, I'll stop all action now. Carsten -- Carsten Ziegeler - Open Source Group, SN AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
Re: [Vote] Releasing 2.1.8 tomorrow
David Crossley wrote: Vadim Gritsenko wrote: David Crossley wrote: there is currently a changed URL-space which will bust links, David, What changed URLs have you noticed, so far? If there is a list, it will help fixing problems. Myself, I noticed that http://cocoon.apache.org/2.1/introduction.html became http://forrest.zones.apache.org/ft/build/cocoon-docs /2.1/documentation/introduction.html It probably can be easily fixed in the navigation document. I'm thinking of removing node ID for 'documentation' node; or setting it to '.' might do the trick. I was referring to the general problems described here: http://marc.theaimsgroup.com/?l=xml-cocoon-devm=113132799820935 Your suggestion might solve that. New docs, generated in http://forrest.zones.apache.org/ft/build/cocoon-docs/2.1, are to replace only 2.1 docs, top-level site remains as it is right now, and I don't see any pages in daisy which are conflicting with that. At least, that is my understanding. So, we need to fix .../2.1/documentation/introduction.html - .../2.1/introduction.html, but other than that, I don't see any major issues. (and you already figured out how to generate changes.html) Vadim
Re: [Vote] Releasing 2.1.8 tomorrow
Ross Gardler wrote: David Crossley wrote: Vadim Gritsenko wrote: What changed URLs have you noticed, so far? If there is a list, it will help fixing problems. Myself, I noticed that http://cocoon.apache.org/2.1/introduction.html became http://forrest.zones.apache.org/ft/build/cocoon-docs /2.1/documentation/introduction.html It probably can be easily fixed in the navigation document. I'm thinking of removing node ID for 'documentation' node; or setting it to '.' might do the trick. The first part of the urlspace (i.e. http://forrest.zones.apache.org/ft/build/cocoon-docs) is nt part of the generated docs. I know. All we need to do is zip up the site built by Forrest and unzip it in the target location, so to get http://cocoon.apache.org/2.1/introduction.html Won't work. Please take a second look: there is an extra /documentation in there. For example... Pages which are in correct location are: /2.1/index.html /2.1/about/features.html /2.1/about/license.html Pages in wrong locations are: /2.1/documentation/introduction.html - /2.1/introduction.html /2.1/status/plan/overview/index.html - /2.1/plan/index.html /2.1/community/bylaws-addendum.html - /2.1/bylaws-addendum.html etc. Vadim
Re: [Vote] Releasing 2.1.8 tomorrow
Vadim Gritsenko wrote: David Crossley wrote: Vadim Gritsenko wrote: David Crossley wrote: there is currently a changed URL-space which will bust links, David, What changed URLs have you noticed, so far? If there is a list, it will help fixing problems. Myself, I noticed that http://cocoon.apache.org/2.1/introduction.html became http://forrest.zones.apache.org/ft/build/cocoon-docs /2.1/documentation/introduction.html It probably can be easily fixed in the navigation document. I'm thinking of removing node ID for 'documentation' node; or setting it to '.' might do the trick. I was referring to the general problems described here: http://marc.theaimsgroup.com/?l=xml-cocoon-devm=113132799820935 Your suggestion might solve that. New docs, generated in http://forrest.zones.apache.org/ft/build/cocoon-docs/2.1, are to replace only 2.1 docs, top-level site remains as it is right now, and I don't see any pages in daisy which are conflicting with that. For example, the docs under the Community and About labels gain extra subdirectories compared with the existing website. -David At least, that is my understanding. So, we need to fix .../2.1/documentation/introduction.html - .../2.1/introduction.html, but other than that, I don't see any major issues. (and you already figured out how to generate changes.html) Vadim
Re: [Vote] Releasing 2.1.8 tomorrow
David Crossley wrote: For example, the docs under the Community and About labels gain extra subdirectories compared with the existing website. That's the bug in need of fixing, imho, and not more than that. I'm sending out a diff... Vadim
Re: license issues in Faces block (Was: [Vote] Releasing 2.1.8 tomorrow)
David Crossley wrote: Don't know how that occurred, e.g. src/blocks/faces/java/org/apache/cocoon/faces/samples/components/taglib/MapTag.java PMC archives have it. See thread started on September 2004, 17th. It was deemed to be non issue, and this demo is shipped w/Cocoon since version 2.1.6. Vadim
Re: [Vote] Releasing 2.1.8 tomorrow
Vadim Gritsenko wrote: David Crossley wrote: For example, the docs under the Community and About labels gain extra subdirectories compared with the existing website. That's the bug in need of fixing, imho, and not more than that. I'm sending out a diff... I've had a look at this, please see the [DOCS] Building for release thread (where Vadim posted the diff). Ross
[Vote] Releasing 2.1.8 tomorrow
This is another try to get 2.1.8 finally out: Please cast your votes for releasing 2.1.8 tomorrow, 8th of November. Carsten -- Carsten Ziegeler - Open Source Group, SN AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
Re: [Vote] Releasing 2.1.8 tomorrow
+1 !
Re: [Vote] Releasing 2.1.8 tomorrow
Carsten Ziegeler wrote: This is another try to get 2.1.8 finally out: Please cast your votes for releasing 2.1.8 tomorrow, 8th of November. +100 ! :-) Sylvain -- Sylvain WallezAnyware Technologies http://people.apache.org/~sylvain http://www.anyware-tech.com Apache Software Foundation Member Research Technology Director
Re: [Vote] Releasing 2.1.8 tomorrow
On 11/8/05, Carsten Ziegeler [EMAIL PROTECTED] wrote: This is another try to get 2.1.8 finally out: Please cast your votes for releasing 2.1.8 tomorrow, 8th of November. +1 Ciao, -- Gianugo Rabellino Pro-netics s.r.l. - http://www.pro-netics.com Orixo, the XML business alliance: http://www.orixo.com (blogging at http://www.rabellino.it/blog/)
Re: [Vote] Releasing 2.1.8 tomorrow
Hi, On 8 Nov 2005, at 10:54, Carsten Ziegeler wrote: Please cast your votes for releasing 2.1.8 tomorrow, 8th of November. +1 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: [Vote] Releasing 2.1.8 tomorrow
Il giorno 08/nov/05, alle ore 11:54, Carsten Ziegeler ha scritto: Please cast your votes for releasing 2.1.8 tomorrow, 8th of November. +1 Ugo -- Ugo Cei Tech Blog: http://agylen.com/ Open Source Zone: http://oszone.org/ Wine Food Blog: http://www.divinocibo.it/
Re: [Vote] Releasing 2.1.8 tomorrow
On 08.11.2005, at 12:15, Gianugo Rabellino wrote: On 11/8/05, Carsten Ziegeler [EMAIL PROTECTED] wrote: This is another try to get 2.1.8 finally out: Please cast your votes for releasing 2.1.8 tomorrow, 8th of November. There are still some samples broken. Unfortunately I don't have the time to help out at the moment. So I don't want to -1 it ...but I cannot give more than a -0 cheers -- Torsten PS: What about a testing matrix for releases? PGP.sig Description: This is a digitally signed message part
Re: [Vote] Releasing 2.1.8 tomorrow
Le 8 nov. 05, à 11:54, Carsten Ziegeler a écrit : Please cast your votes for releasing 2.1.8 tomorrow, 8th of November. +1 -Bertrand
Re: [Vote] Releasing 2.1.8 tomorrow
Carsten Ziegeler wrote: This is another try to get 2.1.8 finally out: Please cast your votes for releasing 2.1.8 tomorrow, 8th of November. +1 Carsten -- Carsten Ziegeler - Open Source Group, SN AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
Re: [Vote] Releasing 2.1.8 tomorrow
Carsten Ziegeler wrote: This is another try to get 2.1.8 finally out: Please cast your votes for releasing 2.1.8 tomorrow, 8th of November. Carsten +1 Ralph
Re: [Vote] Releasing 2.1.8 tomorrow
On 08.11.2005 11:54, Carsten Ziegeler wrote: This is another try to get 2.1.8 finally out: Please cast your votes for releasing 2.1.8 tomorrow, 8th of November. +1 What about the three day voting period ;) Jörg
Re: [Vote] Releasing 2.1.8 tomorrow
Carsten Ziegeler wrote: This is another try to get 2.1.8 finally out: Please cast your votes for releasing 2.1.8 tomorrow, 8th of November. -1 ... People have not addressed the documentation side of things. See other recent email on this topic to which nobody replied. We will not be able to update the website, the documentation will not be packaged with the release nor available alongside, there is currently a changed URL-space which will bust links, and there will be no list of changes for the release. As i warned a long time ago, the re-arrangement of documentation should not have been done until the 2.2 release. I don't have time to fix it or suggest solutions. Other people need to get involved. If people are not going to help fix the new Daisy-based documentation for this release, then we we need to repair the old documentation building system, e.g. the index.xml file seems to be missing and various other source files have been deleted. Another issue is that normally i run a program to scan for license issues, but have not found time. -David
Re: [Vote] Releasing 2.1.8 tomorrow
Le 9 nov. 05, à 01:37, David Crossley a écrit : ...As i warned a long time ago, the re-arrangement of documentation should not have been done until the 2.2 release... Fully agreed, staying with the old docs for 2.1.8 seems much easier, and 2.2 is a good time to make a transition on the docs. ...If people are not going to help fix the new Daisy-based documentation for this release, then we we need to repair the old documentation building system, e.g. the index.xml file seems to be missing and various other source files have been deleted... Could we do the release and regenerate only the index and news pages? I don't think there have been much changes to other parts of the old docs. I'm strongly for releasing 2.1.8 with the old docs and take our time to improve them for 2.2. -Bertrand
Re: [Vote] Releasing 2.1.8 tomorrow
Bertrand Delacretaz wrote: David Crossley a ?crit : ...As i warned a long time ago, the re-arrangement of documentation should not have been done until the 2.2 release... Fully agreed, staying with the old docs for 2.1.8 seems much easier, and 2.2 is a good time to make a transition on the docs. ...If people are not going to help fix the new Daisy-based documentation for this release, then we we need to repair the old documentation building system, e.g. the index.xml file seems to be missing and various other source files have been deleted... Could we do the release and regenerate only the index and news pages? I don't think there have been much changes to other parts of the old docs. I'm strongly for releasing 2.1.8 with the old docs and take our time to improve them for 2.2. Good idea, i was wondering about that as a workaround. We can easily update the complete top-level docs, same as before. http://wiki.apache.org/cocoon/CocoonWebsiteUpdate We might be able to repair the old 2.1 docs sufficiently to get the changes.html page built and update only that page. Doing 'svn log status.xml' shows that quite a lot of changes (~130) are noted since 2.1.7 (March 23 2005). Yes, i just tried a trick to build the changes.html and it works. The rest is busted, but this works. svn diff forrest.properties Index: forrest.properties === --- forrest.properties (revision 293073) +++ forrest.properties (working copy) @@ -101,7 +101,7 @@ # The URL to start crawling from #project.start-uri=linkmap.html -project.start-uri=index.html +project.start-uri=changes.html
Re: [Vote] Releasing 2.1.8 tomorrow
David Crossley wrote: there is currently a changed URL-space which will bust links, David, What changed URLs have you noticed, so far? If there is a list, it will help fixing problems. Myself, I noticed that http://cocoon.apache.org/2.1/introduction.html became http://forrest.zones.apache.org/ft/build/cocoon-docs /2.1/documentation/introduction.html It probably can be easily fixed in the navigation document. I'm thinking of removing node ID for 'documentation' node; or setting it to '.' might do the trick. Vadim
Re: [Vote] Releasing 2.1.8 tomorrow
Vadim Gritsenko wrote: David Crossley wrote: there is currently a changed URL-space which will bust links, David, What changed URLs have you noticed, so far? If there is a list, it will help fixing problems. Myself, I noticed that http://cocoon.apache.org/2.1/introduction.html became http://forrest.zones.apache.org/ft/build/cocoon-docs /2.1/documentation/introduction.html It probably can be easily fixed in the navigation document. I'm thinking of removing node ID for 'documentation' node; or setting it to '.' might do the trick. I was referring to the general problems described here: http://marc.theaimsgroup.com/?l=xml-cocoon-devm=113132799820935 Your suggestion might solve that. -David
Re: [Vote] Releasing 2.1.8 tomorrow
David Crossley wrote: Another issue is that normally i run a program to scan for license issues, but have not found time. I will try to make some time to do that tonight. -David
Re: [Vote] Releasing 2.1.8 tomorrow
David Crossley wrote: Bertrand Delacretaz wrote: David Crossley a ?crit : ...As i warned a long time ago, the re-arrangement of documentation should not have been done until the 2.2 release... Fully agreed, staying with the old docs for 2.1.8 seems much easier, and 2.2 is a good time to make a transition on the docs. ...If people are not going to help fix the new Daisy-based documentation for this release, then we we need to repair the old documentation building system, e.g. the index.xml file seems to be missing and various other source files have been deleted... Could we do the release and regenerate only the index and news pages? I don't think there have been much changes to other parts of the old docs. I'm strongly for releasing 2.1.8 with the old docs and take our time to improve them for 2.2. Good idea, i was wondering about that as a workaround. We can easily update the complete top-level docs, same as before. http://wiki.apache.org/cocoon/CocoonWebsiteUpdate We might be able to repair the old 2.1 docs sufficiently to get the changes.html page built and update only that page. Doing 'svn log status.xml' shows that quite a lot of changes (~130) are noted since 2.1.7 (March 23 2005). Yes, i just tried a trick to build the changes.html and it works. The rest is busted, but this works. svn diff forrest.properties Index: forrest.properties === --- forrest.properties (revision 293073) +++ forrest.properties (working copy) @@ -101,7 +101,7 @@ # The URL to start crawling from #project.start-uri=linkmap.html -project.start-uri=index.html +project.start-uri=changes.html Uh'oh i see that someone has deleted branches/BRANCH_2_1_X/forrest.properties so i need to get that back. Can someone please explain how to find out when that file was removed from SVN. I tried searching my local mail archives for [EMAIL PROTECTED] but cannot find it. -David
Re: [Vote] Releasing 2.1.8 tomorrow
David Crossley wrote: David Crossley wrote: Bertrand Delacretaz wrote: David Crossley a ?crit : ...As i warned a long time ago, the re-arrangement of documentation should not have been done until the 2.2 release... Fully agreed, staying with the old docs for 2.1.8 seems much easier, and 2.2 is a good time to make a transition on the docs. ...If people are not going to help fix the new Daisy-based documentation for this release, then we we need to repair the old documentation building system, e.g. the index.xml file seems to be missing and various other source files have been deleted... Could we do the release and regenerate only the index and news pages? I don't think there have been much changes to other parts of the old docs. I'm strongly for releasing 2.1.8 with the old docs and take our time to improve them for 2.2. Good idea, i was wondering about that as a workaround. We can easily update the complete top-level docs, same as before. http://wiki.apache.org/cocoon/CocoonWebsiteUpdate We might be able to repair the old 2.1 docs sufficiently to get the changes.html page built and update only that page. Doing 'svn log status.xml' shows that quite a lot of changes (~130) are noted since 2.1.7 (March 23 2005). Yes, i just tried a trick to build the changes.html and it works. The rest is busted, but this works. svn diff forrest.properties Index: forrest.properties === --- forrest.properties (revision 293073) +++ forrest.properties (working copy) @@ -101,7 +101,7 @@ # The URL to start crawling from #project.start-uri=linkmap.html -project.start-uri=index.html +project.start-uri=changes.html Uh'oh i see that someone has deleted branches/BRANCH_2_1_X/forrest.properties so i need to get that back. Can someone please explain how to find out when that file was removed from SVN. I tried searching my local mail archives for [EMAIL PROTECTED] but cannot find it. http://marc.theaimsgroup.com/?l=xml-cocoon-cvsm=112947580724456w=2 Upayavira
Re: [Vote] Releasing 2.1.8 tomorrow
David Crossley wrote: Carsten Ziegeler wrote: This is another try to get 2.1.8 finally out: Please cast your votes for releasing 2.1.8 tomorrow, 8th of November. -1 ... People have not addressed the documentation side of things. See other recent email on this topic to which nobody replied. We will not be able to update the website, the documentation will not be packaged with the release nor available alongside, there is currently a changed URL-space which will bust links, and there will be no list of changes for the release. Ok, I'll wait with building the release until this problem is solved. As soon as I get a notice that all issues with the docs have been resolved I'll go ahead. Carsten -- Carsten Ziegeler - Open Source Group, SN AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
