If people have concerns about the dates then please speak up
otherwise please vote on this Release Plan.
One reason for doing a vote is to ensure that it is the
PMC as a whole that prepares and issues the release, rather
than an individual. Such procedures give us the protection
accorded by the AS
David Crossley wrote:
>
> In any case, it needs someone to create the Windows packages.
> See http://forrest.apache.org/procedures/release/How_to_release.html
> for general background and specifically the
> http://forrest.apache.org/procedures/release/How_to_release.html#BuildDist
> at Steps 11 to
On Fri, 2007-03-23 at 13:13 +, [EMAIL PROTECTED] wrote:
> Author: gmcdonald
> Date: Fri Mar 23 06:13:23 2007
> New Revision: 521716
>
> URL: http://svn.apache.org/viewvc?view=rev&rev=521716
> Log:
> Add some definitions, Issue FOR-639
>
...
> +Hooks are applied currently in the themes.core pl
On Fri, 2007-03-23 at 11:45 +, [EMAIL PROTECTED] wrote:
> Author: gmcdonald
> Date: Fri Mar 23 04:45:03 2007
> New Revision: 521680
>
> URL: http://svn.apache.org/viewvc?view=rev&rev=521680
> Log:
> Fix typos,update example structurer filename
...
> -only requesting what the strucuter
> Author: gmcdonald
> Date: Mon Mar 26 05:16:23 2007
> New Revision: 522492
>
> URL: http://svn.apache.org/viewvc?view=rev&rev=522492
> Log:
> Entries that were removed from main status.xml now put into their respective
> plugins status.xml file, related to FOR-865
>
> Modified:
>
> forrest
Ferdinand Soethe wrote:
I just noticed that there are quite a few changes in forrest.xmap that
require changes to
"How to customize processing of html source"
Is it correct to say that (forrest.xmap line 216)
will kick in when content is prov
Ferdinand Soethe wrote:
I have started working on FOR-922 adjusting sitemap-references to the
changes in the sitemap.
What I'm confused about is that the cited (old) sitemap as well as the
current one display the same revision number in the head of the file
$Revision: 1.12 $
How can that be a
Just found the idgen-step where it has always been (in the
body-*.html-matcher). Pardon my confusion. Problem solved.
Ferdinand
As far as I can make sense from the many comments in forrest.xmap ;-)
the processing of *.html source files happens in line 238
>
>
>
>
>
now following {lm:transform.html.document} I find that
locationmap.xml loads a secondary locationmap in line 69
I just noticed that there are quite a few changes in forrest.xmap that
require changes to
"How to customize processing of html source"
Is it correct to say that (forrest.xmap line 216)
>
>
>
> src="{lm:plugin.xmap.input}"
>
I have started working on FOR-922 adjusting sitemap-references to the
changes in the sitemap.
What I'm confused about is that the cited (old) sitemap as well as the
current one display the same revision number in the head of the file
> $Revision: 1.12 $
How can that be after all these changes? Or
[
https://issues.apache.org/jira/browse/FOR-865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484121
]
Gavin commented on FOR-865:
---
List reviewed. We need to add mentions for :-
DOAP
SOLR
FEEDER
WIKI
PDF*
Although PDF is more o
[
https://issues.apache.org/jira/browse/FOR-865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484110
]
Gavin commented on FOR-865:
---
I have moved all (that I can see of) plugin related entries from
site-author/status.xml to its r
Ross Gardler wrote:
> >David Crossley commented on FOR-635:
> >
> >
> >For me, in 'forrest run' mode all images work in html. In PDF only two
> >images work (#4 in group 1 and #3 in group 2).
>
> Interesting...
>
> All images work in html, that's fine.
>
> St
I see we have touched a bit about being careful with working in whiteboard.
I committed a few changes the other day updating the dispatcher docs and
glossary. Since then a site publish has been done, these docs have not been
updated. I see on the site the procedure for publishing plugins, but what
Cyriaque Dupoirieux wrote:
le 25/03/2007 01:26 Ross Gardler a écrit :
Cyriaque Dupoirieux wrote:
Ross,
If you think this commit correct the FOR-962 -
https://issues.apache.org/jira/browse/FOR-962 -, just tell me and
I'll close it.
I've not tested it, but it looks like an OK workaround.
le 25/03/2007 01:26 Ross Gardler a écrit :
Cyriaque Dupoirieux wrote:
Ross,
If you think this commit correct the FOR-962 -
https://issues.apache.org/jira/browse/FOR-962 -, just tell me and
I'll close it.
I've not tested it, but it looks like an OK workaround.
You are cruel with me to sa
David Crossley (JIRA) wrote:
[ https://issues.apache.org/jira/browse/FOR-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483989 ]
David Crossley commented on FOR-635:
For me, in 'forrest run' mode all images work in ht
18 matches
Mail list logo
