You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Davanum Srinivas <di...@yahoo.com> on 2001/10/17 19:01:35 UTC
[C2.0] Should we set a date for 2.0 Final Release?
Team,
Should we set a date for 2.0 Final Release? (or the next Release Candidate)? Am a bit tired of
hearing from people (in my organization) that we cannot switch from C1.X to C2.0 since it is in
Beta/RC Cycle....
Thanks,
dims
=====
Davanum Srinivas - http://jguru.com/dims/
__________________________________________________
Do You Yahoo!?
Make a great connection at Yahoo! Personals.
http://personals.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: let us get serious about 2.0 Final Release
Posted by David Crossley <cr...@indexgeo.com.au>.
Bernhard Huber wrote:
> About documentation in general, I would like to write something
> about the new views, and about the sitemap elements
> map:aggregate, map:part, etc as
> I have noticed that they are not described.
> I will just post the plain text, or should I write it directly in the xml?
It would be best to post as patches to the relevant xdocs
and config files. (Follow contrib.html)
> My english is not perfect so you surely have to review.....
Do not worry about that. If needed, someone will revise it.
--David
> >** Documentation, documentation, documentation
> >- stop apologising for Cocoon 1
> >- positive announcement.xml and index.xml
> >- both of those docs need a concise overiew at top
> >(something less than half-a-page that convinces boss)
> >- much of the documentation is old and still talks about
> >Cocoon 1 configuration methods and issues
> >- much documentation still has "Under construction" notices
> >- people will turn away in droves
> >
> >** cocoon.xconf needs all parameters and components
> >listed and briefly explained as internal documentation
> >
> >
> >
> >** The excellent document "How to Develop Web Applications"
> >and the accompanying webapp.tutorial are missing from
> >the cocoon_20_branch
> >
> >** Better stylesheet for xml.apache.org/cocoon2/
> >- the slow response of the website will not allow 2.0 to
> >make its impact.
>
> I think the problem of the slow response is that neither html-pages, nor
> the images
> has a LastModified, or Expires http-header. Setting the headers for the
> images
> could be accomplished by modifiying the ResourceReader class.
> Trying to speedup without modifying an source you might want to change
> the sitemap of
> documentation setting an expires parameter:
> For example setting an expires parameter values makes the resource to
> 720000 will make the
> resource valid for 1 hour, thus speeding up the loading of documentation
> pages the next 1 hour,
> I think this would help as a first step to speed up the documentation pages:
> The sitemap setting example: <map:match pattern="**images/*.jpg">
> <map:read src="images/{2}.jpg" mime-type="image/jpeg">
> <map:parameter name="expires" value="720000"/>
> </map:read>
> </map:match>
>
> <map:match pattern="**images/*.gif">
> <map:read src="images/{2}.gif" mime-type="image/gif">
> <map:parameter name="expires" value="720000"/>
> </map:read>
> </map:match>
>
> The ResourceReader documentation states:
>
> * The <code>ResourceReader</code> component is used to serve binary data
> * in a sitemap pipeline. It makes use of HTTP Headers to determine if
> * the requested resource should be written to the <code>OutputStream</code>
> * or if it can signal that it hasn't changed.
> *
> * Parameters:
> * <dl>
> * <dt><expires></dt>
> * <dd>This parameter is optional. When specified it determines
> how long
> * in miliseconds the resources can be cached by any proxy or
> browser
> * between Cocoon2 and the requesting visitor.
> * </dd>
> * </dl>
>
> Perhaps setting always a LastModifiedHeader will help too.
>
> >
> >
> >Also the following issues are summarised at
> >documentation/xdocs/plan/release.xml ...
> >
> >** We have many open bugs in bugzilla
> >** Layout the distribution
> >** Ensure that licensing requirements have been met
> >** Decide what to backport from the 2.1 head
> >
> >--David
> >
> >>>--------------------------
> >>>
> >>>>Subject: [C2.0] Should we set a date for 2.0 Final Release?
> >>>>Date: Thu, 18 Oct 2001 14:55:15 +0200
> >>>>From: Martin Man <Ma...@seznam.cz>
> >>>>To: cocoon-dev@xml.apache.org
> >>>>
> >>>>Carsten Ziegeler wrote:
> >>>>
> >>>>>Ok, yes, I didnt check the calendar. Thanks for the hint!
> >>>>>
> >>>>>As I still prefer mondays, we should set the dates to
> >>>>>5th November: RC2
> >>>>>26th November: Final Release
> >>>>>
> >>>>yep, my +1 also for both dates, BTW: without looking to the
> >>>>repository, do we have actualized TODO list... I mean critical
> >>>>isuues (not including documentation) to fix ???
> >>>>
> >>>--------------------------
> >>>
> >>>>Date: Thu, 18 Oct 2001 14:37:57 +0200
> >>>>From: "Carsten Ziegeler" <cz...@sundn.de>
> >>>>To: <co...@xml.apache.org>, <di...@yahoo.com>
> >>>>
> >>>>you're absolutely right. It's the same problem here.
> >>>>Due to the many changes I would propose a RC2.
> >>>>But we still need more documentation! So a good
> >>>>date could be 1st of November for the RC2 and
> >>>>end of november for the final release.
> >>>>
> >>>>But whatever date we decide on for the final
> >>>>release, we *should* stick to it.
> >>>>
> >>>>Carsten
> >>>>Open Source Group sunShine - b:Integrated
> >>>>================================================================
> >>>>Carsten Ziegeler, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
> >>>>www.sundn.de mailto: cziegeler@sundn.de
> >>>>================================================================
> >>>>
> >>>>Dims wrote:
> >>>>
> >>>>>Team,
> >>>>>Should we set a date for 2.0 Final Release? (or the next Release
> >>>>>Candidate)? Am a bit tired of
> >>>>>hearing from people (in my organization) that we cannot switch
> >>>>>from C1.X to C2.0 since it is in
> >>>>>Beta/RC Cycle....
> >>>>>
> >>>>>Thanks,
> >>>>>dims
> >>>>>=====
> >>>>>Davanum Srinivas - http://jguru.com/dims/
> >>>>>
> >>>
> >>>---------------------------------------------------------------------
> >>>To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> >>>For additional commands, email: cocoon-dev-help@xml.apache.org
> >>>
> >>>
> >>>
> >>
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> >For additional commands, email: cocoon-dev-help@xml.apache.org
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: let us get serious about 2.0 Final Release
Posted by Berin Loritsch <bl...@apache.org>.
Bernhard Huber wrote:
> Okay, nice list of headers to set.
>
> Who sets what?
> What is already answered by you.
>
> Who:
.5) HTTP Server
> 1) ServletEngine
> 2) Cocoon
> 2.1) CocoonReader
> 2.2) CocoonSerializer
> 2.3) CocoonGenerators
2.4) CocoonMRUStore (cache implementation)
2.5) CocoonServlet
2.6) CocoonAction
> I think that the ServletEngine won't set any headers, will reread the
> servlet-spec...
There are some set by the HTTP server which may or may not be the
servlet engine.
Out of our control
------------------
Location: ServletEngine (Response.redirectTo())
Server: HTTP Server (can also be added to by Cocoon possibly?)
WWW-Authenticate: ServletEngine (Basic Authentication mechanism)
Proxy-Authenticate: HTTP Server
Content-Encoding: HTTP Server (unless implemented by us)
Our responsibility
------------------
Age: CocoonMRUStore
Vary: CocoonMRUStore/CocoonAction
Retry-After: CocoonServlet (during init time)
Content-Language: CocoonAction/CocoonGenerator/CocoonReader (i18n)
Content-Length: CocoonReader/CocoonMRUStore (only one where we know ahead of time)
Content-Location: CocoonServlet (repeat of the requested URI)
Content-MD5: CocoonReader/CocoonMRUStore (only one where we know ahead of time)--optional
Content-Type: CocoonSerializer
Expires: CocoonMRUStore
Last-Modified: CocoonMRUStore
Allow: CocoonAction/Sitemap?
Unknown responsibility
----------------------
Accept-Ranges
Content-Range
ETag
>
> I have not dived into Cocoon to understand 100% contracts for
> serializer, and generators, and
> if they are allowed to set the http-headers.
>
> But probably it's not the task of the serializer to set the http-headers.
> Thus the http-headers should be set be Cocoon-Servlet after the request
> is handled.
> Is this right?
>
> I will take a look at Cocoon-1 implementation.
>
> Berin Loritsch wrote:
>
>> Bernhard Huber wrote:
>>
>>> Perhaps setting always a LastModifiedHeader will help too.
>>
>>
>>
>> This is one thing that Cocoon may want to include no matter what.
>> Here are the list of
>> valid HTTP 1.1 Headers for responses:
>>
>> Accept-Ranges
>> Age
>> ETag
>> Location
>> Proxy-Authenticate
>> Retry-After
>> Server
>> Vary
>> WWW-Authenticate
>>
>> Brief overview for those who don't know:
>>
>> Accept-Ranges: {bytes|none}
>> Allows the server to indicate it's acceptance of range requests for a
>> resource. Probably
>> not something we want to support at this time, so Cocoon should set
>> this header to none
>> all the time.
>>
>> Age: {seconds}
>> Allows the server to convey the number of seconds since the response
>> (or revalidation)
>> was generated by the origin server. This is used for cache-generated
>> responses. In
>> essence, the Caching mechanism must set this header.
>>
>> ETag: {xyzzy|W/xyzzy|}
>> This has to do with Entity Tags, which I don't fully understand. If a
>> developer understands
>> it and can use it, then they can implement it.
>>
>> Location: {absoluteURI}
>> This is the redirect header--handled by the Redirector in Cocoon.
>>
>> Proxy-Authenticate: {challenge}
>> this is used in conjunction with a 407 Proxy Authentication Required
>> response.
>>
>> Retry-After: {HTTP date|seconds}
>> This is used in conjunction with a 503 service unavailable response.
>> We can use this when
>> we are compiling the initial sitemap and we receive requests.
>>
>> Server: {product|comment}
>> This is usually used by the official web server, and it might be
>> augmented to advertise
>> Cocoon....
>>
>> Vary: {*|field-name}
>> The server should include this header with any cacheable responce that
>> is subject to
>> server driven negotiation. Basically, it tells the client that the
>> resource will only
>> vary on the list of field names in a POST message.
>>
>> WWW-Authenticate: {challenge}
>> This MUST be included with the 401 Unauthorized message--usually taken
>> care of by the
>> servlet container.
>>
>>
>> Beyond this, we have the Entity Header fields. These are used for
>> BOTH requests and response
>> messages. These are:
>>
>> Allow
>> Content-Encoding
>> Content-Language
>> Content-Length
>> Content-Location
>> Content-MD5
>> Content-Range
>> Content-Type
>> Expires
>> Last-Modified
>>
>> Again, the quick definitions of these headers are:
>>
>> Allow: {GET|HEAD|PUT|http method type}
>> Used to specify the types of methods allowable for a resource. Must
>> be present with
>> the 405 Method Not Allowed response. This is useful for forcing POST
>> instead of GET
>> methods for forms, etc. Again, not something Cocoon needs to do out
>> of the gate.
>>
>> Content-Encoding: {content coding}
>> Used when additional encoding has been performed (like gzip) on the
>> resource. After
>> applying the proper decoding, the resource is the same as identified
>> by the Content-Type
>> message.
>>
>> Content-Language: {2 char language code}
>> Used to specify if the resource is specific to a locale. If this is
>> omitted, the content
>> is intended for all languages. This can be a comma separated list.
>> Remember, this can
>> be both request/response. We can use this clue if we want to do
>> internationalization
>> based on the HTTP header.
>>
>> Content-MD5: {base64 encoding of 128 bit MD5 digest}
>> If the content is static, this could be useful to ensure the received
>> document is valid
>> and has not been corrupted in transit.
>>
>> Content-Range: {byte unit}
>> {first-byte-pos}-{last-byte-pos}/{instance-length|*}
>> Used for only downloading a range of bytes (useful for reducing
>> traffic on the net).
>>
>> Content-Type: {mime-type}
>> We all know this one. Cocoon SHOULD set this _allways_.
>>
>> Expires: {http date}
>> Specifies when a resource expires (absolute date). Used to help proxy
>> and client cache
>> implementations. For resources that do not cache, it should be set to
>> the same value as
>> the Date header.
>>
>> Last-Modified: {http date}
>> Specifies the absolute date/time when the resource was last changed.
>> Used to help proxy
>> and client cache implementaitons. This should be set by the Cache
>> mechanism.
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
> .
>
--
"Those who would trade liberty for
temporary security deserve neither"
- Benjamin Franklin
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: let us get serious about 2.0 Final Release
Posted by Bernhard Huber <be...@a1.net>.
Okay, nice list of headers to set.
Who sets what?
What is already answered by you.
Who:
1) ServletEngine
2) Cocoon
2.1) CocoonReader
2.2) CocoonSerializer
2.3) CocoonGenerators
I think that the ServletEngine won't set any headers, will reread the
servlet-spec...
I have not dived into Cocoon to understand 100% contracts for
serializer, and generators, and
if they are allowed to set the http-headers.
But probably it's not the task of the serializer to set the http-headers.
Thus the http-headers should be set be Cocoon-Servlet after the request
is handled.
Is this right?
I will take a look at Cocoon-1 implementation.
Berin Loritsch wrote:
> Bernhard Huber wrote:
>
>> Perhaps setting always a LastModifiedHeader will help too.
>
>
> This is one thing that Cocoon may want to include no matter what.
> Here are the list of
> valid HTTP 1.1 Headers for responses:
>
> Accept-Ranges
> Age
> ETag
> Location
> Proxy-Authenticate
> Retry-After
> Server
> Vary
> WWW-Authenticate
>
> Brief overview for those who don't know:
>
> Accept-Ranges: {bytes|none}
> Allows the server to indicate it's acceptance of range requests for a
> resource. Probably
> not something we want to support at this time, so Cocoon should set
> this header to none
> all the time.
>
> Age: {seconds}
> Allows the server to convey the number of seconds since the response
> (or revalidation)
> was generated by the origin server. This is used for cache-generated
> responses. In
> essence, the Caching mechanism must set this header.
>
> ETag: {xyzzy|W/xyzzy|}
> This has to do with Entity Tags, which I don't fully understand. If a
> developer understands
> it and can use it, then they can implement it.
>
> Location: {absoluteURI}
> This is the redirect header--handled by the Redirector in Cocoon.
>
> Proxy-Authenticate: {challenge}
> this is used in conjunction with a 407 Proxy Authentication Required
> response.
>
> Retry-After: {HTTP date|seconds}
> This is used in conjunction with a 503 service unavailable response.
> We can use this when
> we are compiling the initial sitemap and we receive requests.
>
> Server: {product|comment}
> This is usually used by the official web server, and it might be
> augmented to advertise
> Cocoon....
>
> Vary: {*|field-name}
> The server should include this header with any cacheable responce that
> is subject to
> server driven negotiation. Basically, it tells the client that the
> resource will only
> vary on the list of field names in a POST message.
>
> WWW-Authenticate: {challenge}
> This MUST be included with the 401 Unauthorized message--usually taken
> care of by the
> servlet container.
>
>
> Beyond this, we have the Entity Header fields. These are used for
> BOTH requests and response
> messages. These are:
>
> Allow
> Content-Encoding
> Content-Language
> Content-Length
> Content-Location
> Content-MD5
> Content-Range
> Content-Type
> Expires
> Last-Modified
>
> Again, the quick definitions of these headers are:
>
> Allow: {GET|HEAD|PUT|http method type}
> Used to specify the types of methods allowable for a resource. Must
> be present with
> the 405 Method Not Allowed response. This is useful for forcing POST
> instead of GET
> methods for forms, etc. Again, not something Cocoon needs to do out
> of the gate.
>
> Content-Encoding: {content coding}
> Used when additional encoding has been performed (like gzip) on the
> resource. After
> applying the proper decoding, the resource is the same as identified
> by the Content-Type
> message.
>
> Content-Language: {2 char language code}
> Used to specify if the resource is specific to a locale. If this is
> omitted, the content
> is intended for all languages. This can be a comma separated list.
> Remember, this can
> be both request/response. We can use this clue if we want to do
> internationalization
> based on the HTTP header.
>
> Content-MD5: {base64 encoding of 128 bit MD5 digest}
> If the content is static, this could be useful to ensure the received
> document is valid
> and has not been corrupted in transit.
>
> Content-Range: {byte unit}
> {first-byte-pos}-{last-byte-pos}/{instance-length|*}
> Used for only downloading a range of bytes (useful for reducing
> traffic on the net).
>
> Content-Type: {mime-type}
> We all know this one. Cocoon SHOULD set this _allways_.
>
> Expires: {http date}
> Specifies when a resource expires (absolute date). Used to help proxy
> and client cache
> implementations. For resources that do not cache, it should be set to
> the same value as
> the Date header.
>
> Last-Modified: {http date}
> Specifies the absolute date/time when the resource was last changed.
> Used to help proxy
> and client cache implementaitons. This should be set by the Cache
> mechanism.
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: let us get serious about 2.0 Final Release
Posted by Berin Loritsch <bl...@apache.org>.
Bernhard Huber wrote:
> Perhaps setting always a LastModifiedHeader will help too.
This is one thing that Cocoon may want to include no matter what. Here are the list of
valid HTTP 1.1 Headers for responses:
Accept-Ranges
Age
ETag
Location
Proxy-Authenticate
Retry-After
Server
Vary
WWW-Authenticate
Brief overview for those who don't know:
Accept-Ranges: {bytes|none}
Allows the server to indicate it's acceptance of range requests for a resource. Probably
not something we want to support at this time, so Cocoon should set this header to none
all the time.
Age: {seconds}
Allows the server to convey the number of seconds since the response (or revalidation)
was generated by the origin server. This is used for cache-generated responses. In
essence, the Caching mechanism must set this header.
ETag: {xyzzy|W/xyzzy|}
This has to do with Entity Tags, which I don't fully understand. If a developer understands
it and can use it, then they can implement it.
Location: {absoluteURI}
This is the redirect header--handled by the Redirector in Cocoon.
Proxy-Authenticate: {challenge}
this is used in conjunction with a 407 Proxy Authentication Required response.
Retry-After: {HTTP date|seconds}
This is used in conjunction with a 503 service unavailable response. We can use this when
we are compiling the initial sitemap and we receive requests.
Server: {product|comment}
This is usually used by the official web server, and it might be augmented to advertise
Cocoon....
Vary: {*|field-name}
The server should include this header with any cacheable responce that is subject to
server driven negotiation. Basically, it tells the client that the resource will only
vary on the list of field names in a POST message.
WWW-Authenticate: {challenge}
This MUST be included with the 401 Unauthorized message--usually taken care of by the
servlet container.
Beyond this, we have the Entity Header fields. These are used for BOTH requests and response
messages. These are:
Allow
Content-Encoding
Content-Language
Content-Length
Content-Location
Content-MD5
Content-Range
Content-Type
Expires
Last-Modified
Again, the quick definitions of these headers are:
Allow: {GET|HEAD|PUT|http method type}
Used to specify the types of methods allowable for a resource. Must be present with
the 405 Method Not Allowed response. This is useful for forcing POST instead of GET
methods for forms, etc. Again, not something Cocoon needs to do out of the gate.
Content-Encoding: {content coding}
Used when additional encoding has been performed (like gzip) on the resource. After
applying the proper decoding, the resource is the same as identified by the Content-Type
message.
Content-Language: {2 char language code}
Used to specify if the resource is specific to a locale. If this is omitted, the content
is intended for all languages. This can be a comma separated list. Remember, this can
be both request/response. We can use this clue if we want to do internationalization
based on the HTTP header.
Content-MD5: {base64 encoding of 128 bit MD5 digest}
If the content is static, this could be useful to ensure the received document is valid
and has not been corrupted in transit.
Content-Range: {byte unit} {first-byte-pos}-{last-byte-pos}/{instance-length|*}
Used for only downloading a range of bytes (useful for reducing traffic on the net).
Content-Type: {mime-type}
We all know this one. Cocoon SHOULD set this _allways_.
Expires: {http date}
Specifies when a resource expires (absolute date). Used to help proxy and client cache
implementations. For resources that do not cache, it should be set to the same value as
the Date header.
Last-Modified: {http date}
Specifies the absolute date/time when the resource was last changed. Used to help proxy
and client cache implementaitons. This should be set by the Cache mechanism.
--
"Those who would trade liberty for
temporary security deserve neither"
- Benjamin Franklin
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: let us get serious about 2.0 Final Release
Posted by Bernhard Huber <be...@a1.net>.
hi,
i enhanced the view.xml describing the new features,
i hope it is correct, and helpful for using views.
(the sitemap.xsl is pretty nice, and complicated.)
bye bernhard
>>
>>About documentation in general, I would like to write something about
>>the new
>>views, and about the sitemap elements map:aggregate, map:part, etc as
>>I have noticed that they are not described.
>>
>
>Cool, thanks.
>
>>I will just post the plain text, or should I write it directly in the xml?
>>
>
>Directly using the DTDs in the repo.
>
Re: let us get serious about 2.0 Final Release
Posted by giacomo <gi...@apache.org>.
On Tue, 20 Nov 2001, Bernhard Huber wrote:
> Hi
>
> About documentation in general, I would like to write something about
> the new
> views, and about the sitemap elements map:aggregate, map:part, etc as
> I have noticed that they are not described.
Cool, thanks.
> I will just post the plain text, or should I write it directly in the xml?
Directly using the DTDs in the repo.
> My english is not perfect so you surely have to review.....
Happens to many here as well.
Giacomo
>
> >** Documentation, documentation, documentation
> >- stop apologising for Cocoon 1
> >- positive announcement.xml and index.xml
> >- both of those docs need a concise overiew at top
> >(something less than half-a-page that convinces boss)
> >- much of the documentation is old and still talks about
> >Cocoon 1 configuration methods and issues
> >- much documentation still has "Under construction" notices
> >- people will turn away in droves
> >
> >** cocoon.xconf needs all parameters and components
> >listed and briefly explained as internal documentation
> >
> >
> >
> >** The excellent document "How to Develop Web Applications"
> >and the accompanying webapp.tutorial are missing from
> >the cocoon_20_branch
> >
> >** Better stylesheet for xml.apache.org/cocoon2/
> >- the slow response of the website will not allow 2.0 to
> >make its impact.
> >
> I think the problem of the slow response is that neither html-pages, nor
> the images
> has a LastModified, or Expires http-header. Setting the headers for the
> images
> could be accomplished by modifiying the ResourceReader class.
> Trying to speedup without modifying an source you might want to change
> the sitemap of
> documentation setting an expires parameter:
> For example setting an expires parameter values makes the resource to
> 720000 will make the
> resource valid for 1 hour, thus speeding up the loading of documentation
> pages the next 1 hour,
> I think this would help as a first step to speed up the documentation pages:
> The sitemap setting example: <map:match pattern="**images/*.jpg">
> <map:read src="images/{2}.jpg" mime-type="image/jpeg">
> <map:parameter name="expires" value="720000"/>
> </map:read>
> </map:match>
>
> <map:match pattern="**images/*.gif">
> <map:read src="images/{2}.gif" mime-type="image/gif">
> <map:parameter name="expires" value="720000"/>
> </map:read>
> </map:match>
>
> The ResourceReader documentation states:
>
> * The <code>ResourceReader</code> component is used to serve binary data
> * in a sitemap pipeline. It makes use of HTTP Headers to determine if
> * the requested resource should be written to the <code>OutputStream</code>
> * or if it can signal that it hasn't changed.
> *
> * Parameters:
> * <dl>
> * <dt><expires></dt>
> * <dd>This parameter is optional. When specified it determines
> how long
> * in miliseconds the resources can be cached by any proxy or
> browser
> * between Cocoon2 and the requesting visitor.
> * </dd>
> * </dl>
>
> Perhaps setting always a LastModifiedHeader will help too.
>
> >
> >
> >Also the following issues are summarised at
> >documentation/xdocs/plan/release.xml ...
> >
> >** We have many open bugs in bugzilla
> >** Layout the distribution
> >** Ensure that licensing requirements have been met
> >** Decide what to backport from the 2.1 head
> >
> >--David
> >
> >>>--------------------------
> >>>
> >>>>Subject: [C2.0] Should we set a date for 2.0 Final Release?
> >>>>Date: Thu, 18 Oct 2001 14:55:15 +0200
> >>>>From: Martin Man <Ma...@seznam.cz>
> >>>>To: cocoon-dev@xml.apache.org
> >>>>
> >>>>Carsten Ziegeler wrote:
> >>>>
> >>>>>Ok, yes, I didnt check the calendar. Thanks for the hint!
> >>>>>
> >>>>>As I still prefer mondays, we should set the dates to
> >>>>>5th November: RC2
> >>>>>26th November: Final Release
> >>>>>
> >>>>yep, my +1 also for both dates, BTW: without looking to the
> >>>>repository, do we have actualized TODO list... I mean critical
> >>>>isuues (not including documentation) to fix ???
> >>>>
> >>>--------------------------
> >>>
> >>>>Date: Thu, 18 Oct 2001 14:37:57 +0200
> >>>>From: "Carsten Ziegeler" <cz...@sundn.de>
> >>>>To: <co...@xml.apache.org>, <di...@yahoo.com>
> >>>>
> >>>>you're absolutely right. It's the same problem here.
> >>>>Due to the many changes I would propose a RC2.
> >>>>But we still need more documentation! So a good
> >>>>date could be 1st of November for the RC2 and
> >>>>end of november for the final release.
> >>>>
> >>>>But whatever date we decide on for the final
> >>>>release, we *should* stick to it.
> >>>>
> >>>>Carsten
> >>>>Open Source Group sunShine - b:Integrated
> >>>>================================================================
> >>>>Carsten Ziegeler, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
> >>>>www.sundn.de mailto: cziegeler@sundn.de
> >>>>================================================================
> >>>>
> >>>>Dims wrote:
> >>>>
> >>>>>Team,
> >>>>>Should we set a date for 2.0 Final Release? (or the next Release
> >>>>>Candidate)? Am a bit tired of
> >>>>>hearing from people (in my organization) that we cannot switch
> >>>>>from C1.X to C2.0 since it is in
> >>>>>Beta/RC Cycle....
> >>>>>
> >>>>>Thanks,
> >>>>>dims
> >>>>>=====
> >>>>>Davanum Srinivas - http://jguru.com/dims/
> >>>>>
> >>>
> >>>---------------------------------------------------------------------
> >>>To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> >>>For additional commands, email: cocoon-dev-help@xml.apache.org
> >>>
> >>>
> >>>
> >>
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> >For additional commands, email: cocoon-dev-help@xml.apache.org
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: let us get serious about 2.0 Final Release
Posted by Bernhard Huber <be...@a1.net>.
Hi
About documentation in general, I would like to write something about
the new
views, and about the sitemap elements map:aggregate, map:part, etc as
I have noticed that they are not described.
I will just post the plain text, or should I write it directly in the xml?
My english is not perfect so you surely have to review.....
>** Documentation, documentation, documentation
>- stop apologising for Cocoon 1
>- positive announcement.xml and index.xml
>- both of those docs need a concise overiew at top
>(something less than half-a-page that convinces boss)
>- much of the documentation is old and still talks about
>Cocoon 1 configuration methods and issues
>- much documentation still has "Under construction" notices
>- people will turn away in droves
>
>** cocoon.xconf needs all parameters and components
>listed and briefly explained as internal documentation
>
>
>
>** The excellent document "How to Develop Web Applications"
>and the accompanying webapp.tutorial are missing from
>the cocoon_20_branch
>
>** Better stylesheet for xml.apache.org/cocoon2/
>- the slow response of the website will not allow 2.0 to
>make its impact.
>
I think the problem of the slow response is that neither html-pages, nor
the images
has a LastModified, or Expires http-header. Setting the headers for the
images
could be accomplished by modifiying the ResourceReader class.
Trying to speedup without modifying an source you might want to change
the sitemap of
documentation setting an expires parameter:
For example setting an expires parameter values makes the resource to
720000 will make the
resource valid for 1 hour, thus speeding up the loading of documentation
pages the next 1 hour,
I think this would help as a first step to speed up the documentation pages:
The sitemap setting example: <map:match pattern="**images/*.jpg">
<map:read src="images/{2}.jpg" mime-type="image/jpeg">
<map:parameter name="expires" value="720000"/>
</map:read>
</map:match>
<map:match pattern="**images/*.gif">
<map:read src="images/{2}.gif" mime-type="image/gif">
<map:parameter name="expires" value="720000"/>
</map:read>
</map:match>
The ResourceReader documentation states:
* The <code>ResourceReader</code> component is used to serve binary data
* in a sitemap pipeline. It makes use of HTTP Headers to determine if
* the requested resource should be written to the <code>OutputStream</code>
* or if it can signal that it hasn't changed.
*
* Parameters:
* <dl>
* <dt><expires></dt>
* <dd>This parameter is optional. When specified it determines
how long
* in miliseconds the resources can be cached by any proxy or
browser
* between Cocoon2 and the requesting visitor.
* </dd>
* </dl>
Perhaps setting always a LastModifiedHeader will help too.
>
>
>Also the following issues are summarised at
>documentation/xdocs/plan/release.xml ...
>
>** We have many open bugs in bugzilla
>** Layout the distribution
>** Ensure that licensing requirements have been met
>** Decide what to backport from the 2.1 head
>
>--David
>
>>>--------------------------
>>>
>>>>Subject: [C2.0] Should we set a date for 2.0 Final Release?
>>>>Date: Thu, 18 Oct 2001 14:55:15 +0200
>>>>From: Martin Man <Ma...@seznam.cz>
>>>>To: cocoon-dev@xml.apache.org
>>>>
>>>>Carsten Ziegeler wrote:
>>>>
>>>>>Ok, yes, I didnt check the calendar. Thanks for the hint!
>>>>>
>>>>>As I still prefer mondays, we should set the dates to
>>>>>5th November: RC2
>>>>>26th November: Final Release
>>>>>
>>>>yep, my +1 also for both dates, BTW: without looking to the
>>>>repository, do we have actualized TODO list... I mean critical
>>>>isuues (not including documentation) to fix ???
>>>>
>>>--------------------------
>>>
>>>>Date: Thu, 18 Oct 2001 14:37:57 +0200
>>>>From: "Carsten Ziegeler" <cz...@sundn.de>
>>>>To: <co...@xml.apache.org>, <di...@yahoo.com>
>>>>
>>>>you're absolutely right. It's the same problem here.
>>>>Due to the many changes I would propose a RC2.
>>>>But we still need more documentation! So a good
>>>>date could be 1st of November for the RC2 and
>>>>end of november for the final release.
>>>>
>>>>But whatever date we decide on for the final
>>>>release, we *should* stick to it.
>>>>
>>>>Carsten
>>>>Open Source Group sunShine - b:Integrated
>>>>================================================================
>>>>Carsten Ziegeler, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
>>>>www.sundn.de mailto: cziegeler@sundn.de
>>>>================================================================
>>>>
>>>>Dims wrote:
>>>>
>>>>>Team,
>>>>>Should we set a date for 2.0 Final Release? (or the next Release
>>>>>Candidate)? Am a bit tired of
>>>>>hearing from people (in my organization) that we cannot switch
>>>>>from C1.X to C2.0 since it is in
>>>>>Beta/RC Cycle....
>>>>>
>>>>>Thanks,
>>>>>dims
>>>>>=====
>>>>>Davanum Srinivas - http://jguru.com/dims/
>>>>>
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
>>>For additional commands, email: cocoon-dev-help@xml.apache.org
>>>
>>>
>>>
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
>For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: let us get serious about 2.0 Final Release
Posted by Michael McKibben <mm...@ncube.com>.
Thank you Bernhard for working on the Velocity documentation. I've been
meaning to send Carsten the patch this week like I promised, but you beat
me to it!
Regards,
--mike
On Wed, 21 Nov 2001, Bernhard Huber wrote:
> Hi,
> some documentation about cinclude, and xinclude as it is frequentyl
> requested.
> and i copied from javadoc docu about velocity generator.
> docs are zipped up and attached
> bye bernhard
>
> David Crossley wrote:
>
> >Giacomo Pati wrote:
> >
> >>Quoting David Crossley <cr...@indexgeo.com.au>:
> >>
> >>>There are SIX DAYS TO GO until the agreed date for the
> >>>final release. We also agreed that the date should not slip.
> >>>
> >>>In my opinion, 2.0 is not yet fit for release. So there is only
> >>>one option ... hold the RT threads and get on with the job.
> >>>--David
> >>>
> >>What is it you think needs to be fixed before releaseing it?
> >>Giacomo
> >>
> >
> >** Documentation, documentation, documentation
> >- stop apologising for Cocoon 1
> >- positive announcement.xml and index.xml
> >- both of those docs need a concise overiew at top
> >(something less than half-a-page that convinces boss)
> >- much of the documentation is old and still talks about
> >Cocoon 1 configuration methods and issues
> >- much documentation still has "Under construction" notices
> >- people will turn away in droves
> >
> >** cocoon.xconf needs all parameters and components
> >listed and briefly explained as internal documentation
> >
> >** The excellent document "How to Develop Web Applications"
> >and the accompanying webapp.tutorial are missing from
> >the cocoon_20_branch
> >
> >** Better stylesheet for xml.apache.org/cocoon2/
> >- the slow response of the website will not allow 2.0 to
> >make its impact.
> >
> >Also the following issues are summarised at
> >documentation/xdocs/plan/release.xml ...
> >
> >** We have many open bugs in bugzilla
> >** Layout the distribution
> >** Ensure that licensing requirements have been met
> >** Decide what to backport from the 2.1 head
> >
> >--David
> >
> >>>--------------------------
> >>>
> >>>>Subject: [C2.0] Should we set a date for 2.0 Final Release?
> >>>>Date: Thu, 18 Oct 2001 14:55:15 +0200
> >>>>From: Martin Man <Ma...@seznam.cz>
> >>>>To: cocoon-dev@xml.apache.org
> >>>>
> >>>>Carsten Ziegeler wrote:
> >>>>
> >>>>>Ok, yes, I didnt check the calendar. Thanks for the hint!
> >>>>>
> >>>>>As I still prefer mondays, we should set the dates to
> >>>>>5th November: RC2
> >>>>>26th November: Final Release
> >>>>>
> >>>>yep, my +1 also for both dates, BTW: without looking to the
> >>>>repository, do we have actualized TODO list... I mean critical
> >>>>isuues (not including documentation) to fix ???
> >>>>
> >>>--------------------------
> >>>
> >>>>Date: Thu, 18 Oct 2001 14:37:57 +0200
> >>>>From: "Carsten Ziegeler" <cz...@sundn.de>
> >>>>To: <co...@xml.apache.org>, <di...@yahoo.com>
> >>>>
> >>>>you're absolutely right. It's the same problem here.
> >>>>Due to the many changes I would propose a RC2.
> >>>>But we still need more documentation! So a good
> >>>>date could be 1st of November for the RC2 and
> >>>>end of november for the final release.
> >>>>
> >>>>But whatever date we decide on for the final
> >>>>release, we *should* stick to it.
> >>>>
> >>>>Carsten
> >>>>Open Source Group sunShine - b:Integrated
> >>>>================================================================
> >>>>Carsten Ziegeler, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
> >>>>www.sundn.de mailto: cziegeler@sundn.de
> >>>>================================================================
> >>>>
> >>>>Dims wrote:
> >>>>
> >>>>>Team,
> >>>>>Should we set a date for 2.0 Final Release? (or the next Release
> >>>>>Candidate)? Am a bit tired of
> >>>>>hearing from people (in my organization) that we cannot switch
> >>>>>from C1.X to C2.0 since it is in
> >>>>>Beta/RC Cycle....
> >>>>>
> >>>>>Thanks,
> >>>>>dims
> >>>>>=====
> >>>>>Davanum Srinivas - http://jguru.com/dims/
> >>>>>
> >>>
> >>>---------------------------------------------------------------------
> >>>To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> >>>For additional commands, email: cocoon-dev-help@xml.apache.org
> >>>
> >>>
> >>>
> >>
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> >For additional commands, email: cocoon-dev-help@xml.apache.org
> >
> >
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: let us get serious about 2.0 Final Release
Posted by Bernhard Huber <be...@a1.net>.
Hi,
some documentation about cinclude, and xinclude as it is frequentyl
requested.
and i copied from javadoc docu about velocity generator.
docs are zipped up and attached
bye bernhard
David Crossley wrote:
>Giacomo Pati wrote:
>
>>Quoting David Crossley <cr...@indexgeo.com.au>:
>>
>>>There are SIX DAYS TO GO until the agreed date for the
>>>final release. We also agreed that the date should not slip.
>>>
>>>In my opinion, 2.0 is not yet fit for release. So there is only
>>>one option ... hold the RT threads and get on with the job.
>>>--David
>>>
>>What is it you think needs to be fixed before releaseing it?
>>Giacomo
>>
>
>** Documentation, documentation, documentation
>- stop apologising for Cocoon 1
>- positive announcement.xml and index.xml
>- both of those docs need a concise overiew at top
>(something less than half-a-page that convinces boss)
>- much of the documentation is old and still talks about
>Cocoon 1 configuration methods and issues
>- much documentation still has "Under construction" notices
>- people will turn away in droves
>
>** cocoon.xconf needs all parameters and components
>listed and briefly explained as internal documentation
>
>** The excellent document "How to Develop Web Applications"
>and the accompanying webapp.tutorial are missing from
>the cocoon_20_branch
>
>** Better stylesheet for xml.apache.org/cocoon2/
>- the slow response of the website will not allow 2.0 to
>make its impact.
>
>Also the following issues are summarised at
>documentation/xdocs/plan/release.xml ...
>
>** We have many open bugs in bugzilla
>** Layout the distribution
>** Ensure that licensing requirements have been met
>** Decide what to backport from the 2.1 head
>
>--David
>
>>>--------------------------
>>>
>>>>Subject: [C2.0] Should we set a date for 2.0 Final Release?
>>>>Date: Thu, 18 Oct 2001 14:55:15 +0200
>>>>From: Martin Man <Ma...@seznam.cz>
>>>>To: cocoon-dev@xml.apache.org
>>>>
>>>>Carsten Ziegeler wrote:
>>>>
>>>>>Ok, yes, I didnt check the calendar. Thanks for the hint!
>>>>>
>>>>>As I still prefer mondays, we should set the dates to
>>>>>5th November: RC2
>>>>>26th November: Final Release
>>>>>
>>>>yep, my +1 also for both dates, BTW: without looking to the
>>>>repository, do we have actualized TODO list... I mean critical
>>>>isuues (not including documentation) to fix ???
>>>>
>>>--------------------------
>>>
>>>>Date: Thu, 18 Oct 2001 14:37:57 +0200
>>>>From: "Carsten Ziegeler" <cz...@sundn.de>
>>>>To: <co...@xml.apache.org>, <di...@yahoo.com>
>>>>
>>>>you're absolutely right. It's the same problem here.
>>>>Due to the many changes I would propose a RC2.
>>>>But we still need more documentation! So a good
>>>>date could be 1st of November for the RC2 and
>>>>end of november for the final release.
>>>>
>>>>But whatever date we decide on for the final
>>>>release, we *should* stick to it.
>>>>
>>>>Carsten
>>>>Open Source Group sunShine - b:Integrated
>>>>================================================================
>>>>Carsten Ziegeler, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
>>>>www.sundn.de mailto: cziegeler@sundn.de
>>>>================================================================
>>>>
>>>>Dims wrote:
>>>>
>>>>>Team,
>>>>>Should we set a date for 2.0 Final Release? (or the next Release
>>>>>Candidate)? Am a bit tired of
>>>>>hearing from people (in my organization) that we cannot switch
>>>>>from C1.X to C2.0 since it is in
>>>>>Beta/RC Cycle....
>>>>>
>>>>>Thanks,
>>>>>dims
>>>>>=====
>>>>>Davanum Srinivas - http://jguru.com/dims/
>>>>>
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
>>>For additional commands, email: cocoon-dev-help@xml.apache.org
>>>
>>>
>>>
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
>For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
Re: let us get serious about 2.0 Final Release
Posted by giacomo <gi...@apache.org>.
On Wed, 21 Nov 2001, David Crossley wrote:
> Giacomo Pati wrote:
> > Quoting David Crossley <cr...@indexgeo.com.au>:
> >
> > > There are SIX DAYS TO GO until the agreed date for the
> > > final release. We also agreed that the date should not slip.
> > >
> > > In my opinion, 2.0 is not yet fit for release. So there is only
> > > one option ... hold the RT threads and get on with the job.
> > > --David
> >
> > What is it you think needs to be fixed before releaseing it?
> > Giacomo
>
> ** Documentation, documentation, documentation
> - stop apologising for Cocoon 1
+1
> - positive announcement.xml and index.xml
+1 I've fixed part of index.xml already
> - both of those docs need a concise overiew at top
> (something less than half-a-page that convinces boss)
ok
> - much of the documentation is old and still talks about
> Cocoon 1 configuration methods and issues
> - much documentation still has "Under construction" notices
> - people will turn away in droves
>
> ** cocoon.xconf needs all parameters and components
> listed and briefly explained as internal documentation
I always wished we had a markup for these thing to tear them out for
docs (as with xspdocs for logicsheets).
> ** The excellent document "How to Develop Web Applications"
> and the accompanying webapp.tutorial are missing from
> the cocoon_20_branch
>
> ** Better stylesheet for xml.apache.org/cocoon2/
> - the slow response of the website will not allow 2.0 to
> make its impact.
This will change in the future but it is not only our responsability to
change it as all XML projects have to be convinced.
> Also the following issues are summarised at
> documentation/xdocs/plan/release.xml ...
>
> ** We have many open bugs in bugzilla
> ** Layout the distribution
> ** Ensure that licensing requirements have been met
> ** Decide what to backport from the 2.1 head
I don't see what we should backport into 2.0.
Giacomo
>
> --David
>
> > > --------------------------
> > > > Subject: [C2.0] Should we set a date for 2.0 Final Release?
> > > > Date: Thu, 18 Oct 2001 14:55:15 +0200
> > > > From: Martin Man <Ma...@seznam.cz>
> > > > To: cocoon-dev@xml.apache.org
> > > >
> > > > Carsten Ziegeler wrote:
> > > > > Ok, yes, I didnt check the calendar. Thanks for the hint!
> > > > >
> > > > > As I still prefer mondays, we should set the dates to
> > > > > 5th November: RC2
> > > > > 26th November: Final Release
> > > >
> > > > yep, my +1 also for both dates, BTW: without looking to the
> > > > repository, do we have actualized TODO list... I mean critical
> > > > isuues (not including documentation) to fix ???
> > >
> > > --------------------------
> > > > Date: Thu, 18 Oct 2001 14:37:57 +0200
> > > > From: "Carsten Ziegeler" <cz...@sundn.de>
> > > > To: <co...@xml.apache.org>, <di...@yahoo.com>
> > > >
> > > > you're absolutely right. It's the same problem here.
> > > > Due to the many changes I would propose a RC2.
> > > > But we still need more documentation! So a good
> > > > date could be 1st of November for the RC2 and
> > > > end of november for the final release.
> > > >
> > > > But whatever date we decide on for the final
> > > > release, we *should* stick to it.
> > > >
> > > > Carsten
> > > > Open Source Group sunShine - b:Integrated
> > > > ================================================================
> > > > Carsten Ziegeler, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
> > > > www.sundn.de mailto: cziegeler@sundn.de
> > > > ================================================================
> > > >
> > > > Dims wrote:
> > > > > Team,
> > > > > Should we set a date for 2.0 Final Release? (or the next Release
> > > > > Candidate)? Am a bit tired of
> > > > > hearing from people (in my organization) that we cannot switch
> > > > > from C1.X to C2.0 since it is in
> > > > > Beta/RC Cycle....
> > > > >
> > > > > Thanks,
> > > > > dims
> > > > > =====
> > > > > Davanum Srinivas - http://jguru.com/dims/
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> > > For additional commands, email: cocoon-dev-help@xml.apache.org
> > >
> > >
> > >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: let us get serious about 2.0 Final Release
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
David Crossley wrote:
>
> Giacomo Pati wrote:
> > Quoting David Crossley <cr...@indexgeo.com.au>:
> >
> > > There are SIX DAYS TO GO until the agreed date for the
> > > final release. We also agreed that the date should not slip.
> > >
> > > In my opinion, 2.0 is not yet fit for release. So there is only
> > > one option ... hold the RT threads and get on with the job.
> > > --David
> >
> > What is it you think needs to be fixed before releaseing it?
We should also wait for the final release of Xalan 2 - which is
expected in the first days of december.
Carsten
> > Giacomo
>
> ** Documentation, documentation, documentation
> - stop apologising for Cocoon 1
> - positive announcement.xml and index.xml
> - both of those docs need a concise overiew at top
> (something less than half-a-page that convinces boss)
> - much of the documentation is old and still talks about
> Cocoon 1 configuration methods and issues
> - much documentation still has "Under construction" notices
> - people will turn away in droves
>
> ** cocoon.xconf needs all parameters and components
> listed and briefly explained as internal documentation
>
> ** The excellent document "How to Develop Web Applications"
> and the accompanying webapp.tutorial are missing from
> the cocoon_20_branch
>
> ** Better stylesheet for xml.apache.org/cocoon2/
> - the slow response of the website will not allow 2.0 to
> make its impact.
>
> Also the following issues are summarised at
> documentation/xdocs/plan/release.xml ...
>
> ** We have many open bugs in bugzilla
> ** Layout the distribution
> ** Ensure that licensing requirements have been met
> ** Decide what to backport from the 2.1 head
>
> --David
>
> > > --------------------------
> > > > Subject: [C2.0] Should we set a date for 2.0 Final Release?
> > > > Date: Thu, 18 Oct 2001 14:55:15 +0200
> > > > From: Martin Man <Ma...@seznam.cz>
> > > > To: cocoon-dev@xml.apache.org
> > > >
> > > > Carsten Ziegeler wrote:
> > > > > Ok, yes, I didnt check the calendar. Thanks for the hint!
> > > > >
> > > > > As I still prefer mondays, we should set the dates to
> > > > > 5th November: RC2
> > > > > 26th November: Final Release
> > > >
> > > > yep, my +1 also for both dates, BTW: without looking to the
> > > > repository, do we have actualized TODO list... I mean critical
> > > > isuues (not including documentation) to fix ???
> > >
> > > --------------------------
> > > > Date: Thu, 18 Oct 2001 14:37:57 +0200
> > > > From: "Carsten Ziegeler" <cz...@sundn.de>
> > > > To: <co...@xml.apache.org>, <di...@yahoo.com>
> > > >
> > > > you're absolutely right. It's the same problem here.
> > > > Due to the many changes I would propose a RC2.
> > > > But we still need more documentation! So a good
> > > > date could be 1st of November for the RC2 and
> > > > end of november for the final release.
> > > >
> > > > But whatever date we decide on for the final
> > > > release, we *should* stick to it.
> > > >
> > > > Carsten
> > > > Open Source Group sunShine - b:Integrated
> > > > ================================================================
> > > > Carsten Ziegeler, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
> > > > www.sundn.de mailto: cziegeler@sundn.de
> > > > ================================================================
> > > >
> > > > Dims wrote:
> > > > > Team,
> > > > > Should we set a date for 2.0 Final Release? (or the next Release
> > > > > Candidate)? Am a bit tired of
> > > > > hearing from people (in my organization) that we cannot switch
> > > > > from C1.X to C2.0 since it is in
> > > > > Beta/RC Cycle....
> > > > >
> > > > > Thanks,
> > > > > dims
> > > > > =====
> > > > > Davanum Srinivas - http://jguru.com/dims/
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> > > For additional commands, email: cocoon-dev-help@xml.apache.org
> > >
> > >
> > >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: let us get serious about 2.0 Final Release
Posted by David Crossley <cr...@indexgeo.com.au>.
Giacomo Pati wrote:
> Quoting David Crossley <cr...@indexgeo.com.au>:
>
> > There are SIX DAYS TO GO until the agreed date for the
> > final release. We also agreed that the date should not slip.
> >
> > In my opinion, 2.0 is not yet fit for release. So there is only
> > one option ... hold the RT threads and get on with the job.
> > --David
>
> What is it you think needs to be fixed before releaseing it?
> Giacomo
** Documentation, documentation, documentation
- stop apologising for Cocoon 1
- positive announcement.xml and index.xml
- both of those docs need a concise overiew at top
(something less than half-a-page that convinces boss)
- much of the documentation is old and still talks about
Cocoon 1 configuration methods and issues
- much documentation still has "Under construction" notices
- people will turn away in droves
** cocoon.xconf needs all parameters and components
listed and briefly explained as internal documentation
** The excellent document "How to Develop Web Applications"
and the accompanying webapp.tutorial are missing from
the cocoon_20_branch
** Better stylesheet for xml.apache.org/cocoon2/
- the slow response of the website will not allow 2.0 to
make its impact.
Also the following issues are summarised at
documentation/xdocs/plan/release.xml ...
** We have many open bugs in bugzilla
** Layout the distribution
** Ensure that licensing requirements have been met
** Decide what to backport from the 2.1 head
--David
> > --------------------------
> > > Subject: [C2.0] Should we set a date for 2.0 Final Release?
> > > Date: Thu, 18 Oct 2001 14:55:15 +0200
> > > From: Martin Man <Ma...@seznam.cz>
> > > To: cocoon-dev@xml.apache.org
> > >
> > > Carsten Ziegeler wrote:
> > > > Ok, yes, I didnt check the calendar. Thanks for the hint!
> > > >
> > > > As I still prefer mondays, we should set the dates to
> > > > 5th November: RC2
> > > > 26th November: Final Release
> > >
> > > yep, my +1 also for both dates, BTW: without looking to the
> > > repository, do we have actualized TODO list... I mean critical
> > > isuues (not including documentation) to fix ???
> >
> > --------------------------
> > > Date: Thu, 18 Oct 2001 14:37:57 +0200
> > > From: "Carsten Ziegeler" <cz...@sundn.de>
> > > To: <co...@xml.apache.org>, <di...@yahoo.com>
> > >
> > > you're absolutely right. It's the same problem here.
> > > Due to the many changes I would propose a RC2.
> > > But we still need more documentation! So a good
> > > date could be 1st of November for the RC2 and
> > > end of november for the final release.
> > >
> > > But whatever date we decide on for the final
> > > release, we *should* stick to it.
> > >
> > > Carsten
> > > Open Source Group sunShine - b:Integrated
> > > ================================================================
> > > Carsten Ziegeler, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
> > > www.sundn.de mailto: cziegeler@sundn.de
> > > ================================================================
> > >
> > > Dims wrote:
> > > > Team,
> > > > Should we set a date for 2.0 Final Release? (or the next Release
> > > > Candidate)? Am a bit tired of
> > > > hearing from people (in my organization) that we cannot switch
> > > > from C1.X to C2.0 since it is in
> > > > Beta/RC Cycle....
> > > >
> > > > Thanks,
> > > > dims
> > > > =====
> > > > Davanum Srinivas - http://jguru.com/dims/
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> > For additional commands, email: cocoon-dev-help@xml.apache.org
> >
> >
> >
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: let us get serious about 2.0 Final Release
Posted by Giacomo Pati <gi...@apache.org>.
Quoting David Crossley <cr...@indexgeo.com.au>:
> There are SIX DAYS TO GO until the agreed date for the
> final release. We also agreed that the date should not slip.
>
> In my opinion, 2.0 is not yet fit for release. So there is only
> one option ... hold the RT threads and get on with the job.
What is it you think needs to be fixed before releaseing it?
Giacomo
> --David
>
> --------------------------
> > Subject: [C2.0] Should we set a date for 2.0 Final Release?
> > Date: Thu, 18 Oct 2001 14:55:15 +0200
> > From: Martin Man <Ma...@seznam.cz>
> > To: cocoon-dev@xml.apache.org
> >
> > Carsten Ziegeler wrote:
> > > Ok, yes, I didnt check the calendar. Thanks for the hint!
> > >
> > > As I still prefer mondays, we should set the dates to
> > > 5th November: RC2
> > > 26th November: Final Release
> >
> > yep, my +1 also for both dates, BTW: without looking to the
> > repository, do we have actualized TODO list... I mean critical
> > isuues (not including documentation) to fix ???
>
> --------------------------
> > Date: Thu, 18 Oct 2001 14:37:57 +0200
> > From: "Carsten Ziegeler" <cz...@sundn.de>
> > To: <co...@xml.apache.org>, <di...@yahoo.com>
> >
> > you're absolutely right. It's the same problem here.
> > Due to the many changes I would propose a RC2.
> > But we still need more documentation! So a good
> > date could be 1st of November for the RC2 and
> > end of november for the final release.
> >
> > But whatever date we decide on for the final
> > release, we *should* stick to it.
> >
> > Carsten
> > Open Source Group sunShine - b:Integrated
> > ================================================================
> > Carsten Ziegeler, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
> > www.sundn.de mailto: cziegeler@sundn.de
> > ================================================================
> >
> > Dims wrote:
> > > Team,
> > > Should we set a date for 2.0 Final Release? (or the next Release
> > > Candidate)? Am a bit tired of
> > > hearing from people (in my organization) that we cannot switch
> > > from C1.X to C2.0 since it is in
> > > Beta/RC Cycle....
> > >
> > > Thanks,
> > > dims
> > > =====
> > > Davanum Srinivas - http://jguru.com/dims/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
let us get serious about 2.0 Final Release
Posted by David Crossley <cr...@indexgeo.com.au>.
There are SIX DAYS TO GO until the agreed date for the
final release. We also agreed that the date should not slip.
In my opinion, 2.0 is not yet fit for release. So there is only
one option ... hold the RT threads and get on with the job.
--David
--------------------------
> Subject: [C2.0] Should we set a date for 2.0 Final Release?
> Date: Thu, 18 Oct 2001 14:55:15 +0200
> From: Martin Man <Ma...@seznam.cz>
> To: cocoon-dev@xml.apache.org
>
> Carsten Ziegeler wrote:
> > Ok, yes, I didnt check the calendar. Thanks for the hint!
> >
> > As I still prefer mondays, we should set the dates to
> > 5th November: RC2
> > 26th November: Final Release
>
> yep, my +1 also for both dates, BTW: without looking to the
> repository, do we have actualized TODO list... I mean critical
> isuues (not including documentation) to fix ???
--------------------------
> Date: Thu, 18 Oct 2001 14:37:57 +0200
> From: "Carsten Ziegeler" <cz...@sundn.de>
> To: <co...@xml.apache.org>, <di...@yahoo.com>
>
> you're absolutely right. It's the same problem here.
> Due to the many changes I would propose a RC2.
> But we still need more documentation! So a good
> date could be 1st of November for the RC2 and
> end of november for the final release.
>
> But whatever date we decide on for the final
> release, we *should* stick to it.
>
> Carsten
> Open Source Group sunShine - b:Integrated
> ================================================================
> Carsten Ziegeler, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
> www.sundn.de mailto: cziegeler@sundn.de
> ================================================================
>
> Dims wrote:
> > Team,
> > Should we set a date for 2.0 Final Release? (or the next Release
> > Candidate)? Am a bit tired of
> > hearing from people (in my organization) that we cannot switch
> > from C1.X to C2.0 since it is in
> > Beta/RC Cycle....
> >
> > Thanks,
> > dims
> > =====
> > Davanum Srinivas - http://jguru.com/dims/
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: [C2.0] Should we set a date for 2.0 Final Release?
Posted by Carsten Ziegeler <cz...@sundn.de>.
Hi Vadim,
I think both should go to the next version. We should add this
to the todo list of 2.1 containing those links.
Carsten
> -----Original Message-----
> From: Vadim Gritsenko [mailto:vadim.gritsenko@verizon.net]
> Sent: Thursday, October 18, 2001 7:38 PM
> To: cocoon-dev@xml.apache.org
> Subject: RE: AW: [C2.0] Should we set a date for 2.0 Final Release?
>
>
> Carsten,
>
> What do you think about these issues:
> http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=99780708222079&w=2
> http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=99814216923705&w=2
>
> Should they be fixed before release, or this will go to the next one?
> AFAIK, this is not reflected in bugzilla also...
>
> Vadim
>
> > -----Original Message-----
> > From: Carsten Ziegeler [mailto:cziegeler@sundn.de]
> > Sent: Thursday, October 18, 2001 9:01 AM
> > To: cocoon-dev@xml.apache.org
> > Subject: AW: AW: [C2.0] Should we set a date for 2.0 Final Release?
> >
> > > Martin Man wrote:
> > >
> > > On Thu, Oct 18, 2001 at 02:52:41PM +0200, Carsten Ziegeler wrote:
> > > > Ok, yes, I didnt check the calendar. Thanks for the hint!
> > > >
> > > > As I still prefer mondays, we should set the dates to
> > > > 5th November: RC2
> > > > 26th November: Final Release
> > >
> > > yep, my +1 also for both dates, BTW: without looking to the
> > > repository, do we
> > > have actualized TODO list... I mean critical isuues (not including
> > > documentation) to fix ???
> > >
> > No, it's nothing more in there.
> > Of course, we have all open/known bugs to fix (entered in bugzilla)
> > and the only other thing currently open which should affect 2.0
> > is the removal of the CodeFactories.
> >
> > Carsten
> > > >
> > > > Carsten
> > > >
> > >
> > > --
> > > 2CC0 4AF6 92DA 5CBF 5F09 7BCB 6202 7024 6E06 0223
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> > > For additional commands, email: cocoon-dev-help@xml.apache.org
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> > For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: AW: [C2.0] Should we set a date for 2.0 Final Release?
Posted by Vadim Gritsenko <va...@verizon.net>.
Carsten,
What do you think about these issues:
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=99780708222079&w=2
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=99814216923705&w=2
Should they be fixed before release, or this will go to the next one?
AFAIK, this is not reflected in bugzilla also...
Vadim
> -----Original Message-----
> From: Carsten Ziegeler [mailto:cziegeler@sundn.de]
> Sent: Thursday, October 18, 2001 9:01 AM
> To: cocoon-dev@xml.apache.org
> Subject: AW: AW: [C2.0] Should we set a date for 2.0 Final Release?
>
> > Martin Man wrote:
> >
> > On Thu, Oct 18, 2001 at 02:52:41PM +0200, Carsten Ziegeler wrote:
> > > Ok, yes, I didnt check the calendar. Thanks for the hint!
> > >
> > > As I still prefer mondays, we should set the dates to
> > > 5th November: RC2
> > > 26th November: Final Release
> >
> > yep, my +1 also for both dates, BTW: without looking to the
> > repository, do we
> > have actualized TODO list... I mean critical isuues (not including
> > documentation) to fix ???
> >
> No, it's nothing more in there.
> Of course, we have all open/known bugs to fix (entered in bugzilla)
> and the only other thing currently open which should affect 2.0
> is the removal of the CodeFactories.
>
> Carsten
> > >
> > > Carsten
> > >
> >
> > --
> > 2CC0 4AF6 92DA 5CBF 5F09 7BCB 6202 7024 6E06 0223
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> > For additional commands, email: cocoon-dev-help@xml.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
AW: AW: [C2.0] Should we set a date for 2.0 Final Release?
Posted by Carsten Ziegeler <cz...@sundn.de>.
> Martin Man wrote:
>
> On Thu, Oct 18, 2001 at 02:52:41PM +0200, Carsten Ziegeler wrote:
> > Ok, yes, I didnt check the calendar. Thanks for the hint!
> >
> > As I still prefer mondays, we should set the dates to
> > 5th November: RC2
> > 26th November: Final Release
>
> yep, my +1 also for both dates, BTW: without looking to the
> repository, do we
> have actualized TODO list... I mean critical isuues (not including
> documentation) to fix ???
>
No, it's nothing more in there.
Of course, we have all open/known bugs to fix (entered in bugzilla)
and the only other thing currently open which should affect 2.0
is the removal of the CodeFactories.
Carsten
> >
> > Carsten
> >
>
> --
> 2CC0 4AF6 92DA 5CBF 5F09 7BCB 6202 7024 6E06 0223
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: AW: [C2.0] Should we set a date for 2.0 Final Release?
Posted by Martin Man <Ma...@seznam.cz>.
On Thu, Oct 18, 2001 at 02:52:41PM +0200, Carsten Ziegeler wrote:
> Ok, yes, I didnt check the calendar. Thanks for the hint!
>
> As I still prefer mondays, we should set the dates to
> 5th November: RC2
> 26th November: Final Release
yep, my +1 also for both dates, BTW: without looking to the repository, do we
have actualized TODO list... I mean critical isuues (not including
documentation) to fix ???
>
> Carsten
>
--
2CC0 4AF6 92DA 5CBF 5F09 7BCB 6202 7024 6E06 0223
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
AW: AW: [C2.0] Should we set a date for 2.0 Final Release?
Posted by Carsten Ziegeler <cz...@sundn.de>.
Ok, yes, I didnt check the calendar. Thanks for the hint!
As I still prefer mondays, we should set the dates to
5th November: RC2
26th November: Final Release
Carsten
> -----Ursprungliche Nachricht-----
> Von: Davanum Srinivas [mailto:dims@yahoo.com]
> Gesendet: Donnerstag, 18. Oktober 2001 14:49
> An: cocoon-dev@xml.apache.org
> Betreff: Re: AW: [C2.0] Should we set a date for 2.0 Final Release?
>
>
> Here's my +1 for RC2, 1st of November.
> Here's my +1 for Final Release, End of November.
>
> Thanks,
> dims
>
> PS: Do you prefer mondays or fridays? No problems switching the
> dates to the nearest
> monday/friday.
>
> --- Carsten Ziegeler <cz...@sundn.de> wrote:
> > Hi,
> >
> > you're absolutely right. It's the same problem here.
> > Due to the many changes I would propose a RC2.
> > But we still need more documentation! So a good
> > date could be 1st of November for the RC2 and
> > end of november for the final release.
> >
> > But whatever date we decide on for the final
> > release, we *should* stick to it.
> >
> > Carsten
> >
> > Open Source Group sunShine - b:Integrated
> > ================================================================
> > Carsten Ziegeler, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
> > www.sundn.de mailto: cziegeler@sundn.de
> > ================================================================
> >
> >
> > > -----Ursprungliche Nachricht-----
> > > Von: Davanum Srinivas [mailto:dims@yahoo.com]
> > > Gesendet: Mittwoch, 17. Oktober 2001 19:02
> > > An: cocoon-dev@xml.apache.org
> > > Betreff: [C2.0] Should we set a date for 2.0 Final Release?
> > >
> > >
> > > Team,
> > > Should we set a date for 2.0 Final Release? (or the next Release
> > > Candidate)? Am a bit tired of
> > > hearing from people (in my organization) that we cannot switch
> > > from C1.X to C2.0 since it is in
> > > Beta/RC Cycle....
> > >
> > > Thanks,
> > > dims
> > >
> > > =====
> > > Davanum Srinivas - http://jguru.com/dims/
> > >
> > > __________________________________________________
> > > Do You Yahoo!?
> > > Make a great connection at Yahoo! Personals.
> > > http://personals.yahoo.com
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> > > For additional commands, email: cocoon-dev-help@xml.apache.org
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> > For additional commands, email: cocoon-dev-help@xml.apache.org
> >
>
>
> =====
> Davanum Srinivas - http://jguru.com/dims/
>
> __________________________________________________
> Do You Yahoo!?
> Make a great connection at Yahoo! Personals.
> http://personals.yahoo.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: AW: [C2.0] Should we set a date for 2.0 Final Release?
Posted by Davanum Srinivas <di...@yahoo.com>.
Here's my +1 for RC2, 1st of November.
Here's my +1 for Final Release, End of November.
Thanks,
dims
PS: Do you prefer mondays or fridays? No problems switching the dates to the nearest
monday/friday.
--- Carsten Ziegeler <cz...@sundn.de> wrote:
> Hi,
>
> you're absolutely right. It's the same problem here.
> Due to the many changes I would propose a RC2.
> But we still need more documentation! So a good
> date could be 1st of November for the RC2 and
> end of november for the final release.
>
> But whatever date we decide on for the final
> release, we *should* stick to it.
>
> Carsten
>
> Open Source Group sunShine - b:Integrated
> ================================================================
> Carsten Ziegeler, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
> www.sundn.de mailto: cziegeler@sundn.de
> ================================================================
>
>
> > -----Ursprungliche Nachricht-----
> > Von: Davanum Srinivas [mailto:dims@yahoo.com]
> > Gesendet: Mittwoch, 17. Oktober 2001 19:02
> > An: cocoon-dev@xml.apache.org
> > Betreff: [C2.0] Should we set a date for 2.0 Final Release?
> >
> >
> > Team,
> > Should we set a date for 2.0 Final Release? (or the next Release
> > Candidate)? Am a bit tired of
> > hearing from people (in my organization) that we cannot switch
> > from C1.X to C2.0 since it is in
> > Beta/RC Cycle....
> >
> > Thanks,
> > dims
> >
> > =====
> > Davanum Srinivas - http://jguru.com/dims/
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Make a great connection at Yahoo! Personals.
> > http://personals.yahoo.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> > For additional commands, email: cocoon-dev-help@xml.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
=====
Davanum Srinivas - http://jguru.com/dims/
__________________________________________________
Do You Yahoo!?
Make a great connection at Yahoo! Personals.
http://personals.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
AW: [C2.0] Should we set a date for 2.0 Final Release?
Posted by Carsten Ziegeler <cz...@sundn.de>.
Hi,
you're absolutely right. It's the same problem here.
Due to the many changes I would propose a RC2.
But we still need more documentation! So a good
date could be 1st of November for the RC2 and
end of november for the final release.
But whatever date we decide on for the final
release, we *should* stick to it.
Carsten
Open Source Group sunShine - b:Integrated
================================================================
Carsten Ziegeler, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
www.sundn.de mailto: cziegeler@sundn.de
================================================================
> -----Ursprungliche Nachricht-----
> Von: Davanum Srinivas [mailto:dims@yahoo.com]
> Gesendet: Mittwoch, 17. Oktober 2001 19:02
> An: cocoon-dev@xml.apache.org
> Betreff: [C2.0] Should we set a date for 2.0 Final Release?
>
>
> Team,
> Should we set a date for 2.0 Final Release? (or the next Release
> Candidate)? Am a bit tired of
> hearing from people (in my organization) that we cannot switch
> from C1.X to C2.0 since it is in
> Beta/RC Cycle....
>
> Thanks,
> dims
>
> =====
> Davanum Srinivas - http://jguru.com/dims/
>
> __________________________________________________
> Do You Yahoo!?
> Make a great connection at Yahoo! Personals.
> http://personals.yahoo.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org