Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4853AC8D.3010002@apache.org>
Date: Sat, 14 Jun 2008 12:33:33 +0100
From: Mark Thomas <markt@apache.org>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: Tomcat Developers List <dev@tomcat.apache.org>
Subject: Re: svn commit: r667604 -
 /tomcat/trunk/java/org/apache/catalina/session/StandardSession.java
References: <20080613174351.CF85B2388A0A@eris.apache.org>
 <4852B920.4050306@hanik.com> <4852C252.9030902@apache.org>
 <4852C975.70106@hanik.com> <48530F6D.7010709@joedog.org>
 <48531934.3080208@rowe-clan.net>
In-Reply-To: <48531934.3080208@rowe-clan.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit


William A. Rowe, Jr. wrote:
> 
> Tim Funk wrote:
>> Since there was never a release from trunk - there really isn't a 
>> change log. When trunk is released as a new branch it should have a 
>> RELEASE-NOTES which highlight why its a different branch but 
>> maintaining change log for an unreleased version doesn't make much 
>> sense to me.
> 
> Hmmm - perhaps the simple fact that it's a code base is enough to warrant
> a change log against the last released flavor?

Nearly all of the changes in trunk get ported to 6.0.x where the change log 
is kept up to date.

I agree changes that aren't going to be ported should be documented (code 
clean-up, conversion to generics, etc should be summarised under a single 
entry). That really needs a diff between the two to make sure we capture 
everything. I just kicked such a diff off to see what it looks like.

Mark


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org