Mailing-List: contact dev-help@creadur.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@creadur.apache.org
MIME-Version: 1.0
In-Reply-To: <56098E62.1000006@apache.org>
References: <1304609838.8124.1443358993163.JavaMail.jenkins@crius>
	<993870462.8140.1443366219644.JavaMail.jenkins@crius>
	<56082DE6.3080709@apache.org>
	<CAF8HOZJLt1uCa0g83h96OFmXs4SXtjf+bCkCUW2d7vpJ54qA6Q@mail.gmail.com>
	<CAOGo0VZKhSupCLO82MVRsPaZ867X75f6nGHYUwUc4b+mEBQ3rQ@mail.gmail.com>
	<56098E62.1000006@apache.org>
Date: Mon, 28 Sep 2015 20:09:08 +0100
Message-ID: 
 <CAOGo0VaZSGUtSTH4AoFykRdpjcGWFchNDhBkvtOc1HKvOys-Ug@mail.gmail.com>
Subject: Re: Build failed in Jenkins: Creadur-Rat #290 / RAT-208 / usage of
 changes.xml
From: sebb <sebbaz@gmail.com>
To: dev@creadur.apache.org
Content-Type: text/plain; charset=UTF-8

On 28 September 2015 at 20:00, P. Ottlinger <pottlinger@apache.org> wrote:
> Hi *,
>
> Am 28.09.2015 um 20:29 schrieb sebb:
>> It can be used to create the changes list on the website as well as
>> RELEASE_NOTES.
>>
>> It is how Commons does it.
>
> I'm in favour of the changes plugin as well, but how and where do we
> integrate the changes of the last releases?
>
>
> The changes.xml were not touched for a while:
>
> * https://svn.apache.org/repos/asf/creadur/rat/trunk/src/changes/changes.xml
> Last change: 2012-10-19 21:10:33 +0200
>
> *
> https://svn.apache.org/repos/asf/creadur/rat/trunk/apache-rat-plugin/src/changes/changes.xml
> Last change (before Jochens recent commit): 2012-10-19 21:10:33 +0200
>
> Maybe we should start improving on that after 0.12 is out of the door.

In which case it will probably be left until 0.14 ... etc.

I suggest at least putting the changes for 0.12 in the file and using
that for the RN.

We can add dummy entries (TBA) for the missing versions for now. I can do that.
At least then we would not be any worse off.

> Cheers,
> Phil