cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cédric Damioli <cedric.dami...@anyware-services.com>
Subject Re: [DISCUSS] Releasing 2.1.12
Date Thu, 28 Feb 2013 10:44:33 GMT

Le 28/02/2013 11:26, Francesco Chicchiriccò a écrit :
> On 28/02/2013 11:22, Cédric Damioli wrote:
>> Le 28/02/2013 10:04, Francesco Chicchiriccò a écrit :
>>> On 27/02/2013 22:55, Cédric Damioli wrote:
>>>> 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.

>
>>>> 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.
>
>>> 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.
>
>>>> Le 22/01/2013 11:40, Francesco Chicchiriccò a écrit :
>>>>> On 22/01/2013 07:26, David Crossley wrote:
>>>>>> 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.
>>>>>
>>>>> Adding this as comment to COCOON-2330 - let's move this discussion 
>>>>> there.
>>>>>
>>>>>>>> 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.
>>>>>
>>>>>>>> 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.
>>>>>
>>>>>>>> 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
>>>>> [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
cedric.damioli@anyware-services.com 
<mailto:cedric.damioli@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.

Mime
View raw message