Problem/Motivation

Set default branch to 3.0.x in GitLab - confusing and error-prone otherwise when creating a MR.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Comments

anybody created an issue. See original summary.

anybody’s picture

anybody
Primary language German
Location Porta Westfalica
commented
Title: Set default branch to 30..x in GitLab » Set default branch to 3.0.x in GitLab
Issue summary: View changes
anybody’s picture

anybody
Primary language German
Location Porta Westfalica
commented
Issue summary: View changes
anybody’s picture

anybody
Primary language German
Location Porta Westfalica
commented

And I'm wondering why no release is shown on the module page?
Composer already uses ^3!

joegl’s picture

joegl commented

Yea, I'm curious what's going on. I saw this pop up when running `composer outdated` but there is no 3.0.0 release, and the 3.0.1 release is marked as "beta" and "unsupported", and there's also a 3.0.1-beta1 release made after the 3.0.1 release.

bbu23’s picture

bbu23
Location 🇪🇺🇪🇺🇪🇺
commented
Status: Active » Fixed

I changed the default branch, but can't do a dev release for it since it already has releases attached to it.
Dev releases are not mandatory to exist, but they're very helpful. _nk must've just forgotten to create one prior to other releases.
We'll discuss it together with _nk, but most probably we'd have to create a new branch (e.g. 3.x) in order to have a dev release.
Until then, this issue is solved. Thanks

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

anybody’s picture

anybody
Primary language German
Location Porta Westfalica
commented

Thanks @bbu23 yes totally fine. I personally like 4.x style more than 4.0.x in general.

My vote: Create a 14.x branch to sync it with the parent library version. That works very well for us in other similar projects like Photoswipe to also keep compatibility with the parent lib. 14.x would solve both :)

anybody’s picture

anybody
Primary language German
Location Porta Westfalica
commented

PS: Gitlab dev branch should always be latest, where development happens. That's unrelated to the release thing.

bbu23’s picture

bbu23
Location 🇪🇺🇪🇺🇪🇺
commented

Just an update and a correction to my previous comment: it seems the development release already existed, it was just a matter of marking the "3*" releases as "supported". Now both the dev and the beta releases should be available.

joegl’s picture

joegl commented

I'm still curious if the 3.0.1 release is a beta release or not. The 3.0.1 release notes say "beta version" and an actual 3.0.1-beta1 beta release was tagged and created 10 minutes after the 3.0.1 release. If it is a beta release, the 3.0.1 stable release should probably be unpublished.

bbu23’s picture

bbu23
Location 🇪🇺🇪🇺🇪🇺
commented

I will have to confirm with _nk. But if that's the case, we cannot "unpublish" individual releases. We can only disable full support at "3.0.x" level.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.