[Ns-developers] handling API changes

[Tom Henderson]

Tom Henderson wrote:
> We've had a lot of traffic recently on dealing with backward
> compatibility and API changes.  I'd like to suggest the following
> proposal, which is basically along the lines of solving this issue with
> documentation (sorry, Gustavo), because of the extra work of maintaining
> a backward compatibility layer.
> 
> I propose to put a file in the top level directory called "changes.txt".
>  This could also be kept as html to add more structure and make it more
> browsable (e.g. ns-2 CHANGES.html):
> http://www.isi.edu/nsnam/ns/CHANGES.html

Since HTML seemed to be easier to read and organize, I checked in a 
CHANGES.html file to the top-level directory.  I'd like to ask all 
developers who check in changes to the ns-3 API to add an entry to this 
file.  There are no strict policies for what needs to go in there; see 
the existing listings for the types of things that would be appropriate 
to list.

- Tom