cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Lundquist (JIRA)" <>
Subject [jira] Commented: (COCOON-1956) Project site "Changes" page should be split up by release
Date Sun, 19 Nov 2006 21:15:38 GMT
    [ ] 
Mark Lundquist commented on COCOON-1956:

Following that, 2 more suggestions:

1) The JIRA site admits of categories for issues, e.g. Core, Flowscript, Blocks: Forms, etc.
 Could we organize the items on each release's "Changes" page by these categories?  I realize
that not all changes are associated with a JIRA issue; nevertheless it should be straightforward
to classify those changes that were committed without any JIRA issue into the same categories
as well, for the sake of better organization.

2) In terms of navigation: we could of course add sidebar menu sub-items for the per-release
pages.  But it might be nicer to keep the one "Changes", and have that link to a landing page
that would list all the releases with a link to the full changes page for each release.  This
landing page could give a short summary of the "highlights" for each release, e.g. as a list
of bullet items.  The text in those summary items could even include links to the relevant
places in the User Guide.

> Project site "Changes" page should be split up by release
> ---------------------------------------------------------
>                 Key: COCOON-1956
>                 URL:
>             Project: Cocoon
>          Issue Type: Improvement
>          Components: - Documentation
>    Affects Versions: 2.2-dev (Current SVN), 2.1.10-dev (current SVN)
>            Reporter: Mark Lundquist
>            Priority: Minor
> The "Changes" page ( is getting really long.
 I think we should split this material up, with a separate page for each release.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message