You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Brian K. Wallace" <br...@transmorphix.com> on 2006/03/23 19:42:06 UTC
Assembly of release notes
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Question from the curious:
When creating a release that has the nifty "here's what's changed"
(with the hammer, improvement, etc icons), how is that generated? My
presumption would be a Jira hook... or SVN->Jira, but my presumptions
have been known to be way off before.
Any pointers to that kind of generation would be appreciated.
[Initially for 3.X series, but also for 4.X - I see a couple places
where this information is displayed, but not where it comes from]
Brian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
iD8DBQFEIuv+aCoPKRow/gARAghRAKDTOHfK/1sNuEXw2sGQFRgMZbbJWQCghFpz
ET2fzPExu5aNVvuKsl/DQpA=
=9xvY
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Assembly of release notes
Posted by "Brian K. Wallace" <br...@transmorphix.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Kevin Menard wrote:
> I'm pretty sure it's all done in the status.xml file, which gets processed
> by forrest. If you look at any of the commit messages, you should find a
> corresponding update to that file.
>
Hmmm... Well - I see where that has one line for 3.0.4... was hoping it
was more automated than manual addition. Thanks for the answer, tho' -
now I know where to go.
*whistling Hi-Ho Hi-Ho it's off to Jira and SVN I go* :-D
Thanks again
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
iD8DBQFEIu4EaCoPKRow/gARAoAFAJ4n7+yoOxCp+Aa2NSmdR0QClUL84ACdGW5G
Gr7yJ+erCxNHNeL2REQhmWI=
=u8oc
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Assembly of release notes
Posted by Kevin Menard <km...@servprise.com>.
I'm pretty sure it's all done in the status.xml file, which gets processed
by forrest. If you look at any of the commit messages, you should find a
corresponding update to that file.
--
Kevin
On 3/23/06 1:42 PM, "Brian K. Wallace" <br...@transmorphix.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Question from the curious:
>
> When creating a release that has the nifty "here's what's changed"
> (with the hammer, improvement, etc icons), how is that generated? My
> presumption would be a Jira hook... or SVN->Jira, but my presumptions
> have been known to be way off before.
> Any pointers to that kind of generation would be appreciated.
> [Initially for 3.X series, but also for 4.X - I see a couple places
> where this information is displayed, but not where it comes from]
>
> Brian
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.5 (MingW32)
>
> iD8DBQFEIuv+aCoPKRow/gARAghRAKDTOHfK/1sNuEXw2sGQFRgMZbbJWQCghFpz
> ET2fzPExu5aNVvuKsl/DQpA=
> =9xvY
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org