forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FOR-865) Add missing entries to status.xml to generate the changes list
Date Fri, 30 Mar 2007 03:15:25 GMT

    [ https://issues.apache.org/jira/browse/FOR-865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485405
] 

Gavin commented on FOR-865:
---------------------------

All Jira Issues that I can see as relevent have now been added to the appropriate status.xml
file(s)

I was attempting next to follow Thorstens comments above but have an error:

d:\apache2>java -jar saxon/saxon8.jar -o status.xml log.xml svn2changes.xsl
Error on line 52 of file:/d:/apache2/svn2changes.xsl:
  XPTY0004: Cast does not allow an empty sequence
Transformation failed: Run-time errors were reported

I'm looking into it

> Add missing entries to status.xml to generate the changes list
> --------------------------------------------------------------
>
>                 Key: FOR-865
>                 URL: https://issues.apache.org/jira/browse/FOR-865
>             Project: Forrest
>          Issue Type: Task
>          Components: Core operations, Documentation and website
>    Affects Versions: 0.8-dev
>            Reporter: David Crossley
>         Assigned To: Gavin
>            Priority: Blocker
>             Fix For: 0.8-dev
>
>         Attachments: log.xml, status.xml, svn2changes.xsl
>
>
> There are insufficient entries in our site-author/status.xml to generate the changes.html
for the upcoming release.
> Besides informing users of the major changes and providing cross-links to the issue tracker,
this file also provides recognition of contributions ... at the moment there are too few.
It also has the importance=high attribute, which generates our release announcement ... again,
too few.
> Re: better use of changes.html (Was: Community health)
> http://marc.theaimsgroup.com/?t=114274836600001

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message