Problem/Motivation
In order to #3267267: [Meta] Tasks to deprecate RDF we need a subtree split from core and a stable release. Lets work on that here.
Steps to reproduce
na
Proposed resolution
Create a subtree split
Investigate if we need a orphan branch or we can just add history on top
Make sure tests work
Make sure including the module in core works
Mark older branches and releases unsupported if needed
Profit.
Remaining tasks
Create a subtree split
Investigate if we need a orphan branch or we can just add history on top
Make sure tests work
Make sure including the module in core works
Mark older branches and releases unsupported if needed
User interface changes
None
API changes
n.a.
Data model changes
n.a.
Release notes snippet
tbd
Issue fork rdf-3306737
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
bbralaRetarget to 1.x
Comment #4
bbralaOk, i accidentally screwed up the 1.x branch. I've created a 2.x branch in the main module and did the following:
Then i tested by doing the following (this is part of my local install script for development :x):
I tested if RDF stuff came up in the code as expected. It did.
Also i ran tests in the contrib install.
So it seems the 2.x branch is fully working as expected :)
Comment #5
bbralaComment #7
bbralaComment #8
bbralaComment #10
bbralaWell, the mr is confused. Here is the link to the test on the 2.x branch: pift-ci-job/2464169
Comment #11
phenaproximaI checked out the 2.x branch locally, into my checkout of Drupal core 10.1.x HEAD, and ran all tests. They passed 🎉
One thing I notice: composer.json defines a dependency on core
^9 || ^10. But rdf.info.yml is more specific:^9.5 || ^10. We should probably drop the constraint from composer.json entirely and rely on the info file, no? Or at least we should make sure these match. (Really, couldn't we just remove composer.json entirely? There doesn't appear to be anything in there that packages.drupal.org won't put there automatically.)But, while I'm thinking about it: why would we ever want people to install this module on Drupal 9, any version? Won't it conflict with the core RDF module? Should we change the constraints to
^10only?Comment #12
bbralaYeah I agree, but I need the composer.json for testbot to be able to do anything I think and I think to be able to require it as a path repo? Rather have none though, but rather remove it from a follow up.
In the end the requirements are based on drupals composer repo which uses the info file for core requirements.
So, I'll at least change it to be fully consistent and open a follow-up to remove.
Comment #13
bbralaHmm, adding to that. We need a 9.4 pr 9.5 also, since that makes the upgrade a lot easier. You can upgrade the module before upgrading to 10. Which is helpfull.
Comment #15
bbralaCommitted and released 2.0.0.