You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by "Mark Lundquist (JIRA)" <ji...@apache.org> on 2006/11/19 21:30:37 UTC
[jira] Created: (COCOON-1956) Project site "Changes" page should be
split up by release
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 page for each release.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (COCOON-1956) Project site "Changes" page should
be split up by release
Posted by "Mark Lundquist (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/COCOON-1956?page=comments#action_12451182 ]
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: 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 page for each release.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [ANN]VTD-XML 1.8
Posted by Reinhard Poetz <re...@apache.org>.
Jimmy Zhang wrote:
> We are thinking about adding exceptions to the current GPL...
Great! Have a look at http://people.apache.org/~cliffs/3party.html. This policy
hasn't been approved by the Apache board yet, but all decisions by Apache
projects about the inclusion of third party libraries are cross-checked against it.
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
___________________________________________________________
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
Re: [ANN]VTD-XML 1.8
Posted by Jimmy Zhang <cr...@comcast.net>.
We are thinking about adding exceptions to the current GPL...
----- Original Message -----
From: "Reinhard Poetz" <re...@apache.org>
To: <de...@cocoon.apache.org>
Sent: Wednesday, November 29, 2006 2:45 AM
Subject: Re: [ANN]VTD-XML 1.8
> Jimmy Zhang wrote:
>> Version 1.8 of VTD-XML is now released. The new features are:
>>
>> · XMLModifier is a easy to use class that takes advantage of the
>> incremental update capability offered by VTD-XML
>>
>> · XPath built-in functions are now almost complete
>>
>> · This release added encoding support for iso-8859-2~10, windows
>> code
>> page 1250~1258
>>
>> · Added various functions to autoPilot that evaluate XPath to
>> string,
>> number and boolean
>>
>> · This release also fixes a number of XPath bugs related to string
>> handling
>>
>> To download the latest release please visit http://vtd-xml.sf.net
>
> Is there any chance of relicensing it under an ASL2 compatible license?
> Otherwise I guess it isn't a real option for the most people around here.
>
> --
> Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
> {Software Engineering, Open Source, Web Applications, Apache Cocoon}
>
> web(log): http://www.poetz.cc
> --------------------------------------------------------------------
>
>
>
>
>
> ___________________________________________________________ Der frhe Vogel
> fngt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail:
> http://mail.yahoo.de
>
Re: [ANN]VTD-XML 1.8
Posted by Reinhard Poetz <re...@apache.org>.
Jimmy Zhang wrote:
> Version 1.8 of VTD-XML is now released. The new features are:
>
> · XMLModifier is a easy to use class that takes advantage of the
> incremental update capability offered by VTD-XML
>
> · XPath built-in functions are now almost complete
>
> · This release added encoding support for iso-8859-2~10, windows
> code
> page 1250~1258
>
> · Added various functions to autoPilot that evaluate XPath to
> string,
> number and boolean
>
> · This release also fixes a number of XPath bugs related to string
> handling
>
> To download the latest release please visit http://vtd-xml.sf.net
Is there any chance of relicensing it under an ASL2 compatible license?
Otherwise I guess it isn't a real option for the most people around here.
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
___________________________________________________________
Der fr�he Vogel f�ngt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
[ANN]VTD-XML 1.8
Posted by Jimmy Zhang <cr...@comcast.net>.
Version 1.8 of VTD-XML is now released. The new features are:
· XMLModifier is a easy to use class that takes advantage of the
incremental update capability offered by VTD-XML
· XPath built-in functions are now almost complete
· This release added encoding support for iso-8859-2~10, windows code
page 1250~1258
· Added various functions to autoPilot that evaluate XPath to string,
number and boolean
· This release also fixes a number of XPath bugs related to string
handling
To download the latest release please visit http://vtd-xml.sf.net
[jira] Closed: (COCOON-1956) Project site "Changes" page should be
split up by release
Posted by "Vadim Gritsenko (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/COCOON-1956?page=all ]
Vadim Gritsenko closed COCOON-1956.
-----------------------------------
Fix Version/s: 2.2-dev (Current SVN)
Resolution: Fixed
> 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
> Fix For: 2.2-dev (Current SVN)
>
>
> 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 page for each release.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (COCOON-1956) Project site "Changes" page should
be split up by release
Posted by "Mark Lundquist (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/COCOON-1956?page=comments#action_12451391 ]
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 — 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 page for each release.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (COCOON-1956) Project site "Changes" page should
be split up by release
Posted by "Vadim Gritsenko (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/COCOON-1956?page=comments#action_12451385 ]
Vadim Gritsenko commented on COCOON-1956:
-----------------------------------------
Changes for 2.2 will be a separate page, so Changes for 2.1 won't be growing anymore (after 2.1.10 release).
Changes list for 2.2 is already split into multiple pages, one page per block. So, should I just close this issue?
> 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 page for each release.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira