Discussion:
[DISCUSS] Releasing 2.1.12
Francesco Chicchiriccò
2012-11-18 17:35:08 UTC
Permalink
Hi all (but Cédric in particular),
by looking at JIRA [1] it seems that quite a considerable number of
issues have been fixed since 2.1.11 (31) even though some are still
standing (11+2).

Following our recent discussion in another thread, I have some questions
to Cédric (and other C2.1 devs, if there are...):

1. Do you think that the the 13 outstanding issues can be moved to
2.1.13 or there are some that need to be absolutely included in 2.1.12?

2. Is the release process clear to you? If not, who (maybe active in
the past) can provide some hint?

3. Do you need any help in the release process? If so, who is
available to help? I am, even though I don't remember pretty anything of
C2.1...

4. Considering the questions above, when do you think we can start
releasing 2.1.12?

Thanks for info.
Regards.

[1]
https://issues.apache.org/jira/browse/COCOON/fixforversion/12312903#selectedTab=com.atlassian.jira.plugin.system.project%3Aversion-issues-panel
--
Francesco Chicchiriccò

ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member
http://people.apache.org/~ilgrosso/
Cédric Damioli
2012-11-19 09:45:54 UTC
Permalink
Hi,
Post by Francesco Chicchiriccò
Hi all (but Cédric in particular),
by looking at JIRA [1] it seems that quite a considerable number of
issues have been fixed since 2.1.11 (31) even though some are still
standing (11+2).
Following our recent discussion in another thread, I have some
1. Do you think that the the 13 outstanding issues can be moved to
2.1.13 or there are some that need to be absolutely included in 2.1.12?
3 of them were opened by myself before gaining committership. [1] [2] [3]
I could have closed them already, but was waiting for others' approval.
I don't know if someone has something to say about them ...

The 10 others issues are more than 2 years old

There are also 74 issues with no "fix for" version (29 with a patch
included) but affecting a 2.1.x version

We should maybe ask 2.1 users if there are particular issues they want
to be fixed before cutting a 2.1.12 ?
Post by Francesco Chicchiriccò
2. Is the release process clear to you? If not, who (maybe active in
the past) can provide some hint?
Not really.
I think there was once a page written by Carsten describing the release
process, but I can't find it anymore.
Post by Francesco Chicchiriccò
3. Do you need any help in the release process? If so, who is
available to help? I am, even though I don't remember pretty anything
of C2.1...
Yes please
It would be great if 2 or 3 people other than me could try to run unit
tests and run samples.
Almost 5 years after the 2.1.11, I also don't remember all blocks, it
would be great to also have feedbacks from users of some specific blocks.
Post by Francesco Chicchiriccò
4. Considering the questions above, when do you think we can start
releasing 2.1.12?
Depending if we try to gather some feedbacks from devs and users or not,
it could be quite fast, say in the next few days.
But 5 years after, we can afford one or two more weeks if needed
Post by Francesco Chicchiriccò
Thanks for info.
Regards.
[1]
https://issues.apache.org/jira/browse/COCOON/fixforversion/12312903#selectedTab=com.atlassian.jira.plugin.system.project%3Aversion-issues-panel
[1] https://issues.apache.org/jira/browse/COCOON-2288
[2] https://issues.apache.org/jira/browse/COCOON-2313
[3] https://issues.apache.org/jira/browse/COCOON-2314

Best regards,
--
Cédric Damioli
Ametys CMS
http://www.ametys.org
http://www.anyware-services.com
Francesco Chicchiriccò
2012-11-19 10:40:24 UTC
Permalink
Post by Cédric Damioli
Hi,
Post by Francesco Chicchiriccò
Hi all (but Cédric in particular),
by looking at JIRA [1] it seems that quite a considerable number of
issues have been fixed since 2.1.11 (31) even though some are still
standing (11+2).
Following our recent discussion in another thread, I have some
1. Do you think that the the 13 outstanding issues can be moved to
2.1.13 or there are some that need to be absolutely included in 2.1.12?
3 of them were opened by myself before gaining committership. [1] [2] [3]
I could have closed them already, but was waiting for others'
approval. I don't know if someone has something to say about them ...
I think you can safely apply the "lazy consensus" [1] here, especially
since it seems there is no one else - but you - taking care of C2.1
issues :-(
Post by Cédric Damioli
The 10 others issues are more than 2 years old
There are also 74 issues with no "fix for" version (29 with a patch
included) but affecting a 2.1.x version
We should maybe ask 2.1 users if there are particular issues they want
to be fixed before cutting a 2.1.12 ?
I think you should send an e-mail to users@ ML asking to review the 74
issues reported above (a direct link to the JIRA search would be
helpful) and to explicitly set the fix-for-version to 2.1.12 if they
absolutely require so.
Once 72 hours have passed by, you can look at the results and see what
to do; for any other non-answered issue, I think you can apply again [4].
Post by Cédric Damioli
Post by Francesco Chicchiriccò
2. Is the release process clear to you? If not, who (maybe active
in the past) can provide some hint?
Not really.
I think there was once a page written by Carsten describing the
release process, but I can't find it anymore.
I guess we should directly ask Carlsten, then: let's see if he replies
here, otherwise we can try to contact him somehow else.
Post by Cédric Damioli
Post by Francesco Chicchiriccò
3. Do you need any help in the release process? If so, who is
available to help? I am, even though I don't remember pretty anything
of C2.1...
Yes please
It would be great if 2 or 3 people other than me could try to run unit
tests and run samples.
Almost 5 years after the 2.1.11, I also don't remember all blocks, it
would be great to also have feedbacks from users of some specific blocks.
Just show what steps are needed to make such verifications; about the
"completeness" of such verifications, I think that only dalily usage can
do better, hence don't worry too much.
Post by Cédric Damioli
Post by Francesco Chicchiriccò
4. Considering the questions above, when do you think we can start
releasing 2.1.12?
Depending if we try to gather some feedbacks from devs and users or
not, it could be quite fast, say in the next few days.
But 5 years after, we can afford one or two more weeks if needed
My opinion here is to try to be as safe as possible, but also to try to
release ASAP - at most before the end of the year: we cannot afford
additional delay: let's apply [4] as much as possible and leave any
missing piece from 2.1.13: I hope it won't take 4 more years :-)

Regards.
Post by Cédric Damioli
Post by Francesco Chicchiriccò
[1]
https://issues.apache.org/jira/browse/COCOON/fixforversion/12312903#selectedTab=com.atlassian.jira.plugin.system.project%3Aversion-issues-panel
[1] https://issues.apache.org/jira/browse/COCOON-2288
[2] https://issues.apache.org/jira/browse/COCOON-2313
[3] https://issues.apache.org/jira/browse/COCOON-2314
[4] http://www.apache.org/foundation/glossary.html#LazyConsensus
--
Francesco Chicchiriccò

ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member
http://people.apache.org/~ilgrosso/
Francesco Chicchiriccò
2012-11-19 11:00:52 UTC
Permalink
Post by Francesco Chicchiriccò
[...]
Post by Cédric Damioli
Post by Francesco Chicchiriccò
2. Is the release process clear to you? If not, who (maybe active
in the past) can provide some hint?
Not really.
I think there was once a page written by Carsten describing the
release process, but I can't find it anymore.
I guess we should directly ask Carlsten, then: let's see if he replies
here, otherwise we can try to contact him somehow else.
What about http://wiki.apache.org/cocoon/CocoonReleaseHowTo ?
--
Francesco Chicchiriccò

ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member
http://people.apache.org/~ilgrosso/
Cédric Damioli
2012-11-19 14:12:29 UTC
Permalink
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
[...]
Post by Cédric Damioli
Post by Francesco Chicchiriccò
2. Is the release process clear to you? If not, who (maybe active
in the past) can provide some hint?
Not really.
I think there was once a page written by Carsten describing the
release process, but I can't find it anymore.
I guess we should directly ask Carlsten, then: let's see if he
replies here, otherwise we can try to contact him somehow else.
What about http://wiki.apache.org/cocoon/CocoonReleaseHowTo ?
It seems to be what I was looking for.
I was searching in the site and didn't remember there was a wiki !
Post by Francesco Chicchiriccò
--
Francesco Chicchiriccò
ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member
http://people.apache.org/~ilgrosso/
--
Cédric Damioli
Ametys CMS
http://www.ametys.org
http://www.anyware-services.com
David Crossley
2012-11-21 22:43:19 UTC
Permalink
Post by Cédric Damioli
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
[...]
Post by Cédric Damioli
Post by Francesco Chicchiriccò
2. Is the release process clear to you? If not, who (maybe active
in the past) can provide some hint?
Not really.
I think there was once a page written by Carsten describing the
release process, but I can't find it anymore.
I guess we should directly ask Carlsten, then: let's see if he
replies here, otherwise we can try to contact him somehow else.
What about http://wiki.apache.org/cocoon/CocoonReleaseHowTo ?
It seems to be what I was looking for.
I was searching in the site and didn't remember there was a wiki !
I am still around from the olden days and will try
to help. However my time is very limited.

People on the user list should be invited to
sign up to the "dev" list and assist, even if
it is just to test samples and tweak docs.

-David
Sylvain Wallez
2012-11-22 10:57:33 UTC
Permalink
Post by David Crossley
I am still around from the olden days and will try
to help. However my time is very limited.
Same for here! I would be happy to help where I can, but have limited time.

Sylvain
--
Sylvain Wallez - http://bluxte.net
Francesco Chicchiriccò
2012-11-22 12:55:42 UTC
Permalink
Post by Sylvain Wallez
I am still around from the olden days and will try to help. However
my time is very limited.
Same for here! I would be happy to help where I can, but have limited time.
That sounds great: with two "old foxes" like you things can only raise
better :-)

I think Cédric would need some help especially with pre-release checks
and issues related to blocks he has never dealt with; Cédric, is this
correct?

Regards.
--
Francesco Chicchiriccò

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/
Cédric Damioli
2012-11-22 13:15:57 UTC
Permalink
Post by Francesco Chicchiriccò
Post by Sylvain Wallez
I am still around from the olden days and will try to help. However
my time is very limited.
Same for here! I would be happy to help where I can, but have limited time.
That sounds great: with two "old foxes" like you things can only raise
better :-)
I think Cédric would need some help especially with pre-release checks
and issues related to blocks he has never dealt with; Cédric, is this
correct?
You're right, especially for the "Forms" or "Authentication" blocks.
I know Sylvain wrote a big part of the forms block (we were colleagues
at that time), but it was a looooong time ago :)
Post by Francesco Chicchiriccò
Regards.
Regards,
--
Cédric Damioli
Ametys CMS
http://www.ametys.org
http://www.anyware-services.com
Cédric Damioli
2012-11-19 00:35:02 UTC
Permalink
Hi,
Post by Francesco Chicchiriccò
Hi all (but Cédric in particular),
by looking at JIRA [1] it seems that quite a considerable number of
issues have been fixed since 2.1.11 (31) even though some are still
standing (11+2).
Following our recent discussion in another thread, I have some
1. Do you think that the the 13 outstanding issues can be moved to
2.1.13 or there are some that need to be absolutely included in 2.1.12?
3 of them were opened by myself before gaining committership. [1] [2] [3]
I could have closed them already, but was waiting for others' approval.
I don't know if someone has something to say about them ...

The 10 others issues are more than 2 years old

There are also 74 issues with no "fix for" version (29 with a patch
included) but affecting a 2.1.x version

We should maybe ask 2.1 users if there are particular issues they want
to be fixed before cutting a 2.1.12 ?
Post by Francesco Chicchiriccò
2. Is the release process clear to you? If not, who (maybe active in
the past) can provide some hint?
Not really.
I think there was once a page written by Carsten describing the release
process, but I can't find it anymore.
Post by Francesco Chicchiriccò
3. Do you need any help in the release process? If so, who is
available to help? I am, even though I don't remember pretty anything
of C2.1...
Yes please :)
It would be great if 2 or 3 people other than me could try to run unit
tests and run samples.
Almost 5 years after the 2.1.11, I also don't remember all blocks, it
would be great to also have feedbacks from users of some specific blocks.
Post by Francesco Chicchiriccò
4. Considering the questions above, when do you think we can start
releasing 2.1.12?
Depending if we try to gather some feedbacks from devs and users or not,
it could be quite fast, say in the next few days.
But 5 years after, we can afford one or two more weeks if needed :)
Post by Francesco Chicchiriccò
Thanks for info.
Regards.
[1]
https://issues.apache.org/jira/browse/COCOON/fixforversion/12312903#selectedTab=com.atlassian.jira.plugin.system.project%3Aversion-issues-panel
[1] https://issues.apache.org/jira/browse/COCOON-2288
[2] https://issues.apache.org/jira/browse/COCOON-2313
[3] https://issues.apache.org/jira/browse/COCOON-2314

Best regards,
--
Cédric Damioli
Ametys CMS
http://www.ametys.org
http://www.anyware-services.com
David Crossley
2012-11-27 07:18:12 UTC
Permalink
In the past releases of Cocoon-2.1, we included the relevant versions
of all supporting product dependencies. That is okay as a convenience.

However we need to provide a source code package which does not contain
those external JAR files, and conduct our release vote against that package.
Then we can construct other convenience packages for distribution.

Forrest got into the same situation. Here is some background and
links to other discussion:
http://s.apache.org/mCW
We solved the immediate situation but still need to adjust our build system.

The Cocoon-2.1 Apache Ant build system should be reasonably easy to tweak
to create separate packages.

-David
Francesco Chicchiriccò
2012-11-27 07:40:18 UTC
Permalink
Post by David Crossley
In the past releases of Cocoon-2.1, we included the relevant versions
of all supporting product dependencies. That is okay as a convenience.
However we need to provide a source code package which does not contain
those external JAR files, and conduct our release vote against that package.
Then we can construct other convenience packages for distribution.
Forrest got into the same situation. Here is some background and
http://s.apache.org/mCW
We solved the immediate situation but still need to adjust our build system.
The Cocoon-2.1 Apache Ant build system should be reasonably easy to tweak
to create separate packages.
Hi David,
I've been involved in similar discussions a while ago and I completely
agree with you.

I've opened OCOON-2330 for tracking this: who is available to help?

Regards.
--
Francesco Chicchiriccò

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/
Cédric Damioli
2012-11-27 11:52:43 UTC
Permalink
Post by Francesco Chicchiriccò
Post by David Crossley
In the past releases of Cocoon-2.1, we included the relevant versions
of all supporting product dependencies. That is okay as a convenience.
However we need to provide a source code package which does not contain
those external JAR files, and conduct our release vote against that package.
Then we can construct other convenience packages for distribution.
Forrest got into the same situation. Here is some background and
http://s.apache.org/mCW
We solved the immediate situation but still need to adjust our build system.
The Cocoon-2.1 Apache Ant build system should be reasonably easy to tweak
to create separate packages.
Hi David,
I've been involved in similar discussions a while ago and I completely
agree with you.
I've opened OCOON-2330 for tracking this: who is available to help?
I do
I'll try to modify ant tasks to separate ZIP files
What we have to do is to know exactly which files are Cocoon sources and
which are not

Best regards,
--
Cédric Damioli
Ametys CMS
http://www.ametys.org
http://www.anyware-services.com
Cédric Damioli
2012-11-29 19:50:45 UTC
Permalink
Hi,

I've slightly modified the build files in order to separate libs from
sources.
I've uploaded
http://people.apache.org/~cdamioli/cocoon-2.1.12-rc-src.zip and
http://people.apache.org/~cdamioli/cocoon-2.1.12-rc-deps.zip
to get your comments.

Does these archives correspond to Apache policy ?

Thanks for your feedbacks,

Regards,
Cédric
Post by Cédric Damioli
Post by Francesco Chicchiriccò
Post by David Crossley
In the past releases of Cocoon-2.1, we included the relevant versions
of all supporting product dependencies. That is okay as a convenience.
However we need to provide a source code package which does not contain
those external JAR files, and conduct our release vote against that package.
Then we can construct other convenience packages for distribution.
Forrest got into the same situation. Here is some background and
http://s.apache.org/mCW
We solved the immediate situation but still need to adjust our build system.
The Cocoon-2.1 Apache Ant build system should be reasonably easy to tweak
to create separate packages.
Hi David,
I've been involved in similar discussions a while ago and I
completely agree with you.
I've opened OCOON-2330 for tracking this: who is available to help?
I do
I'll try to modify ant tasks to separate ZIP files
What we have to do is to know exactly which files are Cocoon sources
and which are not
Best regards,
--
Cédric Damioli
Ametys CMS
http://www.ametys.org
http://www.anyware-services.com
David Crossley
2012-12-07 07:14:46 UTC
Permalink
I spent some time to attempt to upgrade the guts of Forrest
to utilise today's Cocoon-2.1.12-dev version.

https://issues.apache.org/jira/browse/FOR-1240

Hooray, it works.

As explained there it would also be good to upgrade some of the
supporting products dependencies in Cocoon. Forrest has some that
are newer than Cocoon and vice versa. We probably each have some
that are out-of-date.

-David
Francesco Chicchiriccò
2012-12-07 07:44:04 UTC
Permalink
Post by David Crossley
I spent some time to attempt to upgrade the guts of Forrest
to utilise today's Cocoon-2.1.12-dev version.
https://issues.apache.org/jira/browse/FOR-1240
Hooray, it works.
That's very good news!
Post by David Crossley
As explained there it would also be good to upgrade some of the
supporting products dependencies in Cocoon. Forrest has some that
are newer than Cocoon and vice versa. We probably each have some
that are out-of-date.
It makes sense: would you like to open an issue for this?

To summarize, what's missing now to release 2.1.12?
Thanks.

Regards.
--
Francesco Chicchiriccò

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/
David Crossley
2012-12-08 03:18:21 UTC
Permalink
Post by Francesco Chicchiriccò
Post by David Crossley
As explained there it would also be good to upgrade some of the
supporting products dependencies in Cocoon. Forrest has some that
are newer than Cocoon and vice versa. We probably each have some
that are out-of-date.
It makes sense: would you like to open an issue for this?
https://issues.apache.org/jira/browse/COCOON-2333
C-2.1: upgrade some supporting product dependencies

That links to a list in SVN at:
https://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/misc/notes/review-jars.txt

Would developers and users please add notes for any jars
that would be necessary or worthwhile to upgrade.

-David
Francesco Chicchiriccò
2012-12-11 10:46:26 UTC
Permalink
Post by Francesco Chicchiriccò
Post by David Crossley
I spent some time to attempt to upgrade the guts of Forrest
to utilise today's Cocoon-2.1.12-dev version.
https://issues.apache.org/jira/browse/FOR-1240
Hooray, it works.
That's very good news!
Post by David Crossley
As explained there it would also be good to upgrade some of the
supporting products dependencies in Cocoon. Forrest has some that
are newer than Cocoon and vice versa. We probably each have some
that are out-of-date.
It makes sense: would you like to open an issue for this?
To summarize, what's missing now to release 2.1.12?
Hi all,
is everything tracked into JIRA [1]?

If so, we are only 3 issues away from releasing 2.1.12, wonderful!

Regards.

[1]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20COCOON%20AND%20fixVersion%20%3D%20%222.1.12-dev%20(Current%20SVN)%22%20AND%20status%20in%20(Open%2C%20Reopened)%20ORDER%20BY%20priority%20DESC
--
Francesco Chicchiriccò

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/
Cédric Damioli
2012-12-11 11:29:41 UTC
Permalink
Hi,
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
Post by David Crossley
I spent some time to attempt to upgrade the guts of Forrest
to utilise today's Cocoon-2.1.12-dev version.
https://issues.apache.org/jira/browse/FOR-1240
Hooray, it works.
That's very good news!
Post by David Crossley
As explained there it would also be good to upgrade some of the
supporting products dependencies in Cocoon. Forrest has some that
are newer than Cocoon and vice versa. We probably each have some
that are out-of-date.
It makes sense: would you like to open an issue for this?
To summarize, what's missing now to release 2.1.12?
Hi all,
is everything tracked into JIRA [1]?
From my POV, yes.
I've added some comments to COCOON-2330. I'm not sure what to include or
exclude from the -src package.
Post by Francesco Chicchiriccò
If so, we are only 3 issues away from releasing 2.1.12, wonderful!
Regards.
[1]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20COCOON%20AND%20fixVersion%20%3D%20%222.1.12-dev%20(Current%20SVN)%22%20AND%20status%20in%20(Open%2C%20Reopened)%20ORDER%20BY%20priority%20DESC
Regards,
--
Cédric Damioli
Ametys CMS
http://www.ametys.org
http://www.anyware-services.com
i***@gmail.com
2012-12-11 16:59:58 UTC
Permalink
Here are some additions to COCOON-2333 (list of current jar files). I'm
also attaching a .txt file in case that's easier to use.

Is the plan to upgrade the code to use the newer jar versions for the
2.12 release?

Thanks,

Dan

==================

Additions to:
https://svn.apache.org/viewvc/cocoon/branches/BRANCH_2_1_X/misc/notes/review-jars.txt?view=markup

Issue: COCOON-2333

Notes: I'm not a developer so functionality/compatibility with cocoon
may not work!



148 L: lib/optional/batik-all-1.6.jar
149 F: C:
150 R: batik-1.7; batik-src-1.7.zip OR batik-1.7.zip
151 http://xmlgraphics.apache.org/batik/



161 L: lib/optional/chaperon-20040205.jar
162 F: C:
163 R: chaperon-3.0; chaperon-3.0-final-src.tar.gz OR
chaperon-3.0-final-bin.tar.gz
http://chaperon.sourceforge.net/



169 L: lib/optional/commons-codec-1.3.jar
170 F: C:
171 R: commons-codec-1.7; commons-codec-1.7-bin.tar.gz OR
commons-codec-1.7-src.tar.gz
https://commons.apache.org/codec/



218 L: lib/optional/fop-0.95.jar
219 F: C:
220 R: fop-1,1; fop-1.1-src.tar.gz OR fop-1.1-bin.tar.gz
https://xmlgraphics.apache.org/fop/1.1/



247 L: lib/optional/icu4j-2.8.jar
248 F: X:
249 R: icu4j-50_1; icu4j-50_1.tgz, icu4j-charset-50_1.jar,
icu4j-localespi-50_1.jar
https://ssl.icu-project.org/icu-jsp/downloadPage.jsp?ver=50.1&base=j&svn=release-50-1
http://site.icu-project.org/



251 L: lib/optional/itext-1.1.jar
252 F: X:
253 R: itext-5.3.4; itext-5.3.4.zip
http://itextpdf.com/,
http://sourceforge.net/projects/itext/files/iText/iText5.3.4/



299 L: lib/optional/jtidy-04aug2000r7-dev.jar
300 F: C:
301 R: jtidy-r938; jtidy-r938.zip OR jtidy-r938-sources.zip
http://jtidy.sourceforge.net/
(http://sourceforge.net/projects/jtidy/files/JTidy/r938/)



303 L: lib/optional/lucene-1.4.3.jar
304 F: C:
305 R: lucene-4.0.0; lucene-4.0.0-src.tgz OR lucene-4.0.0.tgz
https://lucene.apache.org/
See also the SOLR Project (https://lucene.apache.org/solr/, now v4)



317 L: lib/optional/nekohtml-0.9.5.jar
318 F: X:
319 R: nekohtml-1.9.17; nekohtml-1.9.17.tar.gz OR nekohtml-1.9.17.zip
http://nekohtml.sourceforge.net/



329 L: lib/optional/poi-3.0.2-FINAL-20080204.jar
330 F: X:
331 R: poi-3.9; poi-bin-3.9-20121203.tar.gz OR
poi-src-3.9-20121203.tar.gz
https://poi.apache.org/
Notes: See also, alternative TIKA Project (tika.apache.org); Current
SOLR v4 distro uses poi-3.8.jar, poi-ooxml-3.8.jar,
poi-ooxml-schemas-3.8.jar and poi-scratchpad-3.8.jar



365 L: lib/optional/velocity-1.4.jar
366 F: X:
367 R: velocity-1.7; velocity-1.7.tar.gz
https://velocity.apache.org/



393 L: lib/optional/xmlgraphics-commons-1.3.1.jar
394 F: C:
395 R: xmlgraphics-commons-1.5; xmlgraphics-commons-1.5-bin.tar.gz
OR xmlgraphics-commons-1.5-src.tar.gz
https://xmlgraphics.apache.org/commons/
David Crossley
2012-12-12 04:12:59 UTC
Permalink
Post by i***@gmail.com
Here are some additions to COCOON-2333 (list of current jar files). I'm
also attaching a .txt file in case that's easier to use.
Is the plan to upgrade the code to use the newer jar versions for the
2.12 release?
Thanks, i will add some of your notes to the list.

The intention was to gather some information about some of the
important ones. If necessary or desirable, then we could possibly
upgrade some. However there would need to be other Cocoon
committers to assist with that.

IIUC, then Cocoon-2.1 will need to remain at a limited
low version of Java. So that will restrict which jars can
be upgraded, and to what version of their product.

-David
Post by i***@gmail.com
Thanks,
Dan
Francesco Chicchiriccò
2012-12-12 08:33:03 UTC
Permalink
Here are some additions to COCOON-2333 (list of current jar files). I'm also attaching a .txt file in case that's easier to use.
Is the plan to upgrade the code to use the newer jar versions for the 2.12 release?
Thanks, I will add some of your notes to the list.
The intention was to gather some information about some of the important ones. If necessary or desirable, then we could possibly upgrade some. However there would need to be other Cocoon committers to assist with that.
If you can point me to some procedure to test whether everything is
working (if it was Maven I would have known how to do this check) when
upgrading some JAR dependency file, I could provide some assistance.
IIUC, then Cocoon-2.1 will need to remain at a limited low version of Java. So that will restrict which jars can
be upgraded, and to what version of their product.
Agreed: 2.1.12 is a bugfix version - coming after years! - and its scope
could not interfere with Java version.

Regards.
--
Francesco Chicchiriccò

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/
David Crossley
2012-12-12 12:13:22 UTC
Permalink
Post by Francesco Chicchiriccò
Post by i***@gmail.com
Here are some additions to COCOON-2333 (list of current jar files). I'm
also attaching a .txt file in case that's easier to use.
Is the plan to upgrade the code to use the newer jar versions for the 2.12 release?
Thanks, I will add some of your notes to the list.
The intention was to gather some information about some of the important
ones. If necessary or desirable, then we could possibly upgrade some.
However there would need to be other Cocoon committers to assist with that.
If you can point me to some procedure to test whether everything is
working (if it was Maven I would have known how to do this check) when
upgrading some JAR dependency file, I could provide some assistance.
The lib/jars.xml file explains where each jar is used, e.g. which block,
or perhaps core too. So doing ./build.sh to compile and run whatever
code tests are included, then ./cocoon.sh and exercise the relevant Sample.
Post by Francesco Chicchiriccò
IIUC, then Cocoon-2.1 will need to remain at a limited low version of
Java. So that will restrict which jars can
be upgraded, and to what version of their product.
Agreed: 2.1.12 is a bugfix version - coming after years! - and its scope
could not interfere with Java version.
The Cocoon-2.1 README.txt says Java 1.3

However for example this is already in our C-2.1 SVN:
lib/optional/xmlgraphics-commons-1.3.1.jar
and version 1.3 is the first to require Java 1.4
http://xmlgraphics.apache.org/commons/#news-2008-06-11

-David
Cédric Damioli
2012-12-12 12:56:43 UTC
Permalink
Post by David Crossley
Post by Francesco Chicchiriccò
Post by i***@gmail.com
Here are some additions to COCOON-2333 (list of current jar files). I'm
also attaching a .txt file in case that's easier to use.
Is the plan to upgrade the code to use the newer jar versions for the 2.12 release?
Thanks, I will add some of your notes to the list.
The intention was to gather some information about some of the important
ones. If necessary or desirable, then we could possibly upgrade some.
However there would need to be other Cocoon committers to assist with that.
If you can point me to some procedure to test whether everything is
working (if it was Maven I would have known how to do this check) when
upgrading some JAR dependency file, I could provide some assistance.
The lib/jars.xml file explains where each jar is used, e.g. which block,
or perhaps core too. So doing ./build.sh to compile and run whatever
code tests are included, then ./cocoon.sh and exercise the relevant Sample.
Post by Francesco Chicchiriccò
IIUC, then Cocoon-2.1 will need to remain at a limited low version of
Java. So that will restrict which jars can
be upgraded, and to what version of their product.
Agreed: 2.1.12 is a bugfix version - coming after years! - and its scope
could not interfere with Java version.
The Cocoon-2.1 README.txt says Java 1.3
lib/optional/xmlgraphics-commons-1.3.1.jar
and version 1.3 is the first to require Java 1.4
http://xmlgraphics.apache.org/commons/#news-2008-06-11
-David
If I remember correctly, it was decided that 2.1.12 would be the first
version requiring at least a 1.4 JVM
This is written in the status.xml and even the core does not compile
with a JVM < 1.4
We should certainly update the README.txt
--
Cédric Damioli
Ametys CMS
http://www.ametys.org
http://www.anyware-services.com
Francesco Chicchiriccò
2013-01-19 14:11:44 UTC
Permalink
Post by Cédric Damioli
[...]
Post by Francesco Chicchiriccò
Hi all,
is everything tracked into JIRA [1]?
From my POV, yes.
I've added some comments to COCOON-2330. I'm not sure what to include
or exclude from the -src package.
Post by Francesco Chicchiriccò
If so, we are only 3 issues away from releasing 2.1.12, wonderful!
Hello there,
how's the situation with C2.1.12 in 2013? Any help needed?

Regards.
Post by Cédric Damioli
Post by Francesco Chicchiriccò
[1]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20COCOON%20AND%20fixVersion%20%3D%20%222.1.12-dev%20(Current%20SVN)%22%20AND%20status%20in%20(Open%2C%20Reopened)%20ORDER%20BY%20priority%20DESC
--
Francesco Chicchiriccò

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/
Cédric Damioli
2013-01-19 16:19:38 UTC
Permalink
Hi there,

AFAIK the same 3 issues are still opened. Could you give me a hint about
the src/bin split?
Apart, there's the David issue about upgrading all dependencies. I don't
know the status of it.
And also an samples issue reopened by David. I don't know either what to
do with it.

Regards,
Cédric
Post by Francesco Chicchiriccò
Post by Cédric Damioli
[...]
Post by Francesco Chicchiriccò
Hi all,
is everything tracked into JIRA [1]?
From my POV, yes.
I've added some comments to COCOON-2330. I'm not sure what to include
or exclude from the -src package.
Post by Francesco Chicchiriccò
If so, we are only 3 issues away from releasing 2.1.12, wonderful!
Hello there,
how's the situation with C2.1.12 in 2013? Any help needed?
Regards.
Post by Cédric Damioli
Post by Francesco Chicchiriccò
[1]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20COCOON%20AND%20fixVersion%20%3D%20%222.1.12-dev%20(Current%20SVN)%22%20AND%20status%20in%20(Open%2C%20Reopened)%20ORDER%20BY%20priority%20DESC
--
Cédric Damioli
Ametys CMS
http://www.ametys.org
http://www.anyware-services.com
Francesco Chicchiriccò
2013-01-20 15:41:56 UTC
Permalink
Post by Cédric Damioli
Hi there,
AFAIK the same 3 issues are still opened. Could you give me a hint
about the src/bin split?
COCOON-2330 - Could you please tell me (again) how to generate the
source and deps packages from SVN? Thanks.
Post by Cédric Damioli
Apart, there's the David issue about upgrading all dependencies. I
don't know the status of it.
COCOON-2333 - According to [2], there are still few deps to check. I
remember I've asked David about how to contribute on this an he said
something like "update the JAR file an browse if samples still work"
Post by Cédric Damioli
And also an samples issue reopened by David. I don't know either what
to do with it.
COCOON-2069 - David, what should we do with this?

Regards.
Post by Cédric Damioli
Post by Francesco Chicchiriccò
Post by Cédric Damioli
[...]
Post by Francesco Chicchiriccò
Hi all,
is everything tracked into JIRA [1]?
From my POV, yes.
I've added some comments to COCOON-2330. I'm not sure what to
include or exclude from the -src package.
Post by Francesco Chicchiriccò
If so, we are only 3 issues away from releasing 2.1.12, wonderful!
Hello there,
how's the situation with C2.1.12 in 2013? Any help needed?
Regards.
Post by Cédric Damioli
Post by Francesco Chicchiriccò
[1]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20COCOON%20AND%20fixVersion%20%3D%20%222.1.12-dev%20(Current%20SVN)%22%20AND%20status%20in%20(Open%2C%20Reopened)%20ORDER%20BY%20priority%20DESC
[2]
http://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/misc/notes/review-jars.txt
--
Francesco Chicchiriccò

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/
David Crossley
2013-01-22 06:26:51 UTC
Permalink
Post by Francesco Chicchiriccò
Post by Cédric Damioli
Hi there,
AFAIK the same 3 issues are still opened. Could you give me a hint
about the src/bin split?
COCOON-2330 - Could you please tell me (again) how to generate the
source and deps packages from SVN? Thanks.
Do "./build.sh dist".

There will also need to be different NOTICE and LICENSE
files for each package.
Post by Francesco Chicchiriccò
Post by Cédric Damioli
Apart, there's the David issue about upgrading all dependencies. I
don't know the status of it.
COCOON-2333 - According to [2], there are still few deps to check. I
remember I've asked David about how to contribute on this an he said
something like "update the JAR file an browse if samples still work"
See a few messages above on this list. There is more to it
than that, e.g. tweak lib/jars.xml file, do the build (which does
have some code tests), review the relevant samples, etc.

Also the issue is about "some" dependencies, not "all".
For example FOP, Batik, etc. would be good if possible.
Post by Francesco Chicchiriccò
Post by Cédric Damioli
And also an samples issue reopened by David. I don't know either what
to do with it.
COCOON-2069 - David, what should we do with this?
See my issue comment. I made a workaround to fix the cause
of the new misconfiguration which had broken the build for
everyone. It seems that the original patch must have included
some parts of some extra stuff (WSRP). I reckon forget it and
just leave the workaround in-place.

-David
Post by Francesco Chicchiriccò
Regards.
Post by Cédric Damioli
Post by Francesco Chicchiriccò
Post by Cédric Damioli
[...]
Post by Francesco Chicchiriccò
Hi all,
is everything tracked into JIRA [1]?
From my POV, yes.
I've added some comments to COCOON-2330. I'm not sure what to
include or exclude from the -src package.
Post by Francesco Chicchiriccò
If so, we are only 3 issues away from releasing 2.1.12, wonderful!
Hello there,
how's the situation with C2.1.12 in 2013? Any help needed?
Regards.
Post by Cédric Damioli
Post by Francesco Chicchiriccò
[1]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20COCOON%20AND%20fixVersion%20%3D%20%222.1.12-dev%20(Current%20SVN)%22%20AND%20status%20in%20(Open%2C%20Reopened)%20ORDER%20BY%20priority%20DESC
[2]
http://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/misc/notes/review-jars.txt
--
Francesco Chicchiriccò
ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/
Francesco Chicchiriccò
2013-01-22 10:40:14 UTC
Permalink
Post by David Crossley
Post by Francesco Chicchiriccò
Post by Cédric Damioli
Hi there,
AFAIK the same 3 issues are still opened. Could you give me a hint
about the src/bin split?
COCOON-2330 - Could you please tell me (again) how to generate the
source and deps packages from SVN? Thanks.
Do "./build.sh dist".
There will also need to be different NOTICE and LICENSE
files for each package.
Adding this as comment to COCOON-2330 - let's move this discussion there.
Post by David Crossley
Post by Francesco Chicchiriccò
Post by Cédric Damioli
Apart, there's the David issue about upgrading all dependencies. I
don't know the status of it.
COCOON-2333 - According to [2], there are still few deps to check. I
remember I've asked David about how to contribute on this an he said
something like "update the JAR file an browse if samples still work"
See a few messages above on this list. There is more to it
than that, e.g. tweak lib/jars.xml file, do the build (which does
have some code tests), review the relevant samples, etc.
Also the issue is about "some" dependencies, not "all".
For example FOP, Batik, etc. would be good if possible.
Fine, I think I've found again such information at [3]; added this also
as comment to COCOON-2333 - let's move this discussion there.
Post by David Crossley
Post by Francesco Chicchiriccò
Post by Cédric Damioli
And also an samples issue reopened by David. I don't know either what
to do with it.
COCOON-2069 - David, what should we do with this?
See my issue comment. I made a workaround to fix the cause
of the new misconfiguration which had broken the build for
everyone. It seems that the original patch must have included
some parts of some extra stuff (WSRP). I reckon forget it and
just leave the workaround in-place.
I've read your comment in COCOON-2069 and replied there recently: could
you please take a look and reply? Thanks.

Regards.
Post by David Crossley
Post by Francesco Chicchiriccò
Post by Cédric Damioli
Post by Francesco Chicchiriccò
Post by Cédric Damioli
[...]
Post by Francesco Chicchiriccò
Hi all,
is everything tracked into JIRA [1]?
From my POV, yes.
I've added some comments to COCOON-2330. I'm not sure what to
include or exclude from the -src package.
Post by Francesco Chicchiriccò
If so, we are only 3 issues away from releasing 2.1.12, wonderful!
Hello there,
how's the situation with C2.1.12 in 2013? Any help needed?
Regards.
Post by Cédric Damioli
Post by Francesco Chicchiriccò
[1]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20COCOON%20AND%20fixVersion%20%3D%20%222.1.12-dev%20(Current%20SVN)%22%20AND%20status%20in%20(Open%2C%20Reopened)%20ORDER%20BY%20priority%20DESC
[2] http://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/misc/notes/review-jars.txt
[3]
http://markmail.org/message/ijmy6nzd2k4yzghn#query:+page:1+mid:dbsylujycgit224q+state:results
--
Francesco Chicchiriccò

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/
Cédric Damioli
2013-02-27 21:55:14 UTC
Permalink
Hi all,

It seems there remains only one open issue, COCOON-2333, related to
dependencies upgrade.
David, Francesco, others, are we ok with current dependencies ?
Some dependencies are obviously not on their latest versions, but IMHO,
trying to upgrade all jars would be too long, and users may still
upgrade one library if needed. What do you think ?

Best regards,
Cédric
Post by Francesco Chicchiriccò
Post by David Crossley
Post by Francesco Chicchiriccò
Post by Cédric Damioli
Hi there,
AFAIK the same 3 issues are still opened. Could you give me a hint
about the src/bin split?
COCOON-2330 - Could you please tell me (again) how to generate the
source and deps packages from SVN? Thanks.
Do "./build.sh dist".
There will also need to be different NOTICE and LICENSE
files for each package.
Adding this as comment to COCOON-2330 - let's move this discussion there.
Post by David Crossley
Post by Francesco Chicchiriccò
Post by Cédric Damioli
Apart, there's the David issue about upgrading all dependencies. I
don't know the status of it.
COCOON-2333 - According to [2], there are still few deps to check. I
remember I've asked David about how to contribute on this an he said
something like "update the JAR file an browse if samples still work"
See a few messages above on this list. There is more to it
than that, e.g. tweak lib/jars.xml file, do the build (which does
have some code tests), review the relevant samples, etc.
Also the issue is about "some" dependencies, not "all".
For example FOP, Batik, etc. would be good if possible.
Fine, I think I've found again such information at [3]; added this
also as comment to COCOON-2333 - let's move this discussion there.
Post by David Crossley
Post by Francesco Chicchiriccò
Post by Cédric Damioli
And also an samples issue reopened by David. I don't know either what
to do with it.
COCOON-2069 - David, what should we do with this?
See my issue comment. I made a workaround to fix the cause
of the new misconfiguration which had broken the build for
everyone. It seems that the original patch must have included
some parts of some extra stuff (WSRP). I reckon forget it and
just leave the workaround in-place.
could you please take a look and reply? Thanks.
Regards.
Post by David Crossley
Post by Francesco Chicchiriccò
Post by Cédric Damioli
Post by Francesco Chicchiriccò
Post by Cédric Damioli
[...]
Post by Francesco Chicchiriccò
Hi all,
is everything tracked into JIRA [1]?
From my POV, yes.
I've added some comments to COCOON-2330. I'm not sure what to
include or exclude from the -src package.
Post by Francesco Chicchiriccò
If so, we are only 3 issues away from releasing 2.1.12, wonderful!
Hello there,
how's the situation with C2.1.12 in 2013? Any help needed?
Regards.
Post by Cédric Damioli
Post by Francesco Chicchiriccò
[1]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20COCOON%20AND%20fixVersion%20%3D%20%222.1.12-dev%20(Current%20SVN)%22%20AND%20status%20in%20(Open%2C%20Reopened)%20ORDER%20BY%20priority%20DESC
[2]
http://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/misc/notes/review-jars.txt
[3]
http://markmail.org/message/ijmy6nzd2k4yzghn#query:+page:1+mid:dbsylujycgit224q+state:results
Francesco Chicchiriccò
2013-02-28 09:04:06 UTC
Permalink
Post by Francesco Chicchiriccò
Hi all,
It seems there remains only one open issue, COCOON-2333, related to
dependencies upgrade.
With r1451136 I have enabled the generation of .md5 and .sha1 for dist
packages, required by [4]: please check it to confirm that it is working
correctly.
The .asc files will also need to be generated, but I haven't found an
easy way to to this via ANT, hence I guess we have no option but the
manual way, e.g.

$ gpg --armor --output cocoon-2.1.12-src.zip.asc --detach-sig
cocoon-2.1.12-src.zip
$ gpg --armor --output cocoon-2.1.12-src.tar.gz.asc --detach-sig
cocoon-2.1.12-src.tar.gz
$ gpg --armor --output cocoon-2.1.12-deps.zip.asc --detach-sig
cocoon-2.1.12-deps.zip
$ gpg --armor --output cocoon-2.1.12-deps.tar.gz.asc --detach-sig
cocoon-2.1.12-deps.tar.gz

I urge to note that the release manager for 2.1.12 will also need to be
sure that his own key is contained in [5].
Post by Francesco Chicchiriccò
David, Francesco, others, are we ok with current dependencies?
Some dependencies are obviously not on their latest versions, but
IMHO, trying to upgrade all jars would be too long, and users may
still upgrade one library if needed. What do you think?
We have recently turned all the "To be done" statements from [6] into
"Done", hence If no specific limitations and / or bugs are known
affecting the current versions of dependencies, I see no reason for keep
waiting.

I'd create the release 2.1.13 on JIRA, move COCOON-2333 there and start
the release process for 2.1.12.

Regards.
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
Post by David Crossley
Post by Francesco Chicchiriccò
Post by Cédric Damioli
Hi there,
AFAIK the same 3 issues are still opened. Could you give me a hint
about the src/bin split?
COCOON-2330 - Could you please tell me (again) how to generate the
source and deps packages from SVN? Thanks.
Do "./build.sh dist".
There will also need to be different NOTICE and LICENSE
files for each package.
Adding this as comment to COCOON-2330 - let's move this discussion there.
Post by David Crossley
Post by Francesco Chicchiriccò
Post by Cédric Damioli
Apart, there's the David issue about upgrading all dependencies. I
don't know the status of it.
COCOON-2333 - According to [2], there are still few deps to check. I
remember I've asked David about how to contribute on this an he said
something like "update the JAR file an browse if samples still work"
See a few messages above on this list. There is more to it
than that, e.g. tweak lib/jars.xml file, do the build (which does
have some code tests), review the relevant samples, etc.
Also the issue is about "some" dependencies, not "all".
For example FOP, Batik, etc. would be good if possible.
Fine, I think I've found again such information at [3]; added this
also as comment to COCOON-2333 - let's move this discussion there.
Post by David Crossley
Post by Francesco Chicchiriccò
Post by Cédric Damioli
And also an samples issue reopened by David. I don't know either what
to do with it.
COCOON-2069 - David, what should we do with this?
See my issue comment. I made a workaround to fix the cause
of the new misconfiguration which had broken the build for
everyone. It seems that the original patch must have included
some parts of some extra stuff (WSRP). I reckon forget it and
just leave the workaround in-place.
could you please take a look and reply? Thanks.
Regards.
Post by David Crossley
Post by Francesco Chicchiriccò
Post by Cédric Damioli
Post by Francesco Chicchiriccò
Post by Cédric Damioli
[...]
Post by Francesco Chicchiriccò
Hi all,
is everything tracked into JIRA [1]?
From my POV, yes.
I've added some comments to COCOON-2330. I'm not sure what to
include or exclude from the -src package.
Post by Francesco Chicchiriccò
If so, we are only 3 issues away from releasing 2.1.12, wonderful!
Hello there,
how's the situation with C2.1.12 in 2013? Any help needed?
Regards.
Post by Cédric Damioli
Post by Francesco Chicchiriccò
[1]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20COCOON%20AND%20fixVersion%20%3D%20%222.1.12-dev%20(Current%20SVN)%22%20AND%20status%20in%20(Open%2C%20Reopened)%20ORDER%20BY%20priority%20DESC
[2]
http://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/misc/notes/review-jars.txt
[3]
http://markmail.org/message/ijmy6nzd2k4yzghn#query:+page:1+mid:dbsylujycgit224q+state:results
[4] http://www.apache.org/dev/release-signing.html
[5] http://www.apache.org/dist/cocoon/KEYS
[6]
http://svn.apache.org/viewvc/cocoon/branches/BRANCH_2_1_X/misc/notes/review-jars.txt
--
Francesco Chicchiriccò

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/
Cédric Damioli
2013-02-28 10:22:44 UTC
Permalink
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
Hi all,
It seems there remains only one open issue, COCOON-2333, related to
dependencies upgrade.
With r1451136 I have enabled the generation of .md5 and .sha1 for dist
packages, required by [4]: please check it to confirm that it is
working correctly.
The .asc files will also need to be generated, but I haven't found an
easy way to to this via ANT, hence I guess we have no option but the
manual way, e.g.
$ gpg --armor --output cocoon-2.1.12-src.zip.asc --detach-sig
cocoon-2.1.12-src.zip
$ gpg --armor --output cocoon-2.1.12-src.tar.gz.asc --detach-sig
cocoon-2.1.12-src.tar.gz
$ gpg --armor --output cocoon-2.1.12-deps.zip.asc --detach-sig
cocoon-2.1.12-deps.zip
$ gpg --armor --output cocoon-2.1.12-deps.tar.gz.asc --detach-sig
cocoon-2.1.12-deps.tar.gz
I urge to note that the release manager for 2.1.12 will also need to
be sure that his own key is contained in [5].
BTW, who is actually the release manager for 2.1.12 ?
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
David, Francesco, others, are we ok with current dependencies?
Some dependencies are obviously not on their latest versions, but
IMHO, trying to upgrade all jars would be too long, and users may
still upgrade one library if needed. What do you think?
We have recently turned all the "To be done" statements from [6] into
"Done", hence If no specific limitations and / or bugs are known
affecting the current versions of dependencies, I see no reason for
keep waiting.
I've made a very quick tour on samples and all seemed to work nice.
I'll look at them deeper once we have a release candidate.
Post by Francesco Chicchiriccò
I'd create the release 2.1.13 on JIRA, move COCOON-2333 there and
start the release process for 2.1.12.
+1
It'll be part of the release process.

Cédric
Post by Francesco Chicchiriccò
Regards.
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
Post by David Crossley
Post by Francesco Chicchiriccò
Post by Cédric Damioli
Hi there,
AFAIK the same 3 issues are still opened. Could you give me a hint
about the src/bin split?
COCOON-2330 - Could you please tell me (again) how to generate the
source and deps packages from SVN? Thanks.
Do "./build.sh dist".
There will also need to be different NOTICE and LICENSE
files for each package.
Adding this as comment to COCOON-2330 - let's move this discussion there.
Post by David Crossley
Post by Francesco Chicchiriccò
Post by Cédric Damioli
Apart, there's the David issue about upgrading all dependencies. I
don't know the status of it.
COCOON-2333 - According to [2], there are still few deps to check. I
remember I've asked David about how to contribute on this an he said
something like "update the JAR file an browse if samples still work"
See a few messages above on this list. There is more to it
than that, e.g. tweak lib/jars.xml file, do the build (which does
have some code tests), review the relevant samples, etc.
Also the issue is about "some" dependencies, not "all".
For example FOP, Batik, etc. would be good if possible.
Fine, I think I've found again such information at [3]; added this
also as comment to COCOON-2333 - let's move this discussion there.
Post by David Crossley
Post by Francesco Chicchiriccò
Post by Cédric Damioli
And also an samples issue reopened by David. I don't know either what
to do with it.
COCOON-2069 - David, what should we do with this?
See my issue comment. I made a workaround to fix the cause
of the new misconfiguration which had broken the build for
everyone. It seems that the original patch must have included
some parts of some extra stuff (WSRP). I reckon forget it and
just leave the workaround in-place.
could you please take a look and reply? Thanks.
Regards.
Post by David Crossley
Post by Francesco Chicchiriccò
Post by Cédric Damioli
Post by Francesco Chicchiriccò
Post by Cédric Damioli
[...]
Post by Francesco Chicchiriccò
Hi all,
is everything tracked into JIRA [1]?
From my POV, yes.
I've added some comments to COCOON-2330. I'm not sure what to
include or exclude from the -src package.
Post by Francesco Chicchiriccò
If so, we are only 3 issues away from releasing 2.1.12, wonderful!
Hello there,
how's the situation with C2.1.12 in 2013? Any help needed?
Regards.
Post by Cédric Damioli
Post by Francesco Chicchiriccò
[1]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20COCOON%20AND%20fixVersion%20%3D%20%222.1.12-dev%20(Current%20SVN)%22%20AND%20status%20in%20(Open%2C%20Reopened)%20ORDER%20BY%20priority%20DESC
[2]
http://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/misc/notes/review-jars.txt
[3]
http://markmail.org/message/ijmy6nzd2k4yzghn#query:+page:1+mid:dbsylujycgit224q+state:results
[4] http://www.apache.org/dev/release-signing.html
[5] http://www.apache.org/dist/cocoon/KEYS
[6]
http://svn.apache.org/viewvc/cocoon/branches/BRANCH_2_1_X/misc/notes/review-jars.txt
--
Cédric Damioli
Ametys CMS
http://www.ametys.org
http://www.anyware-services.com
Francesco Chicchiriccò
2013-02-28 10:26:20 UTC
Permalink
Post by Cédric Damioli
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
Hi all,
It seems there remains only one open issue, COCOON-2333, related to
dependencies upgrade.
With r1451136 I have enabled the generation of .md5 and .sha1 for
dist packages, required by [4]: please check it to confirm that it is
working correctly.
The .asc files will also need to be generated, but I haven't found an
easy way to to this via ANT, hence I guess we have no option but the
manual way, e.g.
$ gpg --armor --output cocoon-2.1.12-src.zip.asc --detach-sig
cocoon-2.1.12-src.zip
$ gpg --armor --output cocoon-2.1.12-src.tar.gz.asc --detach-sig
cocoon-2.1.12-src.tar.gz
$ gpg --armor --output cocoon-2.1.12-deps.zip.asc --detach-sig
cocoon-2.1.12-deps.zip
$ gpg --armor --output cocoon-2.1.12-deps.tar.gz.asc --detach-sig
cocoon-2.1.12-deps.tar.gz
I urge to note that the release manager for 2.1.12 will also need to
be sure that his own key is contained in [5].
BTW, who is actually the release manager for 2.1.12 ?
Whoever wants to take this up: I was assuming you, actually ;-)
Having some experience with releases (Maven-driven, actually...) I can
help, if you want / need.
Post by Cédric Damioli
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
David, Francesco, others, are we ok with current dependencies?
Some dependencies are obviously not on their latest versions, but
IMHO, trying to upgrade all jars would be too long, and users may
still upgrade one library if needed. What do you think?
We have recently turned all the "To be done" statements from [6] into
"Done", hence If no specific limitations and / or bugs are known
affecting the current versions of dependencies, I see no reason for
keep waiting.
I've made a very quick tour on samples and all seemed to work nice.
I'll look at them deeper once we have a release candidate.
Fine.
Post by Cédric Damioli
Post by Francesco Chicchiriccò
I'd create the release 2.1.13 on JIRA, move COCOON-2333 there and
start the release process for 2.1.12.
+1
It'll be part of the release process.
Fine again.

Regards.
Post by Cédric Damioli
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
Post by David Crossley
Post by Francesco Chicchiriccò
Post by Cédric Damioli
Hi there,
AFAIK the same 3 issues are still opened. Could you give me a hint
about the src/bin split?
COCOON-2330 - Could you please tell me (again) how to generate the
source and deps packages from SVN? Thanks.
Do "./build.sh dist".
There will also need to be different NOTICE and LICENSE
files for each package.
Adding this as comment to COCOON-2330 - let's move this discussion there.
Post by David Crossley
Post by Francesco Chicchiriccò
Post by Cédric Damioli
Apart, there's the David issue about upgrading all dependencies. I
don't know the status of it.
COCOON-2333 - According to [2], there are still few deps to check. I
remember I've asked David about how to contribute on this an he said
something like "update the JAR file an browse if samples still work"
See a few messages above on this list. There is more to it
than that, e.g. tweak lib/jars.xml file, do the build (which does
have some code tests), review the relevant samples, etc.
Also the issue is about "some" dependencies, not "all".
For example FOP, Batik, etc. would be good if possible.
Fine, I think I've found again such information at [3]; added this
also as comment to COCOON-2333 - let's move this discussion there.
Post by David Crossley
Post by Francesco Chicchiriccò
Post by Cédric Damioli
And also an samples issue reopened by David. I don't know either what
to do with it.
COCOON-2069 - David, what should we do with this?
See my issue comment. I made a workaround to fix the cause
of the new misconfiguration which had broken the build for
everyone. It seems that the original patch must have included
some parts of some extra stuff (WSRP). I reckon forget it and
just leave the workaround in-place.
could you please take a look and reply? Thanks.
Regards.
Post by David Crossley
Post by Francesco Chicchiriccò
Post by Cédric Damioli
Post by Francesco Chicchiriccò
Post by Cédric Damioli
[...]
Post by Francesco Chicchiriccò
Hi all,
is everything tracked into JIRA [1]?
From my POV, yes.
I've added some comments to COCOON-2330. I'm not sure what to
include or exclude from the -src package.
Post by Francesco Chicchiriccò
If so, we are only 3 issues away from releasing 2.1.12, wonderful!
Hello there,
how's the situation with C2.1.12 in 2013? Any help needed?
Regards.
Post by Cédric Damioli
Post by Francesco Chicchiriccò
[1]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20COCOON%20AND%20fixVersion%20%3D%20%222.1.12-dev%20(Current%20SVN)%22%20AND%20status%20in%20(Open%2C%20Reopened)%20ORDER%20BY%20priority%20DESC
[2]
http://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/misc/notes/review-jars.txt
[3]
http://markmail.org/message/ijmy6nzd2k4yzghn#query:+page:1+mid:dbsylujycgit224q+state:results
[4] http://www.apache.org/dev/release-signing.html
[5] http://www.apache.org/dist/cocoon/KEYS
[6]
http://svn.apache.org/viewvc/cocoon/branches/BRANCH_2_1_X/misc/notes/review-jars.txt
--
Francesco Chicchiriccò

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/
Cédric Damioli
2013-02-28 10:44:33 UTC
Permalink
Post by Francesco Chicchiriccò
Post by Cédric Damioli
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
Hi all,
It seems there remains only one open issue, COCOON-2333, related to
dependencies upgrade.
With r1451136 I have enabled the generation of .md5 and .sha1 for
dist packages, required by [4]: please check it to confirm that it
is working correctly.
The .asc files will also need to be generated, but I haven't found
an easy way to to this via ANT, hence I guess we have no option but
the manual way, e.g.
$ gpg --armor --output cocoon-2.1.12-src.zip.asc --detach-sig
cocoon-2.1.12-src.zip
$ gpg --armor --output cocoon-2.1.12-src.tar.gz.asc --detach-sig
cocoon-2.1.12-src.tar.gz
$ gpg --armor --output cocoon-2.1.12-deps.zip.asc --detach-sig
cocoon-2.1.12-deps.zip
$ gpg --armor --output cocoon-2.1.12-deps.tar.gz.asc --detach-sig
cocoon-2.1.12-deps.tar.gz
I urge to note that the release manager for 2.1.12 will also need to
be sure that his own key is contained in [5].
BTW, who is actually the release manager for 2.1.12 ?
Whoever wants to take this up: I was assuming you, actually ;-)
Having some experience with releases (Maven-driven, actually...) I can
help, if you want / need.
I'm ok to do the job, if it's ok for others too ;)
Having never done Apache releases, I'll certainly need help at some
point, but IIRC the whole process was particularly well explained on the
wiki.
Post by Francesco Chicchiriccò
Post by Cédric Damioli
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
David, Francesco, others, are we ok with current dependencies?
Some dependencies are obviously not on their latest versions, but
IMHO, trying to upgrade all jars would be too long, and users may
still upgrade one library if needed. What do you think?
We have recently turned all the "To be done" statements from [6]
into "Done", hence If no specific limitations and / or bugs are
known affecting the current versions of dependencies, I see no
reason for keep waiting.
I've made a very quick tour on samples and all seemed to work nice.
I'll look at them deeper once we have a release candidate.
Fine.
Post by Cédric Damioli
Post by Francesco Chicchiriccò
I'd create the release 2.1.13 on JIRA, move COCOON-2333 there and
start the release process for 2.1.12.
+1
It'll be part of the release process.
Fine again.
Regards.
Post by Cédric Damioli
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
Post by David Crossley
Post by Francesco Chicchiriccò
Post by Cédric Damioli
Hi there,
AFAIK the same 3 issues are still opened. Could you give me a hint
about the src/bin split?
COCOON-2330 - Could you please tell me (again) how to generate the
source and deps packages from SVN? Thanks.
Do "./build.sh dist".
There will also need to be different NOTICE and LICENSE
files for each package.
Adding this as comment to COCOON-2330 - let's move this discussion there.
Post by David Crossley
Post by Francesco Chicchiriccò
Post by Cédric Damioli
Apart, there's the David issue about upgrading all dependencies. I
don't know the status of it.
COCOON-2333 - According to [2], there are still few deps to check. I
remember I've asked David about how to contribute on this an he said
something like "update the JAR file an browse if samples still work"
See a few messages above on this list. There is more to it
than that, e.g. tweak lib/jars.xml file, do the build (which does
have some code tests), review the relevant samples, etc.
Also the issue is about "some" dependencies, not "all".
For example FOP, Batik, etc. would be good if possible.
Fine, I think I've found again such information at [3]; added this
also as comment to COCOON-2333 - let's move this discussion there.
Post by David Crossley
Post by Francesco Chicchiriccò
Post by Cédric Damioli
And also an samples issue reopened by David. I don't know either what
to do with it.
COCOON-2069 - David, what should we do with this?
See my issue comment. I made a workaround to fix the cause
of the new misconfiguration which had broken the build for
everyone. It seems that the original patch must have included
some parts of some extra stuff (WSRP). I reckon forget it and
just leave the workaround in-place.
could you please take a look and reply? Thanks.
Regards.
Post by David Crossley
Post by Francesco Chicchiriccò
Post by Cédric Damioli
Post by Francesco Chicchiriccò
Post by Cédric Damioli
[...]
Post by Francesco Chicchiriccò
Hi all,
is everything tracked into JIRA [1]?
From my POV, yes.
I've added some comments to COCOON-2330. I'm not sure what to
include or exclude from the -src package.
Post by Francesco Chicchiriccò
If so, we are only 3 issues away from releasing 2.1.12, wonderful!
Hello there,
how's the situation with C2.1.12 in 2013? Any help needed?
Regards.
Post by Cédric Damioli
Post by Francesco Chicchiriccò
[1]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20COCOON%20AND%20fixVersion%20%3D%20%222.1.12-dev%20(Current%20SVN)%22%20AND%20status%20in%20(Open%2C%20Reopened)%20ORDER%20BY%20priority%20DESC
[2]
http://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/misc/notes/review-jars.txt
[3]
http://markmail.org/message/ijmy6nzd2k4yzghn#query:+page:1+mid:dbsylujycgit224q+state:results
[4] http://www.apache.org/dev/release-signing.html
[5] http://www.apache.org/dist/cocoon/KEYS
[6]
http://svn.apache.org/viewvc/cocoon/branches/BRANCH_2_1_X/misc/notes/review-jars.txt
--
<http://www.anyware-services.com>
www.anyware-services.com <http://www.anyware-services.com>

<http://www.twitter.com/anywareservices>
<http://www.facebook.com/AnywareServices>
<http://anyware-services.us2.list-manage2.com/subscribe?u=1cf1cbf2891b613e90fd95eb2&id=01c7bdfce3>


Inscrivez-vous à notre newsletter

<http://anyware-services.us2.list-manage2.com/subscribe?u=1cf1cbf2891b613e90fd95eb2&id=01c7bdfce3>

*Cédric Damioli*
Directeur technique
***@anyware-services.com
<mailto:***@anyware-services.com>
Tel : +33(0)5 62 19 19 07
Mob : +33(0)6 87 03 61 63
Fax : +33(0)5 61 75 84 12
Adresse : Hôtel Télécom - Augustin Fresnel / 40 rue du Village
d'entreprises / 31670 LABEGE

Ametys: Smart Web CMS
<http://www.ametys.org> www.ametys.org <http://www.ametys.org>

Ce message et toutes les pièces jointes (le "Message") sont
confidentiels et établis à l'intention exclusive de ses destinataires.
Toute modification, édition, utilisation ou diffusion non autorisée est
interdite.
Anyware Services décline toute responsabilité au titre de ce Message
s'il a été altéré, déformé, falsifié ou édité, diffusé sans autorisation.
Francesco Chicchiriccò
2013-02-28 12:35:42 UTC
Permalink
Post by Cédric Damioli
Post by Francesco Chicchiriccò
Post by Cédric Damioli
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
Hi all,
It seems there remains only one open issue, COCOON-2333, related
to dependencies upgrade.
With r1451136 I have enabled the generation of .md5 and .sha1 for
dist packages, required by [4]: please check it to confirm that it
is working correctly.
The .asc files will also need to be generated, but I haven't found
an easy way to to this via ANT, hence I guess we have no option but
the manual way, e.g.
$ gpg --armor --output cocoon-2.1.12-src.zip.asc --detach-sig
cocoon-2.1.12-src.zip
$ gpg --armor --output cocoon-2.1.12-src.tar.gz.asc --detach-sig
cocoon-2.1.12-src.tar.gz
$ gpg --armor --output cocoon-2.1.12-deps.zip.asc --detach-sig
cocoon-2.1.12-deps.zip
$ gpg --armor --output cocoon-2.1.12-deps.tar.gz.asc --detach-sig
cocoon-2.1.12-deps.tar.gz
I urge to note that the release manager for 2.1.12 will also need
to be sure that his own key is contained in [5].
BTW, who is actually the release manager for 2.1.12 ?
Whoever wants to take this up: I was assuming you, actually ;-)
Having some experience with releases (Maven-driven, actually...) I
can help, if you want / need.
I'm ok to do the job, if it's ok for others too ;)
Well, the ASF is a do-ocracy [7] so don't be afraid :-)
Post by Cédric Damioli
Having never done Apache releases, I'll certainly need help at some
point, but IIRC the whole process was particularly well explained on
the wiki.
Guess you are referring to [8].
I think this will also be the chance to update it in some parts, so that
releasing 2.1.13 would be easier.

Regards.
Post by Cédric Damioli
Post by Francesco Chicchiriccò
Post by Cédric Damioli
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
David, Francesco, others, are we ok with current dependencies?
Some dependencies are obviously not on their latest versions, but
IMHO, trying to upgrade all jars would be too long, and users may
still upgrade one library if needed. What do you think?
We have recently turned all the "To be done" statements from [6]
into "Done", hence If no specific limitations and / or bugs are
known affecting the current versions of dependencies, I see no
reason for keep waiting.
I've made a very quick tour on samples and all seemed to work nice.
I'll look at them deeper once we have a release candidate.
Fine.
Post by Cédric Damioli
Post by Francesco Chicchiriccò
I'd create the release 2.1.13 on JIRA, move COCOON-2333 there and
start the release process for 2.1.12.
+1
It'll be part of the release process.
Fine again.
Regards.
Post by Cédric Damioli
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
Post by Francesco Chicchiriccò
Post by David Crossley
Post by Francesco Chicchiriccò
Post by Cédric Damioli
Hi there,
AFAIK the same 3 issues are still opened. Could you give me a hint
about the src/bin split?
COCOON-2330 - Could you please tell me (again) how to generate the
source and deps packages from SVN? Thanks.
Do "./build.sh dist".
There will also need to be different NOTICE and LICENSE
files for each package.
Adding this as comment to COCOON-2330 - let's move this
discussion there.
Post by David Crossley
Post by Francesco Chicchiriccò
Post by Cédric Damioli
Apart, there's the David issue about upgrading all
dependencies. I
don't know the status of it.
COCOON-2333 - According to [2], there are still few deps to check. I
remember I've asked David about how to contribute on this an he said
something like "update the JAR file an browse if samples still work"
See a few messages above on this list. There is more to it
than that, e.g. tweak lib/jars.xml file, do the build (which does
have some code tests), review the relevant samples, etc.
Also the issue is about "some" dependencies, not "all".
For example FOP, Batik, etc. would be good if possible.
Fine, I think I've found again such information at [3]; added
this also as comment to COCOON-2333 - let's move this discussion
there.
Post by David Crossley
Post by Francesco Chicchiriccò
Post by Cédric Damioli
And also an samples issue reopened by David. I don't know either what
to do with it.
COCOON-2069 - David, what should we do with this?
See my issue comment. I made a workaround to fix the cause
of the new misconfiguration which had broken the build for
everyone. It seems that the original patch must have included
some parts of some extra stuff (WSRP). I reckon forget it and
just leave the workaround in-place.
could you please take a look and reply? Thanks.
Regards.
Post by David Crossley
Post by Francesco Chicchiriccò
Post by Cédric Damioli
Post by Francesco Chicchiriccò
Post by Cédric Damioli
[...]
Post by Francesco Chicchiriccò
Hi all,
is everything tracked into JIRA [1]?
From my POV, yes.
I've added some comments to COCOON-2330. I'm not sure what to
include or exclude from the -src package.
Post by Francesco Chicchiriccò
If so, we are only 3 issues away from releasing 2.1.12, wonderful!
Hello there,
how's the situation with C2.1.12 in 2013? Any help needed?
Regards.
Post by Cédric Damioli
Post by Francesco Chicchiriccò
[1]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20COCOON%20AND%20fixVersion%20%3D%20%222.1.12-dev%20(Current%20SVN)%22%20AND%20status%20in%20(Open%2C%20Reopened)%20ORDER%20BY%20priority%20DESC
[2]
http://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/misc/notes/review-jars.txt
[3]
http://markmail.org/message/ijmy6nzd2k4yzghn#query:+page:1+mid:dbsylujycgit224q+state:results
[4] http://www.apache.org/dev/release-signing.html
[5] http://www.apache.org/dist/cocoon/KEYS
[6]
http://svn.apache.org/viewvc/cocoon/branches/BRANCH_2_1_X/misc/notes/review-jars.txt
[7] http://apache.org/foundation/how-it-works.html#decision-making
[8] http://wiki.apache.org/cocoon/CocoonReleaseHowTo
--
Francesco Chicchiriccò

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/
David Crossley
2013-03-03 05:30:55 UTC
Permalink
I am busy for the next two weeks, being away for the second.
Now half-way through testing Forrest using the recently updated
Cocoon and its FOP/Batik/etc. Will try to finish that ASAP.

I see that final touches were recently added to
http://www.apache.org/dev/licensing-howto.html
https://issues.apache.org/jira/browse/INCUBATOR-125

-David
Francesco Chicchiriccò
2013-03-04 12:30:56 UTC
Permalink
Post by David Crossley
I am busy for the next two weeks, being away for the second.
Now half-way through testing Forrest using the recently updated
Cocoon and its FOP/Batik/etc. Will try to finish that ASAP.
...guess it's wise to wait for you to finish such tests before starting
the actual release process ;-)

Regards.
Post by David Crossley
I see that final touches were recently added to
http://www.apache.org/dev/licensing-howto.html
https://issues.apache.org/jira/browse/INCUBATOR-125
--
Francesco Chicchiriccò

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/
Cédric Damioli
2013-03-04 14:18:02 UTC
Permalink
Post by Francesco Chicchiriccò
Post by David Crossley
I am busy for the next two weeks, being away for the second.
Now half-way through testing Forrest using the recently updated
Cocoon and its FOP/Batik/etc. Will try to finish that ASAP.
...guess it's wise to wait for you to finish such tests before
starting the actual release process ;-)
Indeed :)
Post by Francesco Chicchiriccò
Regards.
Post by David Crossley
I see that final touches were recently added to
http://www.apache.org/dev/licensing-howto.html
https://issues.apache.org/jira/browse/INCUBATOR-125
I think our recent work is still compliant with that. WDYT ?

Regards,
Cédric
David Crossley
2013-03-05 07:28:55 UTC
Permalink
Post by Cédric Damioli
Post by Francesco Chicchiriccò
Post by David Crossley
I am busy for the next two weeks, being away for the second.
Now half-way through testing Forrest using the recently updated
Cocoon and its FOP/Batik/etc. Will try to finish that ASAP.
...guess it's wise to wait for you to finish such tests before
starting the actual release process ;-)
Indeed :)
;-)
I only have time for some quick look and testing.
Done that now, and my local Forrest seems happy.

There are some svg-to-png errors from Batik, but other
svg-to-png is okay, so assuming that that is a Forrest issue.

-David
Post by Cédric Damioli
Post by Francesco Chicchiriccò
Post by David Crossley
I see that final touches were recently added to
http://www.apache.org/dev/licensing-howto.html
https://issues.apache.org/jira/browse/INCUBATOR-125
I think our recent work is still compliant with that. WDYT ?
Regards,
Cédric
Francesco Chicchiriccò
2013-03-05 07:55:38 UTC
Permalink
Post by David Crossley
Post by Cédric Damioli
Post by Francesco Chicchiriccò
Post by David Crossley
I am busy for the next two weeks, being away for the second.
Now half-way through testing Forrest using the recently updated
Cocoon and its FOP/Batik/etc. Will try to finish that ASAP.
...guess it's wise to wait for you to finish such tests before
starting the actual release process ;-)
Indeed :)
;-)
I only have time for some quick look and testing.
Done that now, and my local Forrest seems happy.
There are some svg-to-png errors from Batik, but other
svg-to-png is okay, so assuming that that is a Forrest issue.
Oooook, does this mean we can start rolling this long-waited 2.1.12??!?
Cédric, are you ready?

Regards.
Post by David Crossley
Post by Cédric Damioli
Post by Francesco Chicchiriccò
Post by David Crossley
I see that final touches were recently added to
http://www.apache.org/dev/licensing-howto.html
https://issues.apache.org/jira/browse/INCUBATOR-125
I think our recent work is still compliant with that. WDYT ?
Regards,
Cédric
--
Francesco Chicchiriccò

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/
Cédric Damioli
2013-03-05 10:18:20 UTC
Permalink
Hi team,
Post by Francesco Chicchiriccò
Oooook, does this mean we can start rolling this long-waited 2.1.12??!?
Cédric, are you ready?
Let's go !

We are now in the process of releasing 2.1.12 in the next few days, so
please don't check anything in in the 2.1.x branch.
I'll try to follow [1] as much as possible.

Best regards,
Cédric

[1] http://wiki.apache.org/cocoon/CocoonReleaseHowTo
Cédric Damioli
2013-03-08 19:28:03 UTC
Permalink
Hello,

I just uploaded the release material at
http://people.apache.org/~cdamioli/cocoon/

Before starting a formal vote, could some of you download and test the
files (signatures, installation, samples, ...) ?
I saw some broken samples, all related to some external sources (RSS
feeds, SOAP servers, ...). I don't know if this may be considered
blocker for the release.

BTW, how could I have write access on the wiki ? Who are administrators ?

Best regards,
Cédric
Post by Cédric Damioli
Hi team,
Post by Francesco Chicchiriccò
Oooook, does this mean we can start rolling this long-waited 2.1.12??!?
Cédric, are you ready?
Let's go !
We are now in the process of releasing 2.1.12 in the next few days, so
please don't check anything in in the 2.1.x branch.
I'll try to follow [1] as much as possible.
Best regards,
Cédric
[1] http://wiki.apache.org/cocoon/CocoonReleaseHowTo
--
Cédric Damioli
Ametys CMS
http://www.ametys.org
http://www.anyware-services.com
Francesco Chicchiriccò
2013-03-09 11:36:10 UTC
Permalink
Post by Cédric Damioli
Hello,
I just uploaded the release material at
http://people.apache.org/~cdamioli/cocoon/
Before starting a formal vote, could some of you download and test the
files (signatures, installation, samples, ...) ?
I'll so this on Monday.
Post by Cédric Damioli
I saw some broken samples, all related to some external sources (RSS
feeds, SOAP servers, ...). I don't know if this may be considered
blocker for the release.
I don't think so...
Post by Cédric Damioli
BTW, how could I have write access on the wiki ? Who are administrators ?
A while ago [2] we set up with Infra some security for our wiki: if you
want write access you need to be enlisted as contributor in [3]; any PMC
member can also be added to [4] thus becoming administrator.

Please tell me your username and I will add it to [3] or [4], as you prefer.

Regards.
Post by Cédric Damioli
Post by Cédric Damioli
Hi team,
Post by Francesco Chicchiriccò
Oooook, does this mean we can start rolling this long-waited 2.1.12??!?
Cédric, are you ready?
Let's go !
We are now in the process of releasing 2.1.12 in the next few days,
so please don't check anything in in the 2.1.x branch.
I'll try to follow [1] as much as possible.
Best regards,
Cédric
[1] http://wiki.apache.org/cocoon/CocoonReleaseHowTo
[2]
http://old.nabble.com/Re%3A-Spam-on-Cocoon-wiki---Fwd%3A--Cocoon-Wiki--Trivial-Update-of-%22FrontPage%22-by-wikimouse-p33732277.html
[3] http://wiki.apache.org/cocoon/ContributorsGroup
[4] http://wiki.apache.org/cocoon/AdminGroup
--
Francesco Chicchiriccò

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/
Francesco Chicchiriccò
2013-03-11 10:12:10 UTC
Permalink
Post by Cédric Damioli
Hello,
I just uploaded the release material at
http://people.apache.org/~cdamioli/cocoon/
Before starting a formal vote, could some of you download and test
the files (signatures, installation, samples, ...) ?
I'll do this on Monday.
I cannot download almost any file (but some .asc) from the given
location: 403 Forbidden
Post by Cédric Damioli
I saw some broken samples, all related to some external sources (RSS
feeds, SOAP servers, ...). I don't know if this may be considered
blocker for the release.
I don't think so...
Post by Cédric Damioli
BTW, how could I have write access on the wiki ? Who are
administrators ?
A while ago [2] we set up with Infra some security for our wiki: if
you want write access you need to be enlisted as contributor in [3];
any PMC member can also be added to [4] thus becoming administrator.
Please tell me your username and I will add it to [3] or [4], as you prefer.
Regards.
Post by Cédric Damioli
Post by Cédric Damioli
Hi team,
Post by Francesco Chicchiriccò
Oooook, does this mean we can start rolling this long-waited 2.1.12??!?
Cédric, are you ready?
Let's go !
We are now in the process of releasing 2.1.12 in the next few days,
so please don't check anything in in the 2.1.x branch.
I'll try to follow [1] as much as possible.
Best regards,
Cédric
[1] http://wiki.apache.org/cocoon/CocoonReleaseHowTo
[2]
http://old.nabble.com/Re%3A-Spam-on-Cocoon-wiki---Fwd%3A--Cocoon-Wiki--Trivial-Update-of-%22FrontPage%22-by-wikimouse-p33732277.html
[3] http://wiki.apache.org/cocoon/ContributorsGroup
[4] http://wiki.apache.org/cocoon/AdminGroup
--
Francesco Chicchiriccò

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/
Cédric Damioli
2013-03-11 10:18:13 UTC
Permalink
Post by Francesco Chicchiriccò
Post by Cédric Damioli
Hello,
I just uploaded the release material at
http://people.apache.org/~cdamioli/cocoon/
Before starting a formal vote, could some of you download and test
the files (signatures, installation, samples, ...) ?
I'll do this on Monday.
I cannot download almost any file (but some .asc) from the given
location: 403 Forbidden
ouuups, sorry
This should be better now.
Post by Francesco Chicchiriccò
Post by Cédric Damioli
I saw some broken samples, all related to some external sources (RSS
feeds, SOAP servers, ...). I don't know if this may be considered
blocker for the release.
I don't think so...
Post by Cédric Damioli
BTW, how could I have write access on the wiki ? Who are
administrators ?
A while ago [2] we set up with Infra some security for our wiki: if
you want write access you need to be enlisted as contributor in [3];
any PMC member can also be added to [4] thus becoming administrator.
Please tell me your username and I will add it to [3] or [4], as you prefer.
Regards.
Post by Cédric Damioli
Post by Cédric Damioli
Hi team,
Post by Francesco Chicchiriccò
Oooook, does this mean we can start rolling this long-waited 2.1.12??!?
Cédric, are you ready?
Let's go !
We are now in the process of releasing 2.1.12 in the next few days,
so please don't check anything in in the 2.1.x branch.
I'll try to follow [1] as much as possible.
Best regards,
Cédric
[1] http://wiki.apache.org/cocoon/CocoonReleaseHowTo
[2]
http://old.nabble.com/Re%3A-Spam-on-Cocoon-wiki---Fwd%3A--Cocoon-Wiki--Trivial-Update-of-%22FrontPage%22-by-wikimouse-p33732277.html
[3] http://wiki.apache.org/cocoon/ContributorsGroup
[4] http://wiki.apache.org/cocoon/AdminGroup
--
Cédric Damioli
Ametys CMS
http://www.ametys.org
http://www.anyware-services.com
Francesco Chicchiriccò
2013-03-11 16:37:26 UTC
Permalink
Post by Cédric Damioli
Post by Francesco Chicchiriccò
Post by Cédric Damioli
Hello,
I just uploaded the release material at
http://people.apache.org/~cdamioli/cocoon/
Before starting a formal vote, could some of you download and test
the files (signatures, installation, samples, ...) ?
I'll do this on Monday.
I cannot download almost any file (but some .asc) from the given
location: 403 Forbidden
ouuups, sorry
This should be better now.
I was able to
1. download all files
2. check ASC signatures and MD5 / SHA1 hashes
3. (either for zip and tar.gz) extract src, try to build and got
message about missing dependencies
4. (either for zip and tar.gz) extract deps, successfully build, run
and browse samples

If this was a formal vote, I would have given my +1
Nice job!

Looking forward for the actual vote.
Regards.
Post by Cédric Damioli
Post by Francesco Chicchiriccò
Post by Cédric Damioli
I saw some broken samples, all related to some external sources
(RSS feeds, SOAP servers, ...). I don't know if this may be
considered blocker for the release.
I don't think so...
Post by Cédric Damioli
BTW, how could I have write access on the wiki ? Who are
administrators ?
A while ago [2] we set up with Infra some security for our wiki: if
you want write access you need to be enlisted as contributor in [3];
any PMC member can also be added to [4] thus becoming administrator.
Please tell me your username and I will add it to [3] or [4], as you prefer.
Regards.
Post by Cédric Damioli
Post by Cédric Damioli
Hi team,
Post by Francesco Chicchiriccò
Oooook, does this mean we can start rolling this long-waited 2.1.12??!?
Cédric, are you ready?
Let's go !
We are now in the process of releasing 2.1.12 in the next few
days, so please don't check anything in in the 2.1.x branch.
I'll try to follow [1] as much as possible.
Best regards,
Cédric
[1] http://wiki.apache.org/cocoon/CocoonReleaseHowTo
[2]
http://old.nabble.com/Re%3A-Spam-on-Cocoon-wiki---Fwd%3A--Cocoon-Wiki--Trivial-Update-of-%22FrontPage%22-by-wikimouse-p33732277.html
[3] http://wiki.apache.org/cocoon/ContributorsGroup
[4] http://wiki.apache.org/cocoon/AdminGroup
--
Francesco Chicchiriccò

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/
Cédric Damioli
2013-03-13 11:28:40 UTC
Permalink
Post by Francesco Chicchiriccò
I was able to
1. download all files
2. check ASC signatures and MD5 / SHA1 hashes
3. (either for zip and tar.gz) extract src, try to build and got
message about missing dependencies
4. (either for zip and tar.gz) extract deps, successfully build, run
and browse samples
If this was a formal vote, I would have given my +1
Nice job!
Looking forward for the actual vote.
Regards.
Thanks for your feedback.
I hope to be able to tag the SVN, rebuild the files, and launch the
formal vote later today.

Regards,
--
Cédric Damioli
Ametys CMS
http://www.ametys.org
http://www.anyware-services.com
Cédric Damioli
2013-03-14 14:56:51 UTC
Permalink
Hi,
Post by Francesco Chicchiriccò
Post by Cédric Damioli
BTW, how could I have write access on the wiki ? Who are
administrators ?
A while ago [2] we set up with Infra some security for our wiki: if
you want write access you need to be enlisted as contributor in [3];
any PMC member can also be added to [4] thus becoming administrator.
Please tell me your username and I will add it to [3] or [4], as you prefer.
My user name on the Wiki is CedricDamioli

Thanks,
Cédric
Post by Francesco Chicchiriccò
Regards.
Post by Cédric Damioli
Post by Cédric Damioli
Hi team,
Post by Francesco Chicchiriccò
Oooook, does this mean we can start rolling this long-waited 2.1.12??!?
Cédric, are you ready?
Let's go !
We are now in the process of releasing 2.1.12 in the next few days,
so please don't check anything in in the 2.1.x branch.
I'll try to follow [1] as much as possible.
Best regards,
Cédric
[1] http://wiki.apache.org/cocoon/CocoonReleaseHowTo
[2]
http://old.nabble.com/Re%3A-Spam-on-Cocoon-wiki---Fwd%3A--Cocoon-Wiki--Trivial-Update-of-%22FrontPage%22-by-wikimouse-p33732277.html
[3] http://wiki.apache.org/cocoon/ContributorsGroup
[4] http://wiki.apache.org/cocoon/AdminGroup
Francesco Chicchiriccò
2013-03-14 15:04:43 UTC
Permalink
Post by Cédric Damioli
Hi,
Post by Francesco Chicchiriccò
Post by Cédric Damioli
BTW, how could I have write access on the wiki ? Who are
administrators ?
A while ago [2] we set up with Infra some security for our wiki: if
you want write access you need to be enlisted as contributor in [3];
any PMC member can also be added to [4] thus becoming administrator.
Please tell me your username and I will add it to [3] or [4], as you prefer.
My user name on the Wiki is CedricDamioli
Added to [3].

Regards.
Post by Cédric Damioli
Post by Francesco Chicchiriccò
Regards.
Post by Cédric Damioli
Post by Cédric Damioli
Hi team,
Post by Francesco Chicchiriccò
Oooook, does this mean we can start rolling this long-waited 2.1.12??!?
Cédric, are you ready?
Let's go !
We are now in the process of releasing 2.1.12 in the next few
days, so please don't check anything in in the 2.1.x branch.
I'll try to follow [1] as much as possible.
Best regards,
Cédric
[1] http://wiki.apache.org/cocoon/CocoonReleaseHowTo
[2]
http://old.nabble.com/Re%3A-Spam-on-Cocoon-wiki---Fwd%3A--Cocoon-Wiki--Trivial-Update-of-%22FrontPage%22-by-wikimouse-p33732277.html
[3] http://wiki.apache.org/cocoon/ContributorsGroup
[4] http://wiki.apache.org/cocoon/AdminGroup
--
Francesco Chicchiriccò

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/
Loading...