[Development] dist/changes-x.y.z (was: Re: Branches)

[shane.kearns at accenture.com]

> If we're successful, this will be a non-issue once a few dozen entries
> have been added (unless everyone tries to append instead of inserting
> entries in some sorted order).

If you sort by bug ID, the recently reported bugs will be appended at the end.
So staging conflicts happen mostly for the high priority bugs.

> > I'd suggest that bug fixes should not touch the changes file, only
> new
> > features.
>
> That would be a change from previous practice (changes-4.8.x, say; I've
> understood changes-5.0.0 to be a one-time glitch), which probably
> didn't include all, but at least some bug fixes.
>
We bulk added them using git log and searching for "task-number:".
If they are added at the same time as the bug fix, staging conflicts will happen.


This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited.

Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy.

______________________________________________________________________________________

www.accenture.com