You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Christian Grobmeier <gr...@gmail.com> on 2011/10/14 13:33:20 UTC
[ognl] Make us of changes.xml
Hey guys,
i would like to suggest we make consequent use of changes.xml.
Whatever we do, we should open an issue, fix the stuff, and then add a
comment to changes.xml. We do this in log4php and I feel it is very
good: you always can find the changes per issues (via Fisheye- just
check in with the OGNL- number in the comment). And of course it makes
it easy for the release notes and gives a good oversight for us.
Any objections if we would do that from now on?
I have added some missing entries before minutes - please check if I
mentioned the correct dev for this change.
Thanks!
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [ognl] Make us of changes.xml
Posted by Maurizio Cucchiara <ma...@gmail.com>.
Ok,
then no objection from my side.
Sent from my mobile device, so please excuse typos and brevity.
Maurizio Cucchiara
Il giorno 14/ott/2011 14.24, "Simone Tripodi" <si...@apache.org> ha
scritto:
> having the changes.xml is what we already do in all other Commons
> component, for the specific reason that the JIRA report just collect
> the list of fixed issues, collecting changes allows grouping them by
> release.
> +1 for changes
> Simo
>
> http://people.apache.org/~simonetripodi/
> http://simonetripodi.livejournal.com/
> http://twitter.com/simonetripodi
> http://www.99soft.org/
>
>
>
> On Fri, Oct 14, 2011 at 2:18 PM, Christian Grobmeier
> <gr...@gmail.com> wrote:
> > So your preference is to get rid of changes.xml?
> > Because changes would be visible on the site too....
> >
> > On Fri, Oct 14, 2011 at 2:16 PM, Maurizio Cucchiara
> > <ma...@gmail.com> wrote:
> >> Jiira is also able to compute release notes.
> >>
> >> ATM I can't, I will post a link later.
> >>
> >> Sent from my mobile device, so please excuse typos and brevity.
> >>
> >> Maurizio Cucchiara
> >>
> >> Il giorno 14/ott/2011 13.34, "Christian Grobmeier" <gr...@gmail.com>
> ha
> >> scritto:
> >>
> >>> Hey guys,
> >>>
> >>> i would like to suggest we make consequent use of changes.xml.
> >>> Whatever we do, we should open an issue, fix the stuff, and then add a
> >>> comment to changes.xml. We do this in log4php and I feel it is very
> >>> good: you always can find the changes per issues (via Fisheye- just
> >>> check in with the OGNL- number in the comment). And of course it makes
> >>> it easy for the release notes and gives a good oversight for us.
> >>>
> >>> Any objections if we would do that from now on?
> >>>
> >>> I have added some missing entries before minutes - please check if I
> >>> mentioned the correct dev for this change.
> >>>
> >>> Thanks!
> >>> Christian
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> >>> For additional commands, e-mail: dev-help@commons.apache.org
> >>>
> >>>
> >>
> >
> >
> >
> > --
> > http://www.grobmeier.de
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
Re: [ognl] Make us of changes.xml
Posted by Simone Tripodi <si...@apache.org>.
having the changes.xml is what we already do in all other Commons
component, for the specific reason that the JIRA report just collect
the list of fixed issues, collecting changes allows grouping them by
release.
+1 for changes
Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On Fri, Oct 14, 2011 at 2:18 PM, Christian Grobmeier
<gr...@gmail.com> wrote:
> So your preference is to get rid of changes.xml?
> Because changes would be visible on the site too....
>
> On Fri, Oct 14, 2011 at 2:16 PM, Maurizio Cucchiara
> <ma...@gmail.com> wrote:
>> Jiira is also able to compute release notes.
>>
>> ATM I can't, I will post a link later.
>>
>> Sent from my mobile device, so please excuse typos and brevity.
>>
>> Maurizio Cucchiara
>>
>> Il giorno 14/ott/2011 13.34, "Christian Grobmeier" <gr...@gmail.com> ha
>> scritto:
>>
>>> Hey guys,
>>>
>>> i would like to suggest we make consequent use of changes.xml.
>>> Whatever we do, we should open an issue, fix the stuff, and then add a
>>> comment to changes.xml. We do this in log4php and I feel it is very
>>> good: you always can find the changes per issues (via Fisheye- just
>>> check in with the OGNL- number in the comment). And of course it makes
>>> it easy for the release notes and gives a good oversight for us.
>>>
>>> Any objections if we would do that from now on?
>>>
>>> I have added some missing entries before minutes - please check if I
>>> mentioned the correct dev for this change.
>>>
>>> Thanks!
>>> Christian
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>>
>>
>
>
>
> --
> http://www.grobmeier.de
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [ognl] Make us of changes.xml
Posted by Simone Tripodi <si...@apache.org>.
OK sounds I'm making confusion with other projects :) I'll investigate
Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On Fri, Oct 14, 2011 at 3:58 PM, sebb <se...@gmail.com> wrote:
> On 14 October 2011 14:50, Simone Tripodi <si...@apache.org> wrote:
>> just to speak about it: what about putting the .vm template in the
>> remote-resources that bring the LICENSE and NOTICE txt files?
>
> AFAIK, we don't use that.
>
> Anyway, the NOTICE file is specific to each component.
>
>> If it could work, we could put as well basic assemblies descriptor -
>> and components that require customization can easily modify them...
>
> I've no idea how to do that.
>
>> Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://simonetripodi.livejournal.com/
>> http://twitter.com/simonetripodi
>> http://www.99soft.org/
>>
>>
>>
>> On Fri, Oct 14, 2011 at 3:37 PM, sebb <se...@gmail.com> wrote:
>>> On 14 October 2011 14:02, Simone Tripodi <si...@apache.org> wrote:
>>>> I love Seb's approach, if we could specify a way to reuse a shared
>>>> template to generate the release note s in every component, without
>>>> any extra setting, would be amazing!
>>>
>>> I looked into that already.
>>> I don't remember the exact details, but it was quite complicated and messy.
>>> AFAICT it's not possible to include the template in Commons Parent
>>> (that only works for site.xml).
>>>
>>> But of course if a Maven guru can fix it so it's easier to use, please advise.
>>>
>>> The advantage of the current method is that the template can be
>>> tweaked locally if required (but hopefully that's not necessary).
>>>
>>>> Simo
>>>>
>>>> http://people.apache.org/~simonetripodi/
>>>> http://simonetripodi.livejournal.com/
>>>> http://twitter.com/simonetripodi
>>>> http://www.99soft.org/
>>>>
>>>>
>>>>
>>>> On Fri, Oct 14, 2011 at 2:38 PM, sebb <se...@gmail.com> wrote:
>>>>> You can also use changes.xml to produce a release notes text file
>>>>> which can be included in the archives (and used in announces if
>>>>> required).
>>>>>
>>>>> This was added to Commons Parent recently:
>>>>>
>>>>>>>>
>>>>> mvn changes:announcement-generate -Prelease-notes
>>>>>
>>>>> Requires file src/changes/release-notes.vm.
>>>>> A sample template is available from:
>>>>> https://svn.apache.org/repos/asf/commons/proper/commons-parent/trunk/src/changes/release-notes.vm
>>>>> <<<
>>>>>
>>>>> Formatting of the description can be tweaked by using double-space to
>>>>> generate a new-line (this does not affect the HTML version).
>>>>>
>>>>> On 14 October 2011 13:28, Simone Tripodi <si...@apache.org> wrote:
>>>>>> see my previous message; just to give an example, take a look at the
>>>>>> [digester] reports:
>>>>>>
>>>>>> http://commons.apache.org/digester/changes-report.html (changes.xml
>>>>>> introduced only in last release)
>>>>>> http://commons.apache.org/digester/jira-report.html (all jira issues)
>>>>>>
>>>>>> does it make sense?
>>>>>> Simo
>>>>>>
>>>>>> http://people.apache.org/~simonetripodi/
>>>>>> http://simonetripodi.livejournal.com/
>>>>>> http://twitter.com/simonetripodi
>>>>>> http://www.99soft.org/
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Fri, Oct 14, 2011 at 2:24 PM, Maurizio Cucchiara
>>>>>> <ma...@gmail.com> wrote:
>>>>>>> I still no have preference, I would like to understand why we should add
>>>>>>> optional work.
>>>>>>> If there is a valid reason, why not?
>>>>>>> I guess that the next answer is could jiira automatically do what xml is
>>>>>>> able to do?
>>>>>>>
>>>>>>> Sent from my mobile device, so please excuse typos and brevity.
>>>>>>>
>>>>>>> Maurizio Cucchiara
>>>>>>>
>>>>>>> Il giorno 14/ott/2011 14.19, "Christian Grobmeier" <gr...@gmail.com> ha
>>>>>>> scritto:
>>>>>>> So your preference is to get rid of changes.xml?
>>>>>>> Because changes would be visible on the site too....
>>>>>>>
>>>>>>>
>>>>>>> On Fri, Oct 14, 2011 at 2:16 PM, Maurizio Cucchiara
>>>>>>> <ma...@gmail.com> wrote:
>>>>>>>> Jiira i...
>>>>>>> --
>>>>>>> http://www.grobmeier.de
>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-u...
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [ognl] Make us of changes.xml
Posted by sebb <se...@gmail.com>.
On 14 October 2011 14:50, Simone Tripodi <si...@apache.org> wrote:
> just to speak about it: what about putting the .vm template in the
> remote-resources that bring the LICENSE and NOTICE txt files?
AFAIK, we don't use that.
Anyway, the NOTICE file is specific to each component.
> If it could work, we could put as well basic assemblies descriptor -
> and components that require customization can easily modify them...
I've no idea how to do that.
> Simo
>
> http://people.apache.org/~simonetripodi/
> http://simonetripodi.livejournal.com/
> http://twitter.com/simonetripodi
> http://www.99soft.org/
>
>
>
> On Fri, Oct 14, 2011 at 3:37 PM, sebb <se...@gmail.com> wrote:
>> On 14 October 2011 14:02, Simone Tripodi <si...@apache.org> wrote:
>>> I love Seb's approach, if we could specify a way to reuse a shared
>>> template to generate the release note s in every component, without
>>> any extra setting, would be amazing!
>>
>> I looked into that already.
>> I don't remember the exact details, but it was quite complicated and messy.
>> AFAICT it's not possible to include the template in Commons Parent
>> (that only works for site.xml).
>>
>> But of course if a Maven guru can fix it so it's easier to use, please advise.
>>
>> The advantage of the current method is that the template can be
>> tweaked locally if required (but hopefully that's not necessary).
>>
>>> Simo
>>>
>>> http://people.apache.org/~simonetripodi/
>>> http://simonetripodi.livejournal.com/
>>> http://twitter.com/simonetripodi
>>> http://www.99soft.org/
>>>
>>>
>>>
>>> On Fri, Oct 14, 2011 at 2:38 PM, sebb <se...@gmail.com> wrote:
>>>> You can also use changes.xml to produce a release notes text file
>>>> which can be included in the archives (and used in announces if
>>>> required).
>>>>
>>>> This was added to Commons Parent recently:
>>>>
>>>>>>>
>>>> mvn changes:announcement-generate -Prelease-notes
>>>>
>>>> Requires file src/changes/release-notes.vm.
>>>> A sample template is available from:
>>>> https://svn.apache.org/repos/asf/commons/proper/commons-parent/trunk/src/changes/release-notes.vm
>>>> <<<
>>>>
>>>> Formatting of the description can be tweaked by using double-space to
>>>> generate a new-line (this does not affect the HTML version).
>>>>
>>>> On 14 October 2011 13:28, Simone Tripodi <si...@apache.org> wrote:
>>>>> see my previous message; just to give an example, take a look at the
>>>>> [digester] reports:
>>>>>
>>>>> http://commons.apache.org/digester/changes-report.html (changes.xml
>>>>> introduced only in last release)
>>>>> http://commons.apache.org/digester/jira-report.html (all jira issues)
>>>>>
>>>>> does it make sense?
>>>>> Simo
>>>>>
>>>>> http://people.apache.org/~simonetripodi/
>>>>> http://simonetripodi.livejournal.com/
>>>>> http://twitter.com/simonetripodi
>>>>> http://www.99soft.org/
>>>>>
>>>>>
>>>>>
>>>>> On Fri, Oct 14, 2011 at 2:24 PM, Maurizio Cucchiara
>>>>> <ma...@gmail.com> wrote:
>>>>>> I still no have preference, I would like to understand why we should add
>>>>>> optional work.
>>>>>> If there is a valid reason, why not?
>>>>>> I guess that the next answer is could jiira automatically do what xml is
>>>>>> able to do?
>>>>>>
>>>>>> Sent from my mobile device, so please excuse typos and brevity.
>>>>>>
>>>>>> Maurizio Cucchiara
>>>>>>
>>>>>> Il giorno 14/ott/2011 14.19, "Christian Grobmeier" <gr...@gmail.com> ha
>>>>>> scritto:
>>>>>> So your preference is to get rid of changes.xml?
>>>>>> Because changes would be visible on the site too....
>>>>>>
>>>>>>
>>>>>> On Fri, Oct 14, 2011 at 2:16 PM, Maurizio Cucchiara
>>>>>> <ma...@gmail.com> wrote:
>>>>>>> Jiira i...
>>>>>> --
>>>>>> http://www.grobmeier.de
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-u...
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [ognl] Make us of changes.xml
Posted by Simone Tripodi <si...@apache.org>.
just to speak about it: what about putting the .vm template in the
remote-resources that bring the LICENSE and NOTICE txt files?
If it could work, we could put as well basic assemblies descriptor -
and components that require customization can easily modify them...
Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On Fri, Oct 14, 2011 at 3:37 PM, sebb <se...@gmail.com> wrote:
> On 14 October 2011 14:02, Simone Tripodi <si...@apache.org> wrote:
>> I love Seb's approach, if we could specify a way to reuse a shared
>> template to generate the release note s in every component, without
>> any extra setting, would be amazing!
>
> I looked into that already.
> I don't remember the exact details, but it was quite complicated and messy.
> AFAICT it's not possible to include the template in Commons Parent
> (that only works for site.xml).
>
> But of course if a Maven guru can fix it so it's easier to use, please advise.
>
> The advantage of the current method is that the template can be
> tweaked locally if required (but hopefully that's not necessary).
>
>> Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://simonetripodi.livejournal.com/
>> http://twitter.com/simonetripodi
>> http://www.99soft.org/
>>
>>
>>
>> On Fri, Oct 14, 2011 at 2:38 PM, sebb <se...@gmail.com> wrote:
>>> You can also use changes.xml to produce a release notes text file
>>> which can be included in the archives (and used in announces if
>>> required).
>>>
>>> This was added to Commons Parent recently:
>>>
>>>>>>
>>> mvn changes:announcement-generate -Prelease-notes
>>>
>>> Requires file src/changes/release-notes.vm.
>>> A sample template is available from:
>>> https://svn.apache.org/repos/asf/commons/proper/commons-parent/trunk/src/changes/release-notes.vm
>>> <<<
>>>
>>> Formatting of the description can be tweaked by using double-space to
>>> generate a new-line (this does not affect the HTML version).
>>>
>>> On 14 October 2011 13:28, Simone Tripodi <si...@apache.org> wrote:
>>>> see my previous message; just to give an example, take a look at the
>>>> [digester] reports:
>>>>
>>>> http://commons.apache.org/digester/changes-report.html (changes.xml
>>>> introduced only in last release)
>>>> http://commons.apache.org/digester/jira-report.html (all jira issues)
>>>>
>>>> does it make sense?
>>>> Simo
>>>>
>>>> http://people.apache.org/~simonetripodi/
>>>> http://simonetripodi.livejournal.com/
>>>> http://twitter.com/simonetripodi
>>>> http://www.99soft.org/
>>>>
>>>>
>>>>
>>>> On Fri, Oct 14, 2011 at 2:24 PM, Maurizio Cucchiara
>>>> <ma...@gmail.com> wrote:
>>>>> I still no have preference, I would like to understand why we should add
>>>>> optional work.
>>>>> If there is a valid reason, why not?
>>>>> I guess that the next answer is could jiira automatically do what xml is
>>>>> able to do?
>>>>>
>>>>> Sent from my mobile device, so please excuse typos and brevity.
>>>>>
>>>>> Maurizio Cucchiara
>>>>>
>>>>> Il giorno 14/ott/2011 14.19, "Christian Grobmeier" <gr...@gmail.com> ha
>>>>> scritto:
>>>>> So your preference is to get rid of changes.xml?
>>>>> Because changes would be visible on the site too....
>>>>>
>>>>>
>>>>> On Fri, Oct 14, 2011 at 2:16 PM, Maurizio Cucchiara
>>>>> <ma...@gmail.com> wrote:
>>>>>> Jiira i...
>>>>> --
>>>>> http://www.grobmeier.de
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-u...
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [ognl] Make us of changes.xml
Posted by sebb <se...@gmail.com>.
On 14 October 2011 14:02, Simone Tripodi <si...@apache.org> wrote:
> I love Seb's approach, if we could specify a way to reuse a shared
> template to generate the release note s in every component, without
> any extra setting, would be amazing!
I looked into that already.
I don't remember the exact details, but it was quite complicated and messy.
AFAICT it's not possible to include the template in Commons Parent
(that only works for site.xml).
But of course if a Maven guru can fix it so it's easier to use, please advise.
The advantage of the current method is that the template can be
tweaked locally if required (but hopefully that's not necessary).
> Simo
>
> http://people.apache.org/~simonetripodi/
> http://simonetripodi.livejournal.com/
> http://twitter.com/simonetripodi
> http://www.99soft.org/
>
>
>
> On Fri, Oct 14, 2011 at 2:38 PM, sebb <se...@gmail.com> wrote:
>> You can also use changes.xml to produce a release notes text file
>> which can be included in the archives (and used in announces if
>> required).
>>
>> This was added to Commons Parent recently:
>>
>>>>>
>> mvn changes:announcement-generate -Prelease-notes
>>
>> Requires file src/changes/release-notes.vm.
>> A sample template is available from:
>> https://svn.apache.org/repos/asf/commons/proper/commons-parent/trunk/src/changes/release-notes.vm
>> <<<
>>
>> Formatting of the description can be tweaked by using double-space to
>> generate a new-line (this does not affect the HTML version).
>>
>> On 14 October 2011 13:28, Simone Tripodi <si...@apache.org> wrote:
>>> see my previous message; just to give an example, take a look at the
>>> [digester] reports:
>>>
>>> http://commons.apache.org/digester/changes-report.html (changes.xml
>>> introduced only in last release)
>>> http://commons.apache.org/digester/jira-report.html (all jira issues)
>>>
>>> does it make sense?
>>> Simo
>>>
>>> http://people.apache.org/~simonetripodi/
>>> http://simonetripodi.livejournal.com/
>>> http://twitter.com/simonetripodi
>>> http://www.99soft.org/
>>>
>>>
>>>
>>> On Fri, Oct 14, 2011 at 2:24 PM, Maurizio Cucchiara
>>> <ma...@gmail.com> wrote:
>>>> I still no have preference, I would like to understand why we should add
>>>> optional work.
>>>> If there is a valid reason, why not?
>>>> I guess that the next answer is could jiira automatically do what xml is
>>>> able to do?
>>>>
>>>> Sent from my mobile device, so please excuse typos and brevity.
>>>>
>>>> Maurizio Cucchiara
>>>>
>>>> Il giorno 14/ott/2011 14.19, "Christian Grobmeier" <gr...@gmail.com> ha
>>>> scritto:
>>>> So your preference is to get rid of changes.xml?
>>>> Because changes would be visible on the site too....
>>>>
>>>>
>>>> On Fri, Oct 14, 2011 at 2:16 PM, Maurizio Cucchiara
>>>> <ma...@gmail.com> wrote:
>>>>> Jiira i...
>>>> --
>>>> http://www.grobmeier.de
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-u...
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [ognl] Make us of changes.xml
Posted by Simone Tripodi <si...@apache.org>.
I love Seb's approach, if we could specify a way to reuse a shared
template to generate the release note s in every component, without
any extra setting, would be amazing!
Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On Fri, Oct 14, 2011 at 2:38 PM, sebb <se...@gmail.com> wrote:
> You can also use changes.xml to produce a release notes text file
> which can be included in the archives (and used in announces if
> required).
>
> This was added to Commons Parent recently:
>
>>>>
> mvn changes:announcement-generate -Prelease-notes
>
> Requires file src/changes/release-notes.vm.
> A sample template is available from:
> https://svn.apache.org/repos/asf/commons/proper/commons-parent/trunk/src/changes/release-notes.vm
> <<<
>
> Formatting of the description can be tweaked by using double-space to
> generate a new-line (this does not affect the HTML version).
>
> On 14 October 2011 13:28, Simone Tripodi <si...@apache.org> wrote:
>> see my previous message; just to give an example, take a look at the
>> [digester] reports:
>>
>> http://commons.apache.org/digester/changes-report.html (changes.xml
>> introduced only in last release)
>> http://commons.apache.org/digester/jira-report.html (all jira issues)
>>
>> does it make sense?
>> Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://simonetripodi.livejournal.com/
>> http://twitter.com/simonetripodi
>> http://www.99soft.org/
>>
>>
>>
>> On Fri, Oct 14, 2011 at 2:24 PM, Maurizio Cucchiara
>> <ma...@gmail.com> wrote:
>>> I still no have preference, I would like to understand why we should add
>>> optional work.
>>> If there is a valid reason, why not?
>>> I guess that the next answer is could jiira automatically do what xml is
>>> able to do?
>>>
>>> Sent from my mobile device, so please excuse typos and brevity.
>>>
>>> Maurizio Cucchiara
>>>
>>> Il giorno 14/ott/2011 14.19, "Christian Grobmeier" <gr...@gmail.com> ha
>>> scritto:
>>> So your preference is to get rid of changes.xml?
>>> Because changes would be visible on the site too....
>>>
>>>
>>> On Fri, Oct 14, 2011 at 2:16 PM, Maurizio Cucchiara
>>> <ma...@gmail.com> wrote:
>>>> Jiira i...
>>> --
>>> http://www.grobmeier.de
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-u...
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [ognl] Make us of changes.xml
Posted by sebb <se...@gmail.com>.
You can also use changes.xml to produce a release notes text file
which can be included in the archives (and used in announces if
required).
This was added to Commons Parent recently:
>>>
mvn changes:announcement-generate -Prelease-notes
Requires file src/changes/release-notes.vm.
A sample template is available from:
https://svn.apache.org/repos/asf/commons/proper/commons-parent/trunk/src/changes/release-notes.vm
<<<
Formatting of the description can be tweaked by using double-space to
generate a new-line (this does not affect the HTML version).
On 14 October 2011 13:28, Simone Tripodi <si...@apache.org> wrote:
> see my previous message; just to give an example, take a look at the
> [digester] reports:
>
> http://commons.apache.org/digester/changes-report.html (changes.xml
> introduced only in last release)
> http://commons.apache.org/digester/jira-report.html (all jira issues)
>
> does it make sense?
> Simo
>
> http://people.apache.org/~simonetripodi/
> http://simonetripodi.livejournal.com/
> http://twitter.com/simonetripodi
> http://www.99soft.org/
>
>
>
> On Fri, Oct 14, 2011 at 2:24 PM, Maurizio Cucchiara
> <ma...@gmail.com> wrote:
>> I still no have preference, I would like to understand why we should add
>> optional work.
>> If there is a valid reason, why not?
>> I guess that the next answer is could jiira automatically do what xml is
>> able to do?
>>
>> Sent from my mobile device, so please excuse typos and brevity.
>>
>> Maurizio Cucchiara
>>
>> Il giorno 14/ott/2011 14.19, "Christian Grobmeier" <gr...@gmail.com> ha
>> scritto:
>> So your preference is to get rid of changes.xml?
>> Because changes would be visible on the site too....
>>
>>
>> On Fri, Oct 14, 2011 at 2:16 PM, Maurizio Cucchiara
>> <ma...@gmail.com> wrote:
>>> Jiira i...
>> --
>> http://www.grobmeier.de
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-u...
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [ognl] Make us of changes.xml
Posted by Simone Tripodi <si...@apache.org>.
see my previous message; just to give an example, take a look at the
[digester] reports:
http://commons.apache.org/digester/changes-report.html (changes.xml
introduced only in last release)
http://commons.apache.org/digester/jira-report.html (all jira issues)
does it make sense?
Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On Fri, Oct 14, 2011 at 2:24 PM, Maurizio Cucchiara
<ma...@gmail.com> wrote:
> I still no have preference, I would like to understand why we should add
> optional work.
> If there is a valid reason, why not?
> I guess that the next answer is could jiira automatically do what xml is
> able to do?
>
> Sent from my mobile device, so please excuse typos and brevity.
>
> Maurizio Cucchiara
>
> Il giorno 14/ott/2011 14.19, "Christian Grobmeier" <gr...@gmail.com> ha
> scritto:
> So your preference is to get rid of changes.xml?
> Because changes would be visible on the site too....
>
>
> On Fri, Oct 14, 2011 at 2:16 PM, Maurizio Cucchiara
> <ma...@gmail.com> wrote:
>> Jiira i...
> --
> http://www.grobmeier.de
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-u...
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [ognl] Make us of changes.xml
Posted by Maurizio Cucchiara <ma...@gmail.com>.
I still no have preference, I would like to understand why we should add
optional work.
If there is a valid reason, why not?
I guess that the next answer is could jiira automatically do what xml is
able to do?
Sent from my mobile device, so please excuse typos and brevity.
Maurizio Cucchiara
Il giorno 14/ott/2011 14.19, "Christian Grobmeier" <gr...@gmail.com> ha
scritto:
So your preference is to get rid of changes.xml?
Because changes would be visible on the site too....
On Fri, Oct 14, 2011 at 2:16 PM, Maurizio Cucchiara
<ma...@gmail.com> wrote:
> Jiira i...
--
http://www.grobmeier.de
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-u...
Re: [ognl] Make us of changes.xml
Posted by Christian Grobmeier <gr...@gmail.com>.
So your preference is to get rid of changes.xml?
Because changes would be visible on the site too....
On Fri, Oct 14, 2011 at 2:16 PM, Maurizio Cucchiara
<ma...@gmail.com> wrote:
> Jiira is also able to compute release notes.
>
> ATM I can't, I will post a link later.
>
> Sent from my mobile device, so please excuse typos and brevity.
>
> Maurizio Cucchiara
>
> Il giorno 14/ott/2011 13.34, "Christian Grobmeier" <gr...@gmail.com> ha
> scritto:
>
>> Hey guys,
>>
>> i would like to suggest we make consequent use of changes.xml.
>> Whatever we do, we should open an issue, fix the stuff, and then add a
>> comment to changes.xml. We do this in log4php and I feel it is very
>> good: you always can find the changes per issues (via Fisheye- just
>> check in with the OGNL- number in the comment). And of course it makes
>> it easy for the release notes and gives a good oversight for us.
>>
>> Any objections if we would do that from now on?
>>
>> I have added some missing entries before minutes - please check if I
>> mentioned the correct dev for this change.
>>
>> Thanks!
>> Christian
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
--
http://www.grobmeier.de
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [ognl] Make us of changes.xml
Posted by Maurizio Cucchiara <ma...@gmail.com>.
Jiira is also able to compute release notes.
ATM I can't, I will post a link later.
Sent from my mobile device, so please excuse typos and brevity.
Maurizio Cucchiara
Il giorno 14/ott/2011 13.34, "Christian Grobmeier" <gr...@gmail.com> ha
scritto:
> Hey guys,
>
> i would like to suggest we make consequent use of changes.xml.
> Whatever we do, we should open an issue, fix the stuff, and then add a
> comment to changes.xml. We do this in log4php and I feel it is very
> good: you always can find the changes per issues (via Fisheye- just
> check in with the OGNL- number in the comment). And of course it makes
> it easy for the release notes and gives a good oversight for us.
>
> Any objections if we would do that from now on?
>
> I have added some missing entries before minutes - please check if I
> mentioned the correct dev for this change.
>
> Thanks!
> Christian
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>