Problem/Motivation

#3206490: Make the module D9 compatible was a crucial step forward, and now the dev branch is Drupal 9 compatible.

But as a developer, I want to use tagged releases.

Proposed resolution

Create a new release. :)

Remaining tasks

User interface changes

API changes

Data model changes

Comments

huzooka created an issue. See original summary.

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented

https://twitter.com/wimleers/status/1446383289305083925 😊 🙏

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented

Almost two weeks without response … I'm going to use my maintainer powers to tag a release. I hope you forgive me, @jofitz.

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented

I see 3a3174a204653d9ae6b22c40f949bf415c4c9457 (for #2971399: Missing "source_module property" annotation) was tagged as version 1.1, but never released. Dates back to May 16, 2018.

I'm just going to tag 664a31037626112109e2c9c7888f3644d5cbea4f as version 1.2 then.

Wim Leers credited jofitz.

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented
Status: Active » Fixed

https://www.drupal.org/project/nodequeue_migrate/releases/8.x-1.2

Status: Fixed » Closed (fixed)

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