Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Date: Tue, 22 Jan 2013 17:26:51 +1100
From: David Crossley <crossley@apache.org>
To: dev@cocoon.apache.org
Subject: Re: [DISCUSS] Releasing 2.1.12
Message-ID: <20130122062651.GB4420@igg.local>
References: <50A91C4C.6010100@apache.org> <20121207071446.GB26603@igg.local>
 <50C19E44.1070303@apache.org> <50C70F02.5020703@apache.org>
 <50C71925.3040702@apache.org> <50FAA9A0.6060504@apache.org>
 <50FAC79A.6010705@apache.org> <50FC1044.8040906@apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <50FC1044.8040906@apache.org>
User-Agent: Mutt/1.4.2.3i

Francesco Chicchiricc� wrote:
> C�dric Damioli wrote:
> >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.

> >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.

> >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

> Regards.
> 
> >Le 19/01/2013 15:11, Francesco Chicchiricc� a �crit :
> >>On 11/12/2012 12:29, C�dric Damioli wrote:
> >>>[...]
> >>>>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.
> >>>
> >>>>
> >>>>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.
> >>
> >>>>[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/
>