- Issue created by @gareth.poole
-
gareth.poole β
committed c871f760 on 10.0.x
Issue #3376974: Namespace change update docs
-
gareth.poole β
committed c871f760 on 10.0.x
- π³πΏNew Zealand dieuwe Auckland, NZ
I think this is better off being:
drupal/sector
.Then we open a ticket with the infrastructure team to change this project over from a "profile" to a "general" project.
-
stewest β
committed 27783d20 on 10.0.x
Issue #3376974: Namespace change
-
stewest β
committed 27783d20 on 10.0.x
-
stewest β
committed 27783d20 on feat/account-and-password-settings
Issue #3376974: Namespace change
-
stewest β
committed 27783d20 on feat/account-and-password-settings
- Status changed to Needs work
9 months ago 3:33am 21 September 2023 - π³πΏNew Zealand dieuwe Auckland, NZ
I'm not sure about those commits referencing this ticket, they are not related. I have gone through and updated the namespace manually in the 10.0.x branch and forgot to reference this ticket, so it is done.
I have opened an infra ticket in the composer queue to have us moved to a general project: https://www.drupal.org/project/project_composer/issues/3388717 π Convert the Sector Distribution to a general project Fixed
Once that has been approved we can update all the documentation, READMEs, and composer requires.
Namespace for the template is:
drupal/sector_project_template
Namespace for the profile is:
drupal/sector
- Status changed to Fixed
9 months ago 3:59am 25 September 2023 - π³πΏNew Zealand dieuwe Auckland, NZ
Namespace change has been confirmed, likely nothing else to do on the Sector end, other than to include this change in all future release notes.
Automatically closed - issue fixed for 2 weeks with no activity.