-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drupal.org hates our release tags #1225
Comments
https://www.drupal.org/node/1015226 for reference |
If something is on Drupal.org, composer can find it with the 'Drupal/' prefix so packages is no longer necessary unless I'm missing another use for it |
Looks like we need to have our 1.0.0 release tag called 6.1.0 |
Oh no, sorry that is for the deGov distribution. Mea culpa |
maybe the new semantic versioning proposal from TAG will fix this? |
This should be a moot point because Drupal.org now actually uses semantic versioning for Drupal 9+. As long as we stick to 'standard' semantic versioning, we should be alright. I'd wait until we actually push stuff over to Drupal.org before closing the ticket though. |
There are 2 things that need to happen
I'm thinking that synchronizing is the simplest for the community as they don't need to learn anything new. Not sure how we might get Github actions to do that for us without too much trouble. Another question becomes how we can incorporate any patches from the Drupal community back into the code. Sidenote: @dannylamb can you add me to the JSON-LD drupal project and whatever other ones are up there. I pushed out the |
TAG is, after discussion with the tech call, going to rename branches to align with semantic versioning. |
Although at some point I read that you could name a tag anything, it's looking like if I want the release to show up on Drupal.org, it has to be renamed to 8.x-1.0 (no 1.0.0) and be based off of a non-master branch (I specifically chose master as the stable branch).
I'm not sure how best to proceed. Those tags must remain for packagist and our current install. I'm thinking i'll splice off branches from the tagged commits with different names, and release off of those on Drupal.org.
The text was updated successfully, but these errors were encountered: