You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Reinhard Poetz <re...@apache.org> on 2008/04/02 17:36:31 UTC
[vote] Release Cocoon 2.2-final
I've prepared the artifacts for the release of Cocoon 2.2 final. See the list of
all proposed artifacts below.
You can find the staged files for all modules (sources, binaries, javadocs,
checksums, gpg signatures) at
- http://people.apache.org/builds/cocoon/
(Maven 2 repo)
- http://people.apache.org/builds/cocoon/cocoon-2.2-all.tar.gz
(tar archive of all artifacts).
SVN tags of all these artifacts can be found at
http://svn.apache.org/repos/asf/cocoon/tags/cocoon-2.2/.
For the final release I've also created release artifacts for people who don't
want to use Maven 2 or Ivy. These artifacts can be found at -
http://people.apache.org/~reinhard/cocoon-staging/. A tar containing all release
artifacts is available at
http://apache.org/~reinhard/cocoon-2.2-non-maven-all.tar.gz.
Note that there is a special release artifact "cocoon-getting-started" that
creates the structure of a Cocoon project, consisting of a web application and
one block, that can be built by plain Ant only.
Find instructions about how you can test in a seperate mail. Report your
findings to that thread and use this one for voting only. Thanks!
This majority vote stays open for 72 hours.
- o -
SUBPROJECT: COCOON CONFIGURATION
============================================
- cocoon-configuration-api-1.0.2.jar
- cocoon-spring-configurator-1.0.2.jar
SUBPROJECT: COCOON SERVLET-SERVICE-FRAMEWORK
============================================
- cocoon-servlet-service-impl-1.0.0.jar
- cocoon-servlet-service-components-1.0.0.jar
COCOON CORE
============================================
- cocoon-xml-api-1.0.0.jar
- cocoon-xml-impl-1.0.0.jar
- cocoon-xml-resolver-1.0.0.jar
- cocoon-xml-util-1.0.0.jar
- cocoon-thread-api-1.0.0.jar
- cocoon-thread-impl-1.0.0.jar
- cocoon-expression-language-api-1.0.0.jar
- cocoon-expression-language-impl-1.0.0.jar
- cocoon-util-1.0.0.jar
- cocoon-store-impl-1.0.0.jar
- cocoon-pipeline-api-1.0.0.jar
- cocoon-pipeline-impl-1.0.0.jar
- cocoon-pipeline-impl-1.0.0-tests.jar
- cocoon-pipeline-components-1.0.0.jar
- cocoon-sitemap-api-1.0.0.jar
- cocoon-sitemap-impl-1.0.0.jar
- cocoon-sitemap-impl-1.0.0-tests.jar
- cocoon-sitemap-components-1.0.0.jar
- cocoon-core-2.2.0.jar
- cocoon-core-2.2.0-tests.jar
COCOON BLOCKS
============================================
- cocoon-template-impl-1.1.0.jar*
- cocoon-flowscript-impl-1.0.0.jar
- cocoon-auth-api-1.0.0.jar
- cocoon-auth-impl-1.0.0.jar
- cocoon-batik-impl-1.0.0.jar
- cocoon-captcha-impl-1.0.0.jar
- cocoon-fop-impl-1.0.0.jar
- cocoon-html-impl-1.0.0.jar
- cocoon-linkrewriter-impl-1.0.0.jar
- cocoon-mail-impl-1.0.0.jar
- cocoon-databases-hsqldb-client-1.0.0.jar
- cocoon-databases-hsqldb-server-1.0.0.jar
- cocoon-databases-mocks-1.0.0.jar
- cocoon-databases-impl-1.0.0.jar
- cocoon-databases-bridge-1.0.0-jar
- cocoon-ajax-impl-1.0.0.jar
- cocoon-apples-impl-1.0.0.jar
- cocoon-forms-impl-1.1.0.jar*
[*] The 1.0.0 releases are still missing but provided for a version that hasn't
been mirgrated to Spring. These artifacts will hopefully follow soon.
COCOON ARCHETYPES
============================================
- cocoon-22-archetype-block-1.0.0.jar
- cocoon-22-archetype-block-plain-1.0.0.jar
- cocoon-22-archetype-webapp-1.0.0.jar
COCOON TOOLS
============================================
- cocoon-it-fw-1.0.0-M1.jar
- cocoon-maven-plugin-1.0.0-M2.jar
--
Reinhard Pötz Managing Director, {Indoqa} GmbH
http://www.indoqa.com/en/people/reinhard.poetz/
Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member, PMC Chair reinhard@apache.org
_________________________________________________________________________
Re: [vote][result] Release Cocoon 2.2-final
Posted by Reinhard Poetz <re...@apache.org>.
David Crossley wrote:
> Reinhard Poetz wrote:
>> Reinhard Poetz wrote:
>>> The proposed modules have been accepted by 7 +1 votes and no negative
>>> one. I'm going move the artifacts into the Apache Maven M2 sync
>>> repository and also move the non-Maven artifacts to the Cocoon
>>> distribution area.
>
> Should we also put the Maven-built artifacts at the /dist/ as well?
> It would mean that people can get the Cocoon-2.2 jars from many
> alternative locations and closer mirrors.
>
> IIUC, Apache Jackrabbit does that, for example.
>
> I reckon that that would get us closer to ASF ideal
> release procedures too.
Yes, Vadim was pushing me to prepare non-Maven release artifacts as well. As I
pointed out in the voting mail, they can be found at
http://people.apache.org/~reinhard/cocoon-staging/. I will move them to our
official distribution area some time next week, when I find some time to figure
out what exactly I have to do and also have some time for the announcement mail.
--
Reinhard Pötz Managing Director, {Indoqa} GmbH
http://www.indoqa.com/en/people/reinhard.poetz/
Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member, PMC Chair reinhard@apache.org
_________________________________________________________________________
Re: [vote][result] Release Cocoon 2.2-final
Posted by David Crossley <cr...@apache.org>.
Reinhard Poetz wrote:
> Reinhard Poetz wrote:
> >
> >The proposed modules have been accepted by 7 +1 votes and no negative
> >one. I'm going move the artifacts into the Apache Maven M2 sync
> >repository and also move the non-Maven artifacts to the Cocoon
> >distribution area.
Should we also put the Maven-built artifacts at the /dist/ as well?
It would mean that people can get the Cocoon-2.2 jars from many
alternative locations and closer mirrors.
IIUC, Apache Jackrabbit does that, for example.
I reckon that that would get us closer to ASF ideal
release procedures too.
> >When everything is available from the mirrors, I will send out the
> >annoucement messages and update our website accordingly. (Probably not
> >until next week ...)
>
> The artifacts are synched with the central Maven repository
> (http://repo1.maven.org/maven2). The announcement mail and the publishing
> of the non-Maven artifacts will follow next week.
Thanks for all of your effort with the releases.
-David
Re: [vote][result] Release Cocoon 2.2-final
Posted by Reinhard Poetz <re...@apache.org>.
Reinhard Poetz wrote:
>
> The proposed modules have been accepted by 7 +1 votes and no negative
> one. I'm going move the artifacts into the Apache Maven M2 sync
> repository and also move the non-Maven artifacts to the Cocoon
> distribution area.
>
> When everything is available from the mirrors, I will send out the
> annoucement messages and update our website accordingly. (Probably not
> until next week ...)
The artifacts are synched with the central Maven repository
(http://repo1.maven.org/maven2). The announcement mail and the publishing of the
non-Maven artifacts will follow next week.
--
Reinhard Pötz Managing Director, {Indoqa} GmbH
http://www.indoqa.com/en/people/reinhard.poetz/
Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member, PMC Chair reinhard@apache.org
_________________________________________________________________________
[vote][result] Release Cocoon 2.2-final
Posted by Reinhard Poetz <re...@apache.org>.
The proposed modules have been accepted by 7 +1 votes and no negative one. I'm
going move the artifacts into the Apache Maven M2 sync repository and also move
the non-Maven artifacts to the Cocoon distribution area.
When everything is available from the mirrors, I will send out the annoucement
messages and update our website accordingly. (Probably not until next week ...)
--
Reinhard Pötz Managing Director, {Indoqa} GmbH
http://www.indoqa.com/en/people/reinhard.poetz/
Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member, PMC Chair reinhard@apache.org
_________________________________________________________________________
Re: [vote] Release Cocoon 2.2-final
Posted by Jeroen Reijn <j....@hippo.nl>.
Reinhard Poetz wrote:
>
> I've prepared the artifacts for the release of Cocoon 2.2 final. See the
> list of
> all proposed artifacts below.
>
+1
Jeroen
Re: [vote] Release Cocoon 2.2-final
Posted by Andrew Savory <as...@apache.org>.
Hi,
On 02/04/2008, Reinhard Poetz <re...@apache.org> wrote:
> Find instructions about how you can test in a seperate mail. Report your
> findings to that thread and use this one for voting only. Thanks!
>
> This majority vote stays open for 72 hours.
+1
Andrew.
Re: [vote] Release Cocoon 2.2-final
Posted by Reinhard Poetz <re...@apache.org>.
Reinhard Poetz wrote:
>
> I've prepared the artifacts for the release of Cocoon 2.2 final. See the
> list of
> all proposed artifacts below.
+1
--
Reinhard Pötz Managing Director, {Indoqa} GmbH
http://www.indoqa.com/en/people/reinhard.poetz/
Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member, PMC Chair reinhard@apache.org
_________________________________________________________________________
Re: [vote] Release Cocoon 2.2-final
Posted by Giacomo Pati <gi...@apache.org>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Reinhard Poetz wrote:
|
| I've prepared the artifacts for the release of Cocoon 2.2 final. See the
| list of
| all proposed artifacts below.
+1
- --
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
iEYEARECAAYFAkf3O2EACgkQLNdJvZjjVZA8MACg3iBUwy1r+xYlHLtcSWcPesPq
rcsAoJI/hncSRcZLljteriJ8g9RcLD4f
=wB7+
-----END PGP SIGNATURE-----
Re: [vote] Release Cocoon 2.2-final
Posted by Dev at weitling <de...@weitling.net>.
Grzegorz Kossakowski wrote:
> Dev at weitling pisze:
>> BTW: If I could meet some of you wizards and get an indoctrination I
>> could/would improve docs.
>
> Florian, are you coming to ApacheCon (hackathon days)? If not, I'm
> available in Warsaw almost all the time always willing to speak about
> Cocoon. :-)
I'd like to, but they enchained me here, leaving me bread, water and a
computer ;-)
ApacheCon takes place at my first days at a new employer, I hope there
will be a second CocoonGT (or the like) this year?
Bye,
Florian
Re: [vote] Release Cocoon 2.2-final
Posted by Grzegorz Kossakowski <gr...@tuffmail.com>.
Dev at weitling pisze:
>
> Despite my sometimes dumb question here on the list I know Cocoon is
> really cool and still improving. But without good docs the developers
> and the users separate more and more. There are many people who want to
> contribute to Cocoon, but most of them do only have spare time and are
> not paid by a company with interest in Cocoon. For them it's really hard
> to dig trough the docs to understand things before they can even think
> of contributing code.
>
> Why not introduce documentation releases?
To be honest I'm not sure what kind of policy we have about publishing docs but I consider this a
continuous process. For example, Luca has contributed some docs that will get published once I (or
any other committer) finds few minutes to review them.
I don't think it makes that much sense to synchronize docs publishing with artifact releases.
> BTW: If I could meet some of you wizards and get an indoctrination I
> could/would improve docs.
Florian, are you coming to ApacheCon (hackathon days)? If not, I'm available in Warsaw almost all
the time always willing to speak about Cocoon. :-)
--
Grzegorz Kossakowski
Re: [vote] Release Cocoon 2.2-final
Posted by Dev at weitling <de...@weitling.net>.
Carsten Ziegeler wrote:
> Dev at weitling wrote:
>>
>> Sorry, I can't agree. Cocoon still has the same fault as many
>> open-source products: A lack of documentation.
>> I don't know if GSoC is for docs, too, but it is really, really
>> necessary to improve docs.
>> It's still the same Catch-22: To write docs you need to understand
>> the developed, to understand the developed you need the docs, ...
>> Writing docs does belong to development, even when it seems to be at
>> a kindergarden level for newbies!
>>
> I think we all agree that we need docs (or more/better docs),
> absolutely no doubt. And I think we also agree that writing docs is
> one task of the development process, and it's an important task.
>
> But we can't force anyone to write docs; and delaying a release
> because of lacking documentation is not producing the desired effect:
> instead of getting docs this way, nothing is usually happening: no
> docs and no release.
> I don't say that I'm happy about this.
Despite my sometimes dumb question here on the list I know Cocoon is
really cool and still improving. But without good docs the developers
and the users separate more and more. There are many people who want to
contribute to Cocoon, but most of them do only have spare time and are
not paid by a company with interest in Cocoon. For them it's really hard
to dig trough the docs to understand things before they can even think
of contributing code.
Why not introduce documentation releases?
BTW: If I could meet some of you wizards and get an indoctrination I
could/would improve docs.
Florian
Re: [vote] Release Cocoon 2.2-final
Posted by Sylvain Wallez <sy...@apache.org>.
Carsten Ziegeler wrote:
> Dev at weitling wrote:
>>
>> Sorry, I can't agree. Cocoon still has the same fault as many
>> open-source products: A lack of documentation.
>> I don't know if GSoC is for docs, too, but it is really, really
>> necessary to improve docs.
>> It's still the same Catch-22: To write docs you need to understand
>> the developed, to understand the developed you need the docs, ...
>> Writing docs does belong to development, even when it seems to be at
>> a kindergarden level for newbies!
>>
> I think we all agree that we need docs (or more/better docs),
> absolutely no doubt. And I think we also agree that writing docs is
> one task of the development process, and it's an important task.
>
> But we can't force anyone to write docs; and delaying a release
> because of lacking documentation is not producing the desired effect:
> instead of getting docs this way, nothing is usually happening: no
> docs and no release.
> I don't say that I'm happy about this.
Yes. That's exactly what I meant! Thanks for making it clear Carsten :-)
Sylvain
--
Sylvain Wallez - http://bluxte.net
Re: [vote] Release Cocoon 2.2-final
Posted by Carsten Ziegeler <cz...@apache.org>.
Dev at weitling wrote:
>
> Sorry, I can't agree. Cocoon still has the same fault as many
> open-source products: A lack of documentation.
> I don't know if GSoC is for docs, too, but it is really, really
> necessary to improve docs.
> It's still the same Catch-22: To write docs you need to understand the
> developed, to understand the developed you need the docs, ...
> Writing docs does belong to development, even when it seems to be at a
> kindergarden level for newbies!
>
I think we all agree that we need docs (or more/better docs), absolutely
no doubt. And I think we also agree that writing docs is one task of the
development process, and it's an important task.
But we can't force anyone to write docs; and delaying a release because
of lacking documentation is not producing the desired effect: instead of
getting docs this way, nothing is usually happening: no docs and no release.
I don't say that I'm happy about this.
Carsten
--
Carsten Ziegeler
cziegeler@apache.org
Re: [vote] Release Cocoon 2.2-final
Posted by Dev at weitling <de...@weitling.net>.
Sylvain Wallez wrote:
> Carsten Ziegeler wrote:
>> Luca Morandini wrote:
>>> Reinhard Poetz wrote:
>>>>
>>>> I've prepared the artifacts for the release of Cocoon 2.2 final.
>>>
>>> There is much room for improvement in the doc though: don't you
>>> think it should be improved before release ?
>>>
>> It would be great to have better docs, but honestly who is going to
>> write them? We can either release with the docs we have or wait
>> forever for better docs and never release. From these two choices I
>> prefer the first one. Anything between these two extremes is imho not
>> going to happen.
>> We might not get some new users because of bad docs, but we might get
>> people really interested in a new Cocoon. If we wait for better docs
>> we loose everyone as we never release.
>
> Yup. And add to this the fact that doc lifecycle is different from the
> software lifecycle, since there is no doc releases, but a continuous
> improvement.
Sorry, I can't agree. Cocoon still has the same fault as many
open-source products: A lack of documentation.
I don't know if GSoC is for docs, too, but it is really, really
necessary to improve docs.
It's still the same Catch-22: To write docs you need to understand the
developed, to understand the developed you need the docs, ...
Writing docs does belong to development, even when it seems to be at a
kindergarden level for newbies!
Just my 0,02 CHF
Florian
Re: [vote] Release Cocoon 2.2-final
Posted by Sylvain Wallez <sy...@apache.org>.
Carsten Ziegeler wrote:
> Luca Morandini wrote:
>> Reinhard Poetz wrote:
>>>
>>> I've prepared the artifacts for the release of Cocoon 2.2 final.
>>
>> There is much room for improvement in the doc though: don't you think
>> it should be improved before release ?
>>
> It would be great to have better docs, but honestly who is going to
> write them? We can either release with the docs we have or wait
> forever for better docs and never release. From these two choices I
> prefer the first one. Anything between these two extremes is imho not
> going to happen.
> We might not get some new users because of bad docs, but we might get
> people really interested in a new Cocoon. If we wait for better docs
> we loose everyone as we never release.
Yup. And add to this the fact that doc lifecycle is different from the
software lifecycle, since there is no doc releases, but a continuous
improvement.
Sylvain
--
Sylvain Wallez - http://bluxte.net
Re: [vote] Release Cocoon 2.2-final
Posted by Grzegorz Kossakowski <gr...@tuffmail.com>.
Andreas Hartmann pisze:
> Luca Morandini schrieb:
>> Carsten Ziegeler wrote:
>>> It would be great to have better docs, but honestly who is going to
>>> write them?
>>
>> Some (most ?) of it has been already written, it's just a matter of
>> copying it from Javadoc (or 2.1 docs pages) to the 2.2 ones, and check
>> its currentness, of course.
>>
>>
>>> We might not get some new users because of bad docs, but we might get
>>> people really interested in a new Cocoon.
>>
>> Does it mean we already gave up with attracting new users ?
>>
>> What's the "mission" of 2.2 then ?
>>
>> As I see it, this release has the potential of attracting new users to
>> a leaner, meaner Cocoon, but then we should be able to greet them
>> appropriately.
>>
>> As for "old" users: I can talk only for myself, but I think 2.2 is
>> great for new projects only, since it doesn't pay to Springify and
>> Mavenize old ones.
>
> I don't think so - that depends on the situation. We at Lenya will have
> to upgrade sooner or later, otherwise we'd lose touch with the Cocoon
> community and we'd have to backport all fixes and improvements. Most
> people who maintain an ongoing project will do the migration, whether it
> makes sense from a technological point of view or not.
>
> Regarding documentation: In my experience, one of the best ways for
> creating docs is via personal "marketing". When people create a tutorial
> on their blogs or a presentation for a conference, the effort to move
> these contents to the project docs isn't that big (a big chunk of the
> Lenya documentation was developed this way). Maybe some of the
> developers could provide their slides? Even some links to slideshare.net
> could certainly be helpful.
That's some kind of idea... Need to blow cobweb away from my blog.. :-)
--
Grzegorz
Re: [vote] Release Cocoon 2.2-final
Posted by Andreas Hartmann <an...@apache.org>.
Luca Morandini schrieb:
> Carsten Ziegeler wrote:
>> It would be great to have better docs, but honestly who is going to
>> write them?
>
> Some (most ?) of it has been already written, it's just a matter of
> copying it from Javadoc (or 2.1 docs pages) to the 2.2 ones, and check
> its currentness, of course.
>
>
>> We might not get some new users because of bad docs, but we might get
>> people really interested in a new Cocoon.
>
> Does it mean we already gave up with attracting new users ?
>
> What's the "mission" of 2.2 then ?
>
> As I see it, this release has the potential of attracting new users to a
> leaner, meaner Cocoon, but then we should be able to greet them
> appropriately.
>
> As for "old" users: I can talk only for myself, but I think 2.2 is great
> for new projects only, since it doesn't pay to Springify and Mavenize
> old ones.
I don't think so - that depends on the situation. We at Lenya will have
to upgrade sooner or later, otherwise we'd lose touch with the Cocoon
community and we'd have to backport all fixes and improvements. Most
people who maintain an ongoing project will do the migration, whether it
makes sense from a technological point of view or not.
Regarding documentation: In my experience, one of the best ways for
creating docs is via personal "marketing". When people create a tutorial
on their blogs or a presentation for a conference, the effort to move
these contents to the project docs isn't that big (a big chunk of the
Lenya documentation was developed this way). Maybe some of the
developers could provide their slides? Even some links to slideshare.net
could certainly be helpful.
-- Andreas
> So, we got two distinct classes of users:
> 1) Old ones, which will use 2.2 as new projects come in, hence allowing
> for a rather long transition period.
> 2) New ones, which will be very sensible to good docs and samples and
> will try 2.2 right after its release.
>
> The current state of docs is good enough for the old users, not for the
> new ones, I think.
>
> Hence, 2.2 faces the fate of being caught between old users adopting it
> very slowly and new users not adopting it in great numbers... not an
> exciting prospect.
>
> Regards,
>
> --------------------
> Luca Morandini
> www.lucamorandini.it
> --------------------
>
>
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
Re: [vote] Release Cocoon 2.2-final
Posted by Luca Morandini <lm...@ieee.org>.
Carsten Ziegeler wrote:
> It would be great to have better docs, but honestly who is going to
> write them?
Some (most ?) of it has been already written, it's just a matter of
copying it from Javadoc (or 2.1 docs pages) to the 2.2 ones, and check
its currentness, of course.
> We might not get some new users because of bad docs, but we might get
> people really interested in a new Cocoon.
Does it mean we already gave up with attracting new users ?
What's the "mission" of 2.2 then ?
As I see it, this release has the potential of attracting new users to a
leaner, meaner Cocoon, but then we should be able to greet them
appropriately.
As for "old" users: I can talk only for myself, but I think 2.2 is great
for new projects only, since it doesn't pay to Springify and Mavenize
old ones.
So, we got two distinct classes of users:
1) Old ones, which will use 2.2 as new projects come in, hence allowing
for a rather long transition period.
2) New ones, which will be very sensible to good docs and samples and
will try 2.2 right after its release.
The current state of docs is good enough for the old users, not for the
new ones, I think.
Hence, 2.2 faces the fate of being caught between old users adopting it
very slowly and new users not adopting it in great numbers... not an
exciting prospect.
Regards,
--------------------
Luca Morandini
www.lucamorandini.it
--------------------
Re: [vote] Release Cocoon 2.2-final
Posted by Carsten Ziegeler <cz...@apache.org>.
Luca Morandini wrote:
> Reinhard Poetz wrote:
>>
>> I've prepared the artifacts for the release of Cocoon 2.2 final.
>
> There is much room for improvement in the doc though: don't you think it
> should be improved before release ?
>
It would be great to have better docs, but honestly who is going to
write them? We can either release with the docs we have or wait forever
for better docs and never release. From these two choices I prefer the
first one. Anything between these two extremes is imho not going to happen.
We might not get some new users because of bad docs, but we might get
people really interested in a new Cocoon. If we wait for better docs we
loose everyone as we never release.
Carsten
--
Carsten Ziegeler
cziegeler@apache.org
Re: [vote] Release Cocoon 2.2-final
Posted by Luca Morandini <lm...@ieee.org>.
Reinhard Poetz wrote:
> Luca Morandini wrote:
>> Reinhard Poetz wrote:
>>>
>>> I've prepared the artifacts for the release of Cocoon 2.2 final.
>>
>> There is much room for improvement in the doc though: don't you think
>> it should be improved before release ?
>
> What's your plan?
Well, let's wargame the thing:
1) The community releases 2.2.
2) Hopefully, a lot of people would download it and try the tutorials,
(which are good) and people would find it easy to get into Cocoon.
3) A few people would venture deeper, looking at the components' doc and
trying things not covered by the tutorials (like I did).
4) They would find that many components have no doc available (though
most are unchanged from 2.1) and some doc is outdated (for instance, I
had to fix the CForms sample, otherwise it would not have worked in 2.2).
5) Some of them would find the answers they need in the Javadoc, or send
messages to the list, or look into the source code.
6) Some of them, regretfully, would simply find Cocoon too hard to learn
and drop it.
Now, I'd try to avoid people doing 6 by combing the doc and setting it
on a par with the 2.1 doc.
Actually, since it took so long in the making, I suspect people expect a
polished product, in both code and doc.
On a more general note, it would be nice to send this message: "Cocoon
2.2 is a major rewrite: now the old dog is highly modular, Spring-ified,
Mavenized, but still more flexible than Struts 2 or Webflow and far more
powerful and clean than Wicket or JSF"... but we need better doc for
this, I presume.
Regards,
--------------------
Luca Morandini
www.lucamorandini.it
--------------------
Re: [vote] Release Cocoon 2.2-final
Posted by Reinhard Poetz <re...@apache.org>.
Luca Morandini wrote:
> Reinhard Poetz wrote:
>>
>> I've prepared the artifacts for the release of Cocoon 2.2 final.
>
> There is much room for improvement in the doc though: don't you think it
> should be improved before release ?
What's your plan?
--
Reinhard Pötz Managing Director, {Indoqa} GmbH
http://www.indoqa.com/en/people/reinhard.poetz/
Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member, PMC Chair reinhard@apache.org
_________________________________________________________________________
Re: [vote] Release Cocoon 2.2-final
Posted by Luca Morandini <lm...@ieee.org>.
Reinhard Poetz wrote:
>
> I've prepared the artifacts for the release of Cocoon 2.2 final.
There is much room for improvement in the doc though: don't you think it
should be improved before release ?
Just my 2€c.
Regards,
--------------------
Luca Morandini
www.lucamorandini.it
--------------------
Re: [vote] Release Cocoon 2.2-final
Posted by Grzegorz Kossakowski <gr...@tuffmail.com>.
Reinhard Poetz pisze:
>
> I've prepared the artifacts for the release of Cocoon 2.2 final. See the
> list of
> all proposed artifacts below.
>
> You can find the staged files for all modules (sources, binaries, javadocs,
> checksums, gpg signatures) at
>
> - http://people.apache.org/builds/cocoon/
> (Maven 2 repo)
> - http://people.apache.org/builds/cocoon/cocoon-2.2-all.tar.gz
> (tar archive of all artifacts).
>
>
> SVN tags of all these artifacts can be found at
> http://svn.apache.org/repos/asf/cocoon/tags/cocoon-2.2/.
>
> For the final release I've also created release artifacts for people who
> don't
> want to use Maven 2 or Ivy. These artifacts can be found at -
> http://people.apache.org/~reinhard/cocoon-staging/. A tar containing all
> release
> artifacts is available at
> http://apache.org/~reinhard/cocoon-2.2-non-maven-all.tar.gz.
>
>
> Note that there is a special release artifact "cocoon-getting-started" that
> creates the structure of a Cocoon project, consisting of a web
> application and
> one block, that can be built by plain Ant only.
>
>
> Find instructions about how you can test in a seperate mail. Report your
> findings to that thread and use this one for voting only. Thanks!
>
> This majority vote stays open for 72 hours.
tested little bit more yesterday, works fine. Here is my:
+1
--
Grzegorz Kossakowski
Re: [vote] Release Cocoon 2.2-final
Posted by Joerg Heinicke <jo...@gmx.de>.
On 03.04.2008 15:06, Grzegorz Kossakowski wrote:
>> COCOON BLOCKS
>> ============================================
>> - cocoon-template-impl-1.1.0.jar*
>> - cocoon-forms-impl-1.1.0.jar*
>>
>> [*] The 1.0.0 releases are still missing but provided for a version
>> that hasn't
>> been mirgrated to Spring. These artifacts will hopefully follow soon.
>
> Any reason for such a weird practice marked with [*]? It's really
> questionable to release 1.1.0 before 1.0.0...
If think you of linearly releases, yes, it is weird. But we have
branches, so I don't see a real problem with it. Would be nice if we
could release them sometime in the next weeks though.
Joerg
Re: [vote] Release Cocoon 2.2-final
Posted by Reinhard Poetz <re...@apache.org>.
Grzegorz Kossakowski wrote:
>> [*] The 1.0.0 releases are still missing but provided for a version
>> that hasn't
>> been mirgrated to Spring. These artifacts will hopefully follow soon.
>
> Any reason for such a weird practice marked with [*]? It's really
> questionable to release 1.1.0 before 1.0.0...
I noticed that not until I wrote the voting mail and don't have time to create
the 1.0.0 releases of those two modules happen neither this week nor the next.
Maybe somebody else can help out ...
--
Reinhard Pötz Managing Director, {Indoqa} GmbH
http://www.indoqa.com/en/people/reinhard.poetz/
Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member, PMC Chair reinhard@apache.org
_________________________________________________________________________
Re: [vote] Release Cocoon 2.2-final
Posted by Grzegorz Kossakowski <gr...@tuffmail.com>.
Reinhard Poetz pisze:
>
> I've prepared the artifacts for the release of Cocoon 2.2 final. See the
> list of
> all proposed artifacts below.
>
> You can find the staged files for all modules (sources, binaries, javadocs,
> checksums, gpg signatures) at
>
> - http://people.apache.org/builds/cocoon/
> (Maven 2 repo)
> - http://people.apache.org/builds/cocoon/cocoon-2.2-all.tar.gz
> (tar archive of all artifacts).
>
>
> SVN tags of all these artifacts can be found at
> http://svn.apache.org/repos/asf/cocoon/tags/cocoon-2.2/.
>
> For the final release I've also created release artifacts for people who
> don't
> want to use Maven 2 or Ivy. These artifacts can be found at -
> http://people.apache.org/~reinhard/cocoon-staging/. A tar containing all
> release
> artifacts is available at
> http://apache.org/~reinhard/cocoon-2.2-non-maven-all.tar.gz.
>
>
> Note that there is a special release artifact "cocoon-getting-started" that
> creates the structure of a Cocoon project, consisting of a web
> application and
> one block, that can be built by plain Ant only.
>
>
> Find instructions about how you can test in a seperate mail. Report your
> findings to that thread and use this one for voting only. Thanks!
>
> This majority vote stays open for 72 hours.
>
>
> - o -
>
>
> SUBPROJECT: COCOON CONFIGURATION
> ============================================
> - cocoon-configuration-api-1.0.2.jar
> - cocoon-spring-configurator-1.0.2.jar
>
> SUBPROJECT: COCOON SERVLET-SERVICE-FRAMEWORK
> ============================================
> - cocoon-servlet-service-impl-1.0.0.jar
> - cocoon-servlet-service-components-1.0.0.jar
>
> COCOON CORE
> ============================================
> - cocoon-xml-api-1.0.0.jar
> - cocoon-xml-impl-1.0.0.jar
> - cocoon-xml-resolver-1.0.0.jar
> - cocoon-xml-util-1.0.0.jar
> - cocoon-thread-api-1.0.0.jar
> - cocoon-thread-impl-1.0.0.jar
> - cocoon-expression-language-api-1.0.0.jar
> - cocoon-expression-language-impl-1.0.0.jar
> - cocoon-util-1.0.0.jar
> - cocoon-store-impl-1.0.0.jar
> - cocoon-pipeline-api-1.0.0.jar
> - cocoon-pipeline-impl-1.0.0.jar
> - cocoon-pipeline-impl-1.0.0-tests.jar
> - cocoon-pipeline-components-1.0.0.jar
> - cocoon-sitemap-api-1.0.0.jar
> - cocoon-sitemap-impl-1.0.0.jar
> - cocoon-sitemap-impl-1.0.0-tests.jar
> - cocoon-sitemap-components-1.0.0.jar
> - cocoon-core-2.2.0.jar
> - cocoon-core-2.2.0-tests.jar
>
> COCOON BLOCKS
> ============================================
> - cocoon-template-impl-1.1.0.jar*
> - cocoon-flowscript-impl-1.0.0.jar
> - cocoon-auth-api-1.0.0.jar
> - cocoon-auth-impl-1.0.0.jar
> - cocoon-batik-impl-1.0.0.jar
> - cocoon-captcha-impl-1.0.0.jar
> - cocoon-fop-impl-1.0.0.jar
> - cocoon-html-impl-1.0.0.jar
> - cocoon-linkrewriter-impl-1.0.0.jar
> - cocoon-mail-impl-1.0.0.jar
> - cocoon-databases-hsqldb-client-1.0.0.jar
> - cocoon-databases-hsqldb-server-1.0.0.jar
> - cocoon-databases-mocks-1.0.0.jar
> - cocoon-databases-impl-1.0.0.jar
> - cocoon-databases-bridge-1.0.0-jar
> - cocoon-ajax-impl-1.0.0.jar
> - cocoon-apples-impl-1.0.0.jar
> - cocoon-forms-impl-1.1.0.jar*
>
> [*] The 1.0.0 releases are still missing but provided for a version that
> hasn't
> been mirgrated to Spring. These artifacts will hopefully follow soon.
Any reason for such a weird practice marked with [*]? It's really questionable to release 1.1.0
before 1.0.0...
--
Grzegorz Kossakowski
Re: [vote] Release Cocoon 2.2-final
Posted by Felix Knecht <fe...@apache.org>.
Reinhard Poetz schrieb:
>
> I've prepared the artifacts for the release of Cocoon 2.2 final. See
> the list of
> all proposed artifacts below.
>
+1
I tested it with our apps and they still work fine.
Felix
Re: [vote] Release Cocoon 2.2-final
Posted by Ralph Goers <Ra...@dslextreme.com>.
You going to the happiest place on earth? Isn't that Carsten's favorite
place? Never having been (Disneyland is only 1 hr from here) I can't
whether Orlando is much of a culture shock but I somehow doubt it. Try
New York, San Francisco or Hollywood for that.
Joerg Heinicke wrote:
> On 02.04.2008 11:36, Reinhard Poetz wrote:
>
>> I've prepared the artifacts for the release of Cocoon 2.2 final.
>
>> Find instructions about how you can test in a seperate mail. Report your
>> findings to that thread and use this one for voting only. Thanks!
>
> +1 Unfortunately without testing. I planned to do it but haven't made it
>
> ... and in few hours I'm leaving for 1 week of American culture shock:
> Orlando, Florida :)
>
> Joerg
Re: [vote] Release Cocoon 2.2-final
Posted by Leszek Gawron <lg...@mobilebox.pl>.
Joerg Heinicke wrote:
> On 02.04.2008 11:36, Reinhard Poetz wrote:
>
>> I've prepared the artifacts for the release of Cocoon 2.2 final.
>
>> Find instructions about how you can test in a seperate mail. Report your
>> findings to that thread and use this one for voting only. Thanks!
>
> +1 Unfortunately without testing. I planned to do it but haven't made it
A little bit too late but I managed to happily port some of my
production applications to 2.2 and they work without any problem.
>
> ... and in few hours I'm leaving for 1 week of American culture shock:
> Orlando, Florida :)
BB conference maybe?
--
Leszek Gawron http://www.mobilebox.pl/krs.html
CTO at MobileBox Ltd.
Re: [vote] Release Cocoon 2.2-final
Posted by Joerg Heinicke <jo...@gmx.de>.
On 02.04.2008 11:36, Reinhard Poetz wrote:
> I've prepared the artifacts for the release of Cocoon 2.2 final.
> Find instructions about how you can test in a seperate mail. Report your
> findings to that thread and use this one for voting only. Thanks!
+1 Unfortunately without testing. I planned to do it but haven't made it
... and in few hours I'm leaving for 1 week of American culture shock:
Orlando, Florida :)
Joerg