You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Ross Gardler <rg...@apache.org> on 2004/11/20 15:47:10 UTC
Re: generating the changes.xml from svn
[cross posted to Forrest-dev]
Gregor J. Rothfuss wrote:
> Gregor J. Rothfuss wrote:
>
>> thanks to stefano, i learned about svn log -v --xml
>>
>> this results in a 3MB file that has all the commit logs since lenya
>> cvs was started (january 2002). we can easily generate the forrest
>> changes.xml out of it. i'll take a shot at the necessary xsl.
>>
>> for the future, this means we need to make an extra effort to have
>> meaningful commit messages and atomic commits (to avoid duplicate
>> messages about the same change).
>
>
> ok, http://lenya.apache.org/changes.html
This is cool and very good timing too because I just committed a logs
plugin to Forrest. This plugin embeds log files (currently only J2SE
Java logs) in a Forrest published site.
The problem I see with generating changes.xml from svn logs is that the
svn logs are too fine grained and often have multiple commits for the
same/similar things (guidelines are all very well but it will still
happen). There is certainly value in this level of detail for developers
but for a changelog aimed at users when a release is made I think that
there is an overwhelming amount of detail.
So I have a suggestion:
Status.xml remains as it is, manually maintained and used for user
focussed changelogs (in the future we could have a token in the commit
message indicate that the log entry is intended to be included in
changes.html, but that is for later).
Your stylesheet goes into the Forrest logs plugin and is used to
generate a developer focussed changelog with links to the SVN diffs and
all the cool stuff you have.
Moving the stylesheet into a Forrest plugin will increase the number of
projects using this and should result in many improvments such as those
you suggest.
I will move your stylesheet over to the Forrest plugin for you are OK
with me doing that.
Ross
Re: generating the changes.xml from svn
Posted by "Gregor J. Rothfuss" <gr...@apache.org>.
Ross Gardler wrote:
> Yeah I know I can just take it but I would rather not duplicate it
> across projects. If I can integrate it into the plugin and it still
> provide what Lenya needs that is a far better solution (i.e. one
> solution rather than two).
im happy to move it to forrest. it was just a quick proof of concept :)
there are a couple problems with it that would need to be resolved i think.
* port to XSLT 1.0 by using muenchian grouping
* analyse resource usage (my build went from 2 to 11 min with the diff
links enabled)
* add grouping by versions (by specifying SVN revisions for each
release, and redoing the grouping to be based on that.)
* link autodiscovery? eg turn #43534 into a zilla link
some of these are just nice to haves, but the first two are probably
good to have.
--
Gregor J. Rothfuss
COO, Wyona Content Management Solutions http://wyona.com
Apache Lenya http://lenya.apache.org
gregor.rothfuss@wyona.com gregor@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Apache Lenya Project http://lenya.apache.org
Re: generating the changes.xml from svn
Posted by Ross Gardler <rg...@apache.org>.
Thorsten Scherler wrote:
> Ross Gardler escribió:
>
>> I will move your stylesheet over to the Forrest plugin for you are OK
>> with me doing that.
>>
>
> Has the same license ;-)
> just take what you need.
Yeah I know I can just take it but I would rather not duplicate it
across projects. If I can integrate it into the plugin and it still
provide what Lenya needs that is a far better solution (i.e. one
solution rather than two).
Ross
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Apache Lenya Project http://lenya.apache.org
Re: generating the changes.xml from svn
Posted by Thorsten Scherler <th...@apache.org>.
Ross Gardler escribió:
> I will move your stylesheet over to the Forrest plugin for you are OK
> with me doing that.
>
Has the same license ;-)
just take what you need.
--
thorsten
"Together we stand, divided we fall"
Hey you (Pink Floyd)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Apache Lenya Project http://lenya.apache.org
Re: generating the changes.xml from svn
Posted by Ross Gardler <rg...@apache.org>.
Antonio Gallardo wrote:
> I saw the Gregor work and is amazing. I liked it. I was think if is a
> worth to make the same for CVS? I know projects are migrating from CVS to
> SVN.
+1 (although this is relevant on the Forrest list not Lenya - my fault
for cross posting - sorry)
Ross
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Apache Lenya Project http://lenya.apache.org
Re: generating the changes.xml from svn
Posted by "Gregor J. Rothfuss" <gr...@apache.org>.
Antonio Gallardo wrote:
> http://ant.apache.org/manual/CoreTasks/cvstagdiff.html
looks interesting :) doesnt scratch my itch now that we use SVN, but
more power to the person who wants to use that with my XSL.
--
Gregor J. Rothfuss
COO, Wyona Content Management Solutions http://wyona.com
Apache Lenya http://lenya.apache.org
gregor.rothfuss@wyona.com gregor@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Apache Lenya Project http://lenya.apache.org
Re: generating the changes.xml from svn
Posted by Antonio Gallardo <ag...@agssa.net>.
Gregor J. Rothfuss dijo:
> Antonio Gallardo wrote:
>> Hi Ross:
>>
>> I saw the Gregor work and is amazing. I liked it. I was think if is a
>> worth to make the same for CVS? I know projects are migrating from CVS
>> to
>> SVN.
>
> if someone figures out how to generate the CVS changelog in xml, sure.
> note that with cvs, you won't get the cool links to diffs since cvs is
> not atomic.
Because I was tired of the eclipse slowness working with cocoon, on the
weekend (between the friend wedding and other things), I was playing with
the cocoon build system. I found this interesting Ant task that can do the
work:
http://ant.apache.org/manual/CoreTasks/cvstagdiff.html
WDYT?
Best Regards,
Antonio Gallardo.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Apache Lenya Project http://lenya.apache.org
Re: generating the changes.xml from svn
Posted by "Gregor J. Rothfuss" <gr...@apache.org>.
Antonio Gallardo wrote:
> Hi Ross:
>
> I saw the Gregor work and is amazing. I liked it. I was think if is a
> worth to make the same for CVS? I know projects are migrating from CVS to
> SVN.
if someone figures out how to generate the CVS changelog in xml, sure.
note that with cvs, you won't get the cool links to diffs since cvs is
not atomic.
--
Gregor J. Rothfuss
COO, Wyona Content Management Solutions http://wyona.com
Apache Lenya http://lenya.apache.org
gregor.rothfuss@wyona.com gregor@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Apache Lenya Project http://lenya.apache.org
Re: generating the changes.xml from svn
Posted by Antonio Gallardo <ag...@agssa.net>.
Hi Ross:
I saw the Gregor work and is amazing. I liked it. I was think if is a
worth to make the same for CVS? I know projects are migrating from CVS to
SVN.
Best Regards,
Antonio Gallardo.
Ross Gardler dijo:
> [cross posted to Forrest-dev]
>
> Gregor J. Rothfuss wrote:
>> Gregor J. Rothfuss wrote:
>>
>>> thanks to stefano, i learned about svn log -v --xml
>>>
>>> this results in a 3MB file that has all the commit logs since lenya
>>> cvs was started (january 2002). we can easily generate the forrest
>>> changes.xml out of it. i'll take a shot at the necessary xsl.
>>>
>>> for the future, this means we need to make an extra effort to have
>>> meaningful commit messages and atomic commits (to avoid duplicate
>>> messages about the same change).
>>
>>
>> ok, http://lenya.apache.org/changes.html
>
> This is cool and very good timing too because I just committed a logs
> plugin to Forrest. This plugin embeds log files (currently only J2SE
> Java logs) in a Forrest published site.
>
> The problem I see with generating changes.xml from svn logs is that the
> svn logs are too fine grained and often have multiple commits for the
> same/similar things (guidelines are all very well but it will still
> happen). There is certainly value in this level of detail for developers
> but for a changelog aimed at users when a release is made I think that
> there is an overwhelming amount of detail.
>
> So I have a suggestion:
>
> Status.xml remains as it is, manually maintained and used for user
> focussed changelogs (in the future we could have a token in the commit
> message indicate that the log entry is intended to be included in
> changes.html, but that is for later).
>
> Your stylesheet goes into the Forrest logs plugin and is used to
> generate a developer focussed changelog with links to the SVN diffs and
> all the cool stuff you have.
>
> Moving the stylesheet into a Forrest plugin will increase the number of
> projects using this and should result in many improvments such as those
> you suggest.
>
> I will move your stylesheet over to the Forrest plugin for you are OK
> with me doing that.
>
> Ross
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
> For additional commands, e-mail: dev-help@lenya.apache.org
> Apache Lenya Project http://lenya.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Apache Lenya Project http://lenya.apache.org