Upayavira wrote:
I have just done a huge commit (sorry!) of the old 2.1 documentation,
converted into a flat structure with the content formatted as HTML.
I've also committed a site.xml to go with this.
This means we're ready to start the job of moving content across to the
new structure, bit by
Le 14 avr. 05, à 11:51, Upayavira a écrit :
...I think so. I __REALLY__ don't want any of these c21- docs to
survive. They are there for conversion purposes, not for public
consumption...
Sure...OTOH, having no docs at all would block a potential release,
whereas having legacy docs is better tha
Bertrand Delacretaz wrote:
Le 14 avr. 05, à 11:41, Reinhard Poetz a écrit :
...I don't see why we would want to keep the legacy info but if you
think it' necessary, just add the tag. For now I make a test whether
"/meta/legacy" is available and print a warning box...
Ok, we can always change lat
Le 14 avr. 05, à 11:41, Reinhard Poetz a écrit :
...I don't see why we would want to keep the legacy info but if you
think it' necessary, just add the tag. For now I make a test whether
"/meta/legacy" is available and print a warning box...
Ok, we can always change later if needed - YAGNI maybe..
Bertrand Delacretaz wrote:
Le 14 avr. 05, à 10:43, Reinhard Poetz a écrit :
...Instead of legacy.21 we added
userdocs/generators/extractor-generator.html
This should be enough to add the fixme box too - I will update the
stylesheet...
ok no problem, thanks!
But this makes me think: we
Le 14 avr. 05, à 10:43, Reinhard Poetz a écrit :
...Instead of legacy.21 we added
userdocs/generators/extractor-generator.html
This should be enough to add the fixme box too - I will update the
stylesheet...
ok no problem, thanks!
But this makes me think: we might want to keep this in
Bertrand Delacretaz wrote:
Le 13 avr. 05, à 16:46, Upayavira a écrit :
I have just done a huge commit (sorry!) of the old 2.1 documentation,
converted into a flat structure with the content formatted as HTML...
Thanks!
I had planned to mark the published legacy docs, by adding
legacy.21
to each
On 13 Apr 2005, at 19:48, Upayavira wrote:
Jeremy Quinn wrote:
On 13 Apr 2005, at 15:46, Upayavira wrote:
I have just done a huge commit (sorry!) of the old 2.1
documentation, converted into a flat structure with the content
formatted as HTML.
I've also committed a site.xml to go with this.
This
Le 13 avr. 05, à 16:46, Upayavira a écrit :
I have just done a huge commit (sorry!) of the old 2.1 documentation,
converted into a flat structure with the content formatted as HTML...
Thanks!
I had planned to mark the published legacy docs, by adding
legacy.21
to each c21* meta.xml, which causes
Jeremy Quinn wrote:
On 13 Apr 2005, at 15:46, Upayavira wrote:
I have just done a huge commit (sorry!) of the old 2.1 documentation,
converted into a flat structure with the content formatted as HTML.
I've also committed a site.xml to go with this.
This means we're ready to start the job of movin
On 13 Apr 2005, at 15:46, Upayavira wrote:
I have just done a huge commit (sorry!) of the old 2.1 documentation,
converted into a flat structure with the content formatted as HTML.
I've also committed a site.xml to go with this.
This means we're ready to start the job of moving content across to
I have just done a huge commit (sorry!) of the old 2.1 documentation,
converted into a flat structure with the content formatted as HTML.
I've also committed a site.xml to go with this.
This means we're ready to start the job of moving content across to the
new structure, bit by bit. I'll start
12 matches
Mail list logo
