Re: Lost changelogs

On 2 May 2014, at 13:28, ida277 wrote:

> Eric Steele wrote
>> We tend to not have up to date changelog entries for older branches 
>> in
>> master.
>
> Which certainly wouldn't be much of a problem for versions that are 
> not
> supported anymore, but as it happened with p.a.portlets there were 
> bugfixes
> lost, which concerned all branches. And we do want support all of them
> still, non?
>
> Eric Steele wrote
>> I do try to keep those updated across branches, but with 200+
>> packages, it's a nightmare.
>
> Oh no, I didn't mean to critize you by any means, that would never 
> come up
> to my mind, quite the contrary I am very happy Plone has such 
> cool-blooded
> (in terms of staying calm, even if the server burns), very responsible
> release-managers doing an awesome job, imho.
> I just wanted to emphasize the idea of pull-request-reviewers taking 
> more
> care of these things and if such a concept exists already, so my quest 
> is
> actually how it is decided who is granted to merge pull-requests, or 
> can
> just any core-committer do that on any package (meaning the 
> convention, not
> the actual repo-permissions) ?
>
> Eric Steele wrote
>> If you look at releases for the 2.2.x
>> branch, you'll see the entries are there.
>> https://pypi.python.org/pypi/plone.app.discussion/2.2.12
>
> True. Yet, changelogs are ment to be complete always and how would I 
> know
> something's actually missing, if I just had a look at CHANGES.txt of 
> the
> newest version of a package. I hope it is not expected to do extra 
> research
> to find out about that.
>
> All in all I just want to deal with the situation in a constructive 
> way and
> find out how to improve.
> I am aware that major changes come along with major pain and would 
> like to
> help also to ease that.
>
> -ida


Yeah, sorry. I didn't mean to come off as defensive about it. It's a 
part of the procedure that sucks and I'd love to see it fixed.

Part of my release scripts check the changelog to get entries for the 
next release. I'll see about adding one to make sure previous releases 
have entries in the current change log as well. That'll cover new ones 
as I cut future releases, but I'd certainly appreciate help updating 
them now so that the process for the next release of 5.0 isn't horrible.

Eric

------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.  Get 
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs