[Unison-hackers] Re: a common patch set - first attempt [repost]

[Zvezdan Petkovic]

My point of view is much simpler than the four proposed options.
There is really only one option.
If you call something _stable_, then it _must_ be stable.
That means, if the stability bug is discovered and fixed, it should be
checked in the stable branch in CVS (or subversion in your case).
No ifs or buts here.

You call 2.10.2 stable, make the branch for it and keep it stable.
Whenever you check in something, run a script that extracts the source
into a .tar.gz file so that package and port systems can pick it up.

Regarding the snapshot (beta), it's a snapshot of a developer version.
It shouldn't be updated.  It's just a snapshot of development and people
who use it like to live on the edge.  Their choice.

Once the developer version is brought into some acceptably stable
condition it should be tested and then proclaimed stable.
The new development branch should be opened during the testing, and when
the new stable is promoted a snapshot of the development branch can be
made as a new snapshot.

	Zvezdan Petkovic