draft NEWS, licensing clarification, release plan

* NEWS

With help from Tõivo, I have prepared NEWS for the imminent (perhaps
even this month) 2.51.4 release.

(I had meant to put it on a feature branch in my fork, but somehow git
pushed it to the main repo, and I can't force-push the old ref, so I'm
just going with it.  I intend to normally make changes via the PR
process.)

So please have a look and tell me what's wrong/missing, including
replacement/new text I can use.

  https://github.com/bcpierce00/unison/blob/master/doc/changes.tex

* LICENSING

Prompted by some offlist discussions, I've added a description of
licensing.  This is meant to say how it is and has been, for people who
don't have a habit of listening to Free Software licensing podcasts for
fun, and is not meant to be a policy change.

I'd specifically like a nod (or objection) from Benjamin and everyone
else is of course welcome to comment.

https://github.com/bcpierce00/unison/pull/536
https://github.com/bcpierce00/unison/pull/536/commits/6b21600c75fa0a962b38a8216b2282d5732fb5b3

* RELEASE PLAN

  - a few manual edits (e.g. mailinglist info is old) that I'll just
    amke directly

  - merge the licensing PR or decide not to

  - tag an RC and ask for testing on unison-users@
    (If you are on hackers and not users, let me know, so I can send
    that request here too.)

  - adjust version number in manual and tag release

  - As long as this heads for happening soonish, I would like to avoid
    merging anything that isn't a bugfix relative to 2.51.3 or a doc
    fix.

_______________________________________________
Unison-hackers mailing list
[email protected]
https://LISTS.SEAS.UPENN.EDU/mailman/listinfo/unison-hackers

-----BEGIN PGP SIGNATURE-----

iF0EARECAB0WIQS7wyAjWilQwVHG9Vsf2nroCY7WDgUCYMfZLgAKCRAf2nroCY7W
DgOcAJ9f8t0DOShcdnkRaolAtW9g3HSjoQCeI4zFcWm1Zc0QeUZQhq1c23dR7ig=
=jTVe
-----END PGP SIGNATURE-----