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
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
-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 -
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
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
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
Andrew Savory wrote:
Hi,
We should accept this and get 2.2 out the door (honestly, I think
delaying it further will lose more users than not having sufficient
docs) and then if we can, turn some of the energy of this debate into
writing docs. Better yet, let's be diligent in taking questions on
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
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
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
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
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
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
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
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
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
Hi,
(Changing subject, starting new thread. Please, when an email says
'this thread is for votes only', try to respect that!)
On 03/04/2008, Luca Morandini [EMAIL PROTECTED] wrote:
Carsten Ziegeler wrote:
We might not get some new users because of bad docs, but we might get
people really
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
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
Hi,
On 02/04/2008, Reinhard Poetz [EMAIL PROTECTED] 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.
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
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
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
Andrew Savory pisze:
Hi,
(Changing subject, starting new thread. Please, when an email says
'this thread is for votes only', try to respect that!)
On 03/04/2008, Luca Morandini [EMAIL PROTECTED] wrote:
Carsten Ziegeler wrote:
We might not get some new users because of bad docs, but we might
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'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)
-
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ötzManaging Director, {Indoqa} GmbH
http://www.indoqa.com/en/people/reinhard.poetz/
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
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
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
30 matches
Mail list logo
