Request for comments about using named branches to track releases

[Arne Babenhauserheide]

Steve - Gadget Barnes <gadgetsteve at hotmail.com> writes:

> On 25/08/2017 03:37, Mario Castelán Castro wrote:
>>   it can not be generated at
>> compile-time by calling Mercurial.
>
> Why not? It is reasonably usual in many VCSs and Development Work Cycles 
> to do exactly that for compiled languages and for interpreted languages 
> such as python to have a "Publish" or "Release" step that uses the VCS 
> to update/create a version information file of some form that provides 
> the information.

Having had to build git-projects which I cloned with hg-git, and having
experienced projects which switched from CVS to SVN or SVN to HG and
suddenly could not build their old versions anymore, I came to cherish
VCS-independent build systems, so I understand the request.

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein
ohne es zu merken
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://www.mercurial-scm.org/pipermail/mercurial/attachments/20170827/f0c34e2b/attachment.sig>