OpenJDK (Java) migrating from Mercurial?

[Bob Hood]

On 11/18/2019 7:17 AM, Malcolm Matalka wrote:
> There is also "safety in numbers" when it comes to git.  Meanwhile, us
> in the hg world can't even agree on the best way to make a branch.

Why must there be a "best way"?  You've had several approaches laid out for 
you in this thread with regard to Mercurial--certainly more than git 
offers--and yet you can't accept it because there are /too many/choices?  
Choose the approach that best works for your particular situation.  How do you 
know which that is?  You'll have to discover that for yourself.  We cannot 
possibly know the depth and details of your day-to-day operation, and what 
approach would represent a "best practice" for it.

You're the CTO: You are the one who /provides/the guard rails.  You're going 
to have to skirt a few edges before you can figure out where they need to be 
placed.

I know whereof I speak:  I'm Director of Engineering.  It's part of the job.  
For my situation, using named branches provides us with clear demarcation of 
existing releases, and work-in-progress, of a public-facing commercial 
product.  Somebody else may have a crew or a project more suited to using 
bookmarks, hence that would be the better way for them to manage.Mercurial 
gives you the flexibility to fit your situation, as long as y/ou/ can define it.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20191118/34d9fa78/attachment-0002.html>