Re: [release] Boost 1.85.0

From: Marshall Clow (mclow.lists_at_[hidden])
Date: 2024-05-23 23:12:47

On May 23, 2024, at 3:04 PM, Andrey Semashev via Boost <boost_at_[hidden]> wrote:
> 
> On 5/21/24 10:08, Andrey Semashev wrote:
>> On 4/15/24 21:02, Marshall Clow via Boost wrote:
>>> Release 1.85.0 of the Boost C++ Libraries is now available.
>>> 
>>> These open-source libraries work well with the C++ Standard Library,
>>> and are usable across a broad spectrum of applications. The Boost
>>> license encourages both commercial and non-commercial use.
>>> 
>>> This release contains two new libraries:
>>> 	* Boost.Charconv: A high quality implementation of <charconv> in C++11, from Matt Borland.
>>> 	* Boost.Scope: A collection of scope guard utilities and a unique_resource wrapper, from Andrey Semashev.
>>> 
>>> The release also contains numerous enhancements and bug fixes for existing libraries.
>>> 
>>> For details, including download links, see
>>> <http://www.boost.org/users/news/version_1.85.0>
>>> 
>>> You can also download directly from:
>>> <https://boostorg.jfrog.io/artifactory/main/release/1.85.0/>
>>> 
>>> To install this release on your system, see
>>> <http://www.boost.org/doc/libs/release/more/getting_started/index.html>
>>> 
>>> Thanks to everyone who participated in this release.
>> 
>> For Boost.Log, the boost-1.85.0 tag is pointing to the wrong commit:
>> 
>> e79cfd841f90e4f0d7f4729440e7ef92ef7495da
>> 
>> It should point to:
>> 
>> 2d932ddcb5b05a9b2cc0a9df2d8a6ff88883f2b3
>> 
>> which is the last commit in the series that were merged to master (with
>> permission) right before the release. I can see the changes in that
>> commit are present in the 1.85.0 .tar.bz2 archive from jfrog, and are
>> also present on the website.
> 
> Ping? Should I fix the tag myself?

Sorry - I've been head down in some other stuff.

But I’ve been reading the git-tag documentation on https://git-scm.com/docs/git-tag#:~:text=If%20you%20got%20the%20wrong,you%20have%20the%20new%20version.

Where it talks about “fixing” a tag.
Have you read that?

> # On Re-tagging
> What should you do when you tag a wrong commit and you would want to re-tag?
> 
> If you never pushed anything out, just re-tag it. Use "-f" to replace the old one. And you’re done.
> 
> But if you have pushed things out (or others could just read your repository directly), then others will have already seen the old tag. In that case you can do one of two things:
> 
> The sane thing. Just admit you screwed up, and use a different name. Others have already seen one tag-name, and if you keep the same name, you may be in the situation that two people both have "version X", but they actually have different "X"'s. So just call it "X.1" and be done with it.
> 
> The insane thing. You really want to call the new version "X" too, even though others have already seen the old one. So just use git tag -f again, as if you hadn’t already published the old one.

— Marshall