Re: cl-defstruct-based package.el, now with ert tests and no external tar!

[Sebastian Wiesner]

2013/6/5 Dmitry Gutov <address@hidden>:
> Daniel Hackney <address@hidden> writes:
>>> You can start with ChangeLog files. When writing a changelog entry,
>>> one usually briefly describes and sometimes justifies the mechanical
>>> transformations being performed on the code, and it helps other people
>>> understand the changes.
>>
>> Since it is a complete refactoring, what should I say? Should I include
>> a line for each new or changed function
>
> I think so: http://www.gnu.org/prep/standards/html_node/Change-Logs.html
>
>>> I see you've also already started on NEWS entries.
>>
>> How does it look so far? Any suggestions on how to improve it?
>
> Actually, I'm not entirely sure the NEWS entries are appropriate in this
> case.
>
> Compare: "file named NEWS which contains a list of user-visible changes
> worth mentioning"
> (http://www.gnu.org/prep/standards/html_node/NEWS-File.html).
>
> and
>
> "User-facing commands have not changed and existing archives and files
> will continue to work as before;"

The API *has* changed.  We (that is, the Carton team [1]) “use” this
API.  We need to port Carton to the new API, and NEWS entries
explaining the changes would help.

[1]: https://github.com/rejeep/carton