Re: Move change log into separate file?

You could still do that in the change log file. We could keep the change log section and link to the separate change log file.

/Adam

On 2017-09-08 18:26, Daniel Burnett wrote:
Hmm, I liked the fact that searching for old or deprecated APIs pulled up something in the change log, because it was then easy to see by the date *which* version I should be looking at.  But I'm okay with it if others are.  Cullen has had concerns in the past with what's in the change log, so it would be good to hear from him here.


On Fri, Sep 8, 2017 at 9:49 AM, Adam Bergkvist <adam.bergkvist@ericsson.com<mailto:adam.bergkvist@ericsson.com>> wrote:
Hi

I propose that we move the change log into a separate file. Perhaps a
simple txt or md. I don't think it's that common to have it in the spec.
The current setup makes it harder to search the spec for old and
deprecated API. You always get a few hits in the change log section
where an old method is mentioned. And it wouldn't hurt to make  the
document a few lines shorter. :)

/Adam