2015-03-11 12:35 AEST by Arthur Barrett - Unpublished commits.

This is an enhancement Tony and I talked about for a LOOOOONG time.  

I just discovered there is no record of it here, so I'm adding it now.  Better late than never.

The idea is that the developer wants to 'commit' some code changes, so they can try some changes that 
may 'break' the code.  If they do 'break' the code they want to rollback the changes to their last 
'unpublished' commit.  But they don't want other developers accidentally using the new code, because it's 
not ready for prime time.  

The 'Essential CVS' book talks about 'flying fish' branching for this purpose.  Do these types of 
development exercises on short lived branches.  But there is an administrative overhead with that which 
'unpublished commits' would avoid.

But there are a lot of implementation questions:
- do the unpublished commits go to the server, or remain on the local PC?
- in unreserved mode, can more than one developer commit a (conflicting) unpublished commit
- when the final commit is done, are the 'waypoints' also committed?
- do we limit the number of 'unpublished' commits before requiring a published commit (e.g.: one)
- can you perform an unpublished commit if your local revision is out of date (do you require an 
update/conflict resolution first)