[DISCUSS] Releasing 2.2.1
Hi all (but Thorsten and Javier in particular), by looking at JIRA [1] it seems that quite a considerable number of issues have been fixed since 2.2 (23) even though some are still standing (6+1). Following our recent discussion in another thread, I have some questions: 1. Do you think that the the 7 outstanding issues can be moved to 2.2.2 or there are some that need to be absolutely included in 2.2.1? 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 have never worked with C2.2 4. Considering the questions above, when do you think we can start releasing 2.2.1? Thanks for info. Regards. [1] https://issues.apache.org/jira/browse/COCOON/fixforversion/12313093 -- Francesco Chicchiriccò ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member http://people.apache.org/~ilgrosso/
[jira] [Updated] (COCOON-2304) ThreadLocal in Rhino context is not always cleared
[
https://issues.apache.org/jira/browse/COCOON-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò updated COCOON-2304:
---
Fix Version/s: (was: 2.2)
2.2.1-SNAPSHOT
> ThreadLocal in Rhino context is not always cleared
> --
>
> Key: COCOON-2304
> URL: https://issues.apache.org/jira/browse/COCOON-2304
> Project: Cocoon
> Issue Type: Bug
> Components: - Flowscript
>Reporter: Graham Triggs
> Fix For: 2.2.1-SNAPSHOT
>
> Attachments: flowscript.diff
>
>
> The Mozilla Rhino Context isn't exited in all cases in
> FOM_JavascriptInterpreter. This can lead to a leak on application
> undeployment, with the ThreadLocal references inside.
> Patch restructures the code slightly to use try { } finally { } blocks to
> ensure the Context.exit() is called where appropriate (this makes the patch
> look bigger than it really is, due to indenting).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (COCOON-2108) xmodule:flow-attr Does not accept document objects
[ https://issues.apache.org/jira/browse/COCOON-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated COCOON-2108: --- Fix Version/s: (was: 2.2) 2.2.1-SNAPSHOT > xmodule:flow-attr Does not accept document objects > -- > > Key: COCOON-2108 > URL: https://issues.apache.org/jira/browse/COCOON-2108 > Project: Cocoon > Issue Type: Bug > Components: * Cocoon Core >Affects Versions: 2.1.11, 2.2 >Reporter: Hugh Sparks >Priority: Minor > Fix For: 2.1.12-dev (Current SVN), 2.2.1-SNAPSHOT > > Attachments: Cocoon-2.2-truck-JXPathHelper.java.patch, > Cocoon-BRANCH-2.1.X-JXPathHelper.java.patch, xmodulePuzzle.txt > > > Sending document objects from flowscript back to the pipeline using > xmodule:flow-attr produces unexpected results. Also, the examples from > the documentation do not work as described: > http://cocoon.apache.org/2.1/861.daisy.html > The most common error reported is: > 'The object type: class java.lang.String could not be serialized to XML" > This issue was discussed recently on the cocoon-users mailing list. > The thread was introduced by Kazo Csaba with the subject "Sending DOM from > flowscript to pipeline." > (July 17, 2007) > He has attempted to trace this behavior in the source code and believes that a > possibly-inappropriate conversion to string occurs in some cases. > Jason Johnston suggested moving the issue to JIRA. > I've created a demonstration of this apparent bug and some related problems > in this very brief example: > http://www.csparks.com/xmodulePuzzle.txt > I hope someone can fix or explain the correct usage of xmodule:flow-attr. > Thanks to all, > -Hugh Sparks, h...@csparks.com -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[DISCUSS] Releasing 2.1.12
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/
[jira] [Closed] (COCOON-2329) Fix and update http://cocoon.apache.org/1273_1_1.html content
[ https://issues.apache.org/jira/browse/COCOON-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò closed COCOON-2329. -- Resolution: Fixed http://svn.apache.org/viewvc?rev=1410930&view=rev > Fix and update http://cocoon.apache.org/1273_1_1.html content > - > > Key: COCOON-2329 > URL: https://issues.apache.org/jira/browse/COCOON-2329 > Project: Cocoon > Issue Type: Bug > Components: Site >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò > > As reported in user mailing list [1] the "Getting involved" page needs some > fixes and update. > [1] http://cocoon.markmail.org/thread/dswbfzhv4eacsnjc -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
RE: [DISCUSS] Release plan
Hi, Did anyone read any of these OSGI books by any chance? http://www.manning.com/hall/ http://www.manning.com/cummins/ http://www.manning.com/alves/ I am interested in buying one of these to get more acquainted and perhaps help out in the future. Robby -Original Message- From: Thorsten Scherler [mailto:scher...@gmail.com] Sent: Saturday, November 17, 2012 10:43 PM To: dev@cocoon.apache.org Subject: Re: [DISCUSS] Release plan On 11/12/2012 10:25 AM, Francesco Chicchiriccò wrote: > ... > = > > My questions now are: > > 1. Would you agree with the above drafted release plan? Yes, with a 2.1 release, since I recall there had been a couple of changes. > > 2. If so, who is available to help with these tasks? Consider that > documentation tasks are an easier way to contribute to the project > even without development skills. In 2002 I started exactly in this project with documentation. The initial purpose of cocoon was to generate consistence documentation for java.apache.org meaning to write some cocoon docs (esp. c3) be sure you pop onto our watch list. > > If you've been using C3 and appreciate this, please don't deny your > help: we really need it! c3 is really missing helping hands. I would love to get some cocoon veterans reactivated again especially for the OSGI re-factoring that we need to do in the future. This project is as old as the ASF itself and we have a long list of prime ASF member contributing to this project. However I understand that we all only have very limited time. ...but for everyone that is reading this and like the idea of cocoon please help with - constructive discussions and giving the helping hand on the ml - documentation - testing and bug fixing - integrating c3 in your project salu2 PS thanks Francesco for starting this and it had been a pleasure to meet you in person. -- Thorsten Scherler codeBusters S.L. - web based systems http://www.codebusters.es/
