Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <15050394.1164048663212.JavaMail.jira@brutus>
Date: Mon, 20 Nov 2006 10:51:03 -0800 (PST)
From: "Mark Lundquist (JIRA)" <jira@apache.org>
To: dev@cocoon.apache.org
Subject: [jira] Commented: (COCOON-1956) Project site "Changes" page should
 be split up by release
In-Reply-To: <16376634.1163968237040.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

    [ http://issues.apache.org/jira/browse/COCOON-1956?page=3Dcomments#acti=
on_12451391 ]=20
           =20
Mark Lundquist commented on COCOON-1956:
----------------------------------------

Right... in the 2.2 world, blocks can be on their own release cycles anyway=
, so a single changes page =E2=80=94 either per major release like in 2.1, =
or per minor release like I was suggesting) doesn't even really make sense =
anymore.

Yeah... I would say, thanks for the attention, and go ahead and close it.


> Project site "Changes" page should be split up by release
> ---------------------------------------------------------
>
>                 Key: COCOON-1956
>                 URL: http://issues.apache.org/jira/browse/COCOON-1956
>             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 (http://cocoon.apache.org/2.1/changes.html) is getting=
 really long.  I think we should split this material up, with a separate pa=
ge for each release.

--=20
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: htt=
p://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira