You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by is...@cocoondev.org on 2004/07/19 09:03:34 UTC
[issues] Created: (FOR-220) Include the pdf-tab.xmap as standard feature
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.cocoondev.org/jira//secure/ViewIssue.jspa?key=FOR-220
Here is an overview of the issue:
---------------------------------------------------------------------
Key: FOR-220
Summary: Include the pdf-tab.xmap as standard feature
Type: New Feature
Status: Unassigned
Priority: Minor
Project: Forrest
Component: None
Versions:
0.7
Assignee:
Reporter: Thorsten Scherler
Created: Mon, 19 Jul 2004 9:03 AM
Updated: Mon, 19 Jul 2004 9:03 AM
Description:
This feature will allow aggregate parts of the site.xml like described in the howto that was added because of FOR-218.
The basic idea is to include the sitemaps described in the howto (src/documentation/content/xdocs/howto/howto-pdf-tab.xml) to the *.xmap folder. This way it will be possible to define aggregation parts with the attribute "wholesite='true'".
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.cocoondev.org/jira//Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
Re: [Proposal] what can happen during feature freeze
Posted by Dave Brondsema <da...@brondsema.net>.
David Crossley wrote:
> (Again use a situation as an example to develop our procedures.)
>
> Thorsten Scherler wrote:
> (Re: FOR-220: Include the pdf-tab.xmap as standard feature)
>
>>I know it is feature freeze, but I reckon it would be a
>>good idea to include this feature in 0.6!
>>
>>Have a look at the how-to it is pretty straight forward
>>and _screams_ for being a standard feature ;-).
>>
>>We would have to include the pdf-tab.xmap and add the
>>match in the sitemap.xmap. That's it!
>
>
> If that is really all, then it seems that this does not
> risk introducing more issues.
>
> (Also add a demo to "seed site" and then run 'build test'.)
>
> If you have the energy, then i would say do it. There is
> still time to retract before release if it doesn't work out.
>
> By the way, i think that you have done the correct thing
> by asking the list.
>
> This should be our procedure during a feature freeze:
>
> * Adding or changing documentation is okay.
>
> * Fixing bugs is okay, but being careful to add/run
> tests to ensure that it doesn't break other stuff.
>
> * Concentrate on closing issues for the imminent release.
>
> * Adding new things that we are sure will not introduce
> new issues. However, ask the dev list.
>
* make a branch if you're really eager to start working on a big new
feature and there is not much you can do to help close out the remaining
issues
--
Dave Brondsema : dave@brondsema.net
http://www.splike.com : programming
http://csx.calvin.edu : student org
http://www.brondsema.net : personal
[Proposal] what can happen during feature freeze
Posted by David Crossley <cr...@apache.org>.
(Again use a situation as an example to develop our procedures.)
Thorsten Scherler wrote:
(Re: FOR-220: Include the pdf-tab.xmap as standard feature)
> I know it is feature freeze, but I reckon it would be a
> good idea to include this feature in 0.6!
>
> Have a look at the how-to it is pretty straight forward
> and _screams_ for being a standard feature ;-).
>
> We would have to include the pdf-tab.xmap and add the
> match in the sitemap.xmap. That's it!
If that is really all, then it seems that this does not
risk introducing more issues.
(Also add a demo to "seed site" and then run 'build test'.)
If you have the energy, then i would say do it. There is
still time to retract before release if it doesn't work out.
By the way, i think that you have done the correct thing
by asking the list.
This should be our procedure during a feature freeze:
* Adding or changing documentation is okay.
* Fixing bugs is okay, but being careful to add/run
tests to ensure that it doesn't break other stuff.
* Concentrate on closing issues for the imminent release.
* Adding new things that we are sure will not introduce
new issues. However, ask the dev list.
--
David Crossley
Re: [issues] Created: (FOR-220) Include the pdf-tab.xmap as standard
feature
Posted by Thorsten Scherler <th...@juntadeandalucia.es>.
Hello devs,
I know it is feature freeze, but I reckon it would be a good idea to
include this feature in 0.6!
Have a look at the how-to it is pretty straight forward and _screams_
for being a standard feature ;-).
We would have to include the pdf-tab.xmap and add the match in the
sitemap.xmap. That's it!
WDYT?
king regards
thorsten
issues@cocoondev.org wrote:
>Message:
>
> A new issue has been created in JIRA.
>
>---------------------------------------------------------------------
>View the issue:
>
> http://issues.cocoondev.org/jira//secure/ViewIssue.jspa?key=FOR-220
>
>
>Here is an overview of the issue:
>---------------------------------------------------------------------
> Key: FOR-220
> Summary: Include the pdf-tab.xmap as standard feature
> Type: New Feature
>
> Status: Unassigned
> Priority: Minor
>
> Project: Forrest
> Component: None
> Versions:
> 0.7
>
> Assignee:
> Reporter: Thorsten Scherler
>
> Created: Mon, 19 Jul 2004 9:03 AM
> Updated: Mon, 19 Jul 2004 9:03 AM
>
>Description:
>This feature will allow aggregate parts of the site.xml like described in the howto that was added because of FOR-218.
>
>The basic idea is to include the sitemaps described in the howto (src/documentation/content/xdocs/howto/howto-pdf-tab.xml) to the *.xmap folder. This way it will be possible to define aggregation parts with the attribute "wholesite='true'".
>
>
>---------------------------------------------------------------------
>JIRA INFORMATION:
>This message is automatically generated by JIRA.
>
>If you think it was sent incorrectly contact one of the administrators:
> http://issues.cocoondev.org/jira//Administrators.jspa
>
>If you want more information on JIRA, or have a bug to report see:
> http://www.atlassian.com/software/jira
>
>
>
>
--
Thorsten Scherler
Departamento de Desarrollo de Proyectos
Sociedad Andaluza para el Desarrollo de la Sociedad de la Información S.A.U.