Problem/Motivation

The 8.x-2.x branch has no releases. This makes a harder to contribute patches, since there is no version available for the latest 8.x-2.x branch when uploading a patch file.

Proposed resolution

Add a 8.x-2.x dev release

Comments

idebr created an issue. See original summary.

sjerdo’s picture

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.

idebr’s picture

Version: 2.2.3 » 2.6.x-dev
idebr’s picture

Status: Fixed » Needs work

2.6.x does not match the semantic version expected by drupal.org infrastructure. As a result, no development pipeline is reported on the project page: https://www.drupal.org/project/cookie_content_blocker

The expected branch structure is:
2.x (<-- default branch and dev release, also supports legacy branch naming: 8.x-2.x)
2.6.x (latest release branch)

sjerdo’s picture

Ok, I didn't want to remove branch 8.x-2.x, but I had to, to publish 2.x-dev
Drupal.org blocked me from publishing a 8.x-2.x-dev version

Open MR destination branches are updated

https://www.drupal.org/project/cookie_content_blocker/releases/2.x-dev

sjerdo’s picture

Status: Needs work » Fixed

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.

idebr’s picture

Title: Add 8.x-2.x dev release » Add 2.x dev release
Version: 2.6.x-dev » 2.x-dev

https://www.drupal.org/project/cookie_content_blocker now displays dev releases for 2.4.2 and 2.5.0, but not 2.6.1. I suspect this is due to https://www.drupal.org/project/cookie_content_blocker/releases/2.6.x-dev

Can this release be deleted or unpublished? https://www.drupal.org/project/cookie_content_blocker/releases/2.6.x-dev

sjerdo’s picture

Unfortunately, I am not able to delete version 2.6.x-dev

Status: Fixed » Closed (fixed)

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