Release tags request..
B2 is doing it's own "out of band" (aka independent) releases. In order to avoid confusion.. Can the Boost release process please avoid tagging the build subrepo with the Boost release tags from now on? -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net
On Sun, Jun 23, 2019 at 8:15 PM Rene Rivera via Boost <boost@lists.boost.org> wrote:
B2 is doing it's own "out of band" (aka independent) releases. In order to avoid confusion.. Can the Boost release process please avoid tagging the build subrepo with the Boost release tags from now on?
I think it's important to have Boost release tags in every Boost submodule. Otherwise it's not possible to checkout a given Boost release from git.
On Sun, Jun 23, 2019 at 12:18 PM Andrey Semashev <andrey.semashev@gmail.com> wrote:
On Sun, Jun 23, 2019 at 8:15 PM Rene Rivera via Boost <boost@lists.boost.org> wrote:
B2 is doing it's own "out of band" (aka independent) releases. In order
to
avoid confusion.. Can the Boost release process please avoid tagging the build subrepo with the Boost release tags from now on?
I think it's important to have Boost release tags in every Boost submodule. Otherwise it's not possible to checkout a given Boost release from git.
Yes it is possible. The root repo has the release tag. Which if you get the submodules will have the appropriate commit hashes to fetch. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net
On Sun, Jun 23, 2019 at 1:15 PM Rene Rivera wrote:
B2 is doing it's own "out of band" (aka independent) releases. In order to avoid confusion.. Can the Boost release process please avoid tagging the build subrepo with the Boost release tags from now on?
B2 could also do its own "out of band" (aka independent) releases from a repository not under the boostorg organization, to avoid confusion with what users have come to expect with submodules (library and tools) under the boostorg organization (aka release tags corresponding to the Boost release). Glen
On Sun, Jun 23, 2019 at 12:36 PM Glen Fernandes <glen.fernandes@gmail.com> wrote:
On Sun, Jun 23, 2019 at 1:15 PM Rene Rivera wrote:
B2 is doing it's own "out of band" (aka independent) releases. In order
to
avoid confusion.. Can the Boost release process please avoid tagging the build subrepo with the Boost release tags from now on?
B2 could also do its own "out of band" (aka independent) releases from a repository not under the boostorg organization, to avoid confusion with what users have come to expect with submodules (library and tools) under the boostorg organization (aka release tags corresponding to the Boost release).
Yes, I brought that up last year with the other B2 owners. They rejected that approach. But do note that under that approach Boost would not be permitted to add the Boost release tags anyway. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net
On 24/06/2019 05:15, Rene Rivera wrote:
B2 is doing it's own "out of band" (aka independent) releases. In order to avoid confusion.. Can the Boost release process please avoid tagging the build subrepo with the Boost release tags from now on?
As a user of Boost, I find it very convenient that boost-X.YY tags are added to the submodules to show which commit tree is in each release. I would be annoyed if this were removed. I don't see how this causes confusion. Just use some different prefix for your own independent releases.
On Sun, Jun 23, 2019 at 7:11 PM Gavin Lambert via Boost < boost@lists.boost.org> wrote:
On 24/06/2019 05:15, Rene Rivera wrote:
B2 is doing it's own "out of band" (aka independent) releases. In order to avoid confusion.. Can the Boost release process please avoid tagging the build subrepo with the Boost release tags from now on?
As a user of Boost, I find it very convenient that boost-X.YY tags are added to the submodules to show which commit tree is in each release.
I would be annoyed if this were removed.
I don't see how this causes confusion. Just use some different prefix for your own independent releases.
The confusion is when looking at <https://github.com/boostorg/build/releases> and seeing "unofficial" releases. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net
On Sun, Jun 23, 2019 at 8:19 PM Rene Rivera wrote:
The confusion is when looking at <https://github.com/boostorg/build/releases> and seeing "unofficial" releases.
To the user that expects to find a 1.X.Y tag when looking at boostorg/<Z> corresponding to the Boost 1.X.Y release, the "4.0.0" is the unofficial, less meaningful, and confusing tag. These are the majority of the users. What the concern over this issue tells me is that non-Boost users that care about Boost.Build are being done a disservice by being forced to use boostorg.org/build repository if the "official" Boost.Build has to diverge in any way (including release numbering scheme). i.e. These users are probably best served by "official" B2 living in <organization>/b2, with boostorg/build just a fork of that repository. Glen
On 24/06/2019 12:18, Rene Rivera wrote:
The confusion is when looking at <https://github.com/boostorg/build/releases> and seeing "unofficial" releases.
Then upvote this request to fix the GitHub UI, or talk to their support directly: https://github.community/t5/How-to-use-Git-and-GitHub/Tag-without-release/m-... The fact that GitHub is interpreting tags incorrectly is not a reason to stop creating them.
participants (4)
-
Andrey Semashev -
Gavin Lambert -
Glen Fernandes -
Rene Rivera