[prev in list] [next in list] [prev in thread] [next in thread] 

List:       struts-dev
Subject:    Re: [PROPOSAL] Target tickets to milestones and use as roadmap
From:       Patrick Lightbody <plightbo () gmail ! com>
Date:       2005-11-30 19:51:09
Message-ID: c372afa40511301151l4e276fc9he5ae66b5f8520301 () mail ! gmail ! com
[Download RAW message or body]

What we have done with WebWork is use Confluence to generate all our
documentation. Then we use the JIRA macro plugin to include all the
issues. We also have a standard Confluence template for release notes,
making each release consistent:

http://wiki.opensymphony.com/display/WW/Previous+releases

For a specific release, see:

http://wiki.opensymphony.com/display/WW/WebWork+2.2

Note that while we show all the issues, we also have a high level
description of the key changes for the release that is written by
hand. We also do some other neat tricks you  guys might be interested
in, like generating documentation based on code in CVS using a
"snippet" macro that we borrowed from CodeHaus and extended.

For example, see the ActionMapper reference docs:

http://wiki.opensymphony.com/display/WW/ActionMapper

All the "yellow content" comes from the source files directly.When the
content is exported, the yellow background and "refresh link" are not
rendered.

Patrick

On 11/30/05, Hubert Rabago <hrabago@gmail.com> wrote:
> On 11/30/05, Niall Pemberton <niall.pemberton@gmail.com> wrote:
> > Maybe jira has something smarter, but I found a maven feature recently
> > working on Commons Resources - you can specify an "issue" number in
> > the change log and attribute credit ("due-to") and as long as you have
> > the issue tracking *format* configured in your project.properties it
> > will automatically generate a link and "thanks to" text.
> >
> > This is what it looks like:
> > http://tinyurl.com/9qjq5
> >
> > This is what it generates:
> > http://jakarta.apache.org/commons/resources/changes-report.html
> >
> > Niall
>
> Oh that's right.  I remember seeing you use those in the commit
> messages, but I didn't follow through to figure out where they ended
> up.
>
>
> On 11/30/05, Don Brown <mrdon@twdata.org> wrote:
> > Yeah, I've been using that changes thing with stxx for years now.  I believe it
> > started with Forrest.  Anyways, sure, that would work too, although I'd prefer
> > even the xml to be automatically generated.  What if we went back to having a
> > commit message template that could be parsed for info like this?
>
> I wouldn't mind that.  "went back" - I didn't know there was one before.
>
> Hubert
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]