forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thorsten Scherler <thors...@apache.org>
Subject Re: [jira] Commented: (FOR-865) Add missing entries to status.xml to generate the changes list
Date Sat, 03 Jun 2006 19:54:16 GMT
El vie, 02-06-2006 a las 02:15 +0000, David Crossley (JIRA) escribió:
>     [ http://issues.apache.org/jira/browse/FOR-865?page=comments#action_12414339 ] 
> 
> David Crossley commented on FOR-865:
> ------------------------------------
> 
> Thanks, this is useful for browsing to gather the important changes into our main status.xml
> 
> mkdir FOR-865-status; cd FOR-865-status
> forrest seed
> mv ~/Desktop/status.xml src/documentation/content/xdocs/
> edit forrest.properties to add projectInfo plugin
> edit src/documentation/content/locationmap.xml
> to add:
> <match pattern="project.status">
>  <location src="{project:content.xdocs}/status.xml" />
> </match>
> 
> forrest run
> http://localhost:8888/changes.html
> 

Thanks for this nice summary how to see the status.xml made from svn and
their actual use.

Yes, I even thought it might be a good idea to add it to the release as
status-svn.xml. This way the devs can directly go to specific svn
actions via the viewsvn and see the code changes.

The reason why I create it in the first place, David already has shown
with
http://svn.apache.org/viewvc?rev=411149&view=rev
http://svn.apache.org/viewvc?rev=411152&view=rev
http://svn.apache.org/viewvc?rev=411153&view=rev

This let us compare our status and the work done in our rep. I still
need to create lots of status entries and I needed a handy way to see my
commits.

salu2

> > Add missing entries to status.xml to generate the changes list
> > --------------------------------------------------------------
> >
> >          Key: FOR-865
> >          URL: http://issues.apache.org/jira/browse/FOR-865
> >      Project: Forrest
> >         Type: Task
> 
> >   Components: Documentation and website, Core operations
> >     Versions: 0.8-dev
> >     Reporter: David Crossley
> >     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
> 
-- 
thorsten

"Together we stand, divided we fall!" 
Hey you (Pink Floyd)


Mime
View raw message