Re: Lost changelogs

We tend to not have up to date changelog entries for older branches in 
master. I do try to keep those updated across branches, but with 200+ 
packages, it's a nightmare. 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

Eric

On 2 May 2014, at 12:43, ida277 wrote:

> Nathan Van Gheem-3 wrote
>> Can you share an example of lost changelogs?
>
> Right now, I stumbled over plone.app.discussion, which I cannot make 
> to work
> with Plone-4.3.3. The versions.cfg pins p.a.discussion to 2.2.12, so I
> thought I have a look at the product's site on PyPI, to see what has 
> changed
> and noticed the missing entry for 2.2.12.
>
> Same goes for p.a.portlets, which I just reviewed with kind guidance 
> of
> David Glick, synchronizing commited bugfixes between three separated
> branches and restoring the missing logs. Still it's not clear, how
> future-commits affecting several branches will stay in sync.
>
> And there was another one I which I cannot recall right now, but I'll 
> add it
> here, when it hits me again.
>
>
> Nathan Van Gheem-3 wrote
>> Policy is usually yes, for every change, put an entry in.
>
> Ok, thanks for confirming.
>
> Leaves up the quest, why it's not happening and how we can ensure 
> proper
> logs for the future. To me, this concerns the people merging 
> pull-requests,
> and if noticing something's wrong, to educate the comitter about it 
> (besides
> of the usual official note in a doc somewhere, which probably exists
> already), would you see that likely?
>
> To me a concept of a responsible person and a seconder, could be of 
> help I
> think, and aren't product-owners ment to hold that role?
> As a fairly fresh core-comitter, I'm just asking to get more clarity, 
> maybe
> the approach is actually less hierachic/person-centric.
>
> Regards, ida
>
> On Fri, May 2, 2014, at 07:04 AM, ida277 wrote:
>> Hej everybody,
>>
>> I'm lately experiencing with quite a few core-packages, that parts of 
>> the
>> changelogs are missing, how can we avoid that?
>>
>> Respectively I'd assume package-owners are responsible for proper
>> releases
>> and there is a competent seconder, if the owner can't be available.
>> Please
>> forgive me, if I have overseen something obvious, but what is 
>> actually
>> our
>> policy about that?
>>
>> Additionally I'd expect a changelog-entry to be equivalent with the
>> corresponding pull-request-comment, yet often they don't show up in 
>> GIT's
>> history, or not in a way that I can easily find matching comments, 
>> how do
>> you (all of ya Ploners) think about that and what do you think should 
>> be
>> our
>> "best-practice"?
>>
>> Curious about enlightnings and with best regards
>> Ida
>>
>>
>>
>> --
>> View this message in context:
>> http://plone.293351.n2.nabble.com/Lost-changelogs-tp7571208.html
>> Sent from the Core Developers mailing list archive at Nabble.com.
>>
>> ------------------------------------------------------------------------------
>> "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
>> _______________________________________________
>> Plone-developers mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/plone-developers
>
> ------------------------------------------------------------------------------
> "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
> _______________________________________________
> Plone-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/plone-developers
>
>
>
>
>
> --
> View this message in context: 
> http://plone.293351.n2.nabble.com/Lost-changelogs-tp7571208p7571212.html
> Sent from the Core Developers mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> "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
> _______________________________________________
> Plone-developers mailing list
> Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/plone-developers

------------------------------------------------------------------------------
"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

_______________________________________________
Plone-developers mailing list
Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/plone-developers