Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.After some discussion with the team and in the public Slack channel, the following decision has been made:
- Sector 9.3 will be upgraded to Drupal core 9.4 in its next version as core 9.3 will be EOL by the end of the year. Next year this same branch will be upgraded to core 9.5 and supported through to D9's EOL in November 2023.
- No new 9.x branches will be created for Sector and so 9.3 will remain the stable D9 branch until EOL.
- New development will take place on the Sector 10.0.x branch which will aim to have a mostly functional release by the end of the year (contrib dependent).
Sector dev should be ready to upgrade to Drupal core 9.4.7 without issue, but any problems resulting from testing will be dealt with here.
Comments
Comment #3
dieuweBasic testing on the latest dev shows no issues.
However
drupal/admin_toolbarhas an 'unsupported' warning now so we'll sort that out before the next release (either in this ticket or another).Comment #4
xurizaemonThere are several other minor-looking updates which it'd be good to be proactive about - happy to move this to another issue if you want to keep this on 9.4.x target.
Is there something we could we do to help get those landed?
Antibot and Admin Toolbar don't look of concern for significant impact to me - AFAIK Sector doesn't have any "deep" integration with them.
Comment #7
dieuweI've made all of these updates and done some testing - changes to block class were probably the most extensive, but upgrading is smooth.
Planning to release this tomorrow as I have a few more things to test out.
Comment #8
dieuweComment #10
dieuweComment #11
dieuweCorrect title.
Comment #12
xurizaemonWhoa, is this the first release of Sector where the MAJOR.MINOR has deviated from matching core?
Sorry for missing this when it landed! I see @dieuwe proposed this in https://drupal.slack.com/archives/CR8D58SM6/p1664493072835669 1 Sept
I liked that only the patch version deviated from the required Drupal core version, and that
https://git.drupalcode.org/project/sector/-/blob/9.1.x/composer.json
https://git.drupalcode.org/project/sector/-/blob/9.2.x/composer.json
https://git.drupalcode.org/project/sector/-/blob/9.3.x/composer.json
(but now it doesn't)
If Sector's dependency on core increments by a minor version, I would expect that to result in a matching minor version update, in order to accurately carry through the semantics of core's version update. AFAIK that changed here.
Was this a conscious decision or have I misunderstood Sector's policy on tracking core versions? It really seems much simpler to be able to talk about "9.3" and have it mean the same thing.
Not asking for a reversal here :)
Comment #13
dieuweYes, you are right about this - at least the first 9.x version to deviate from the matching core pattern. The main reason I pushed for this was that we don't plan to do any actual further development on the 9.x release numbers.
We'd have ended up with 9.4 and 9.5 branches that would basically only ever going to get releases bumping up core versions + some contrib. In addition there is less than 12 months of official life left on Drupal 9.x and only about a month on Drupal 9.3.
With Drupal 10 we'll take stock of what Drupal's LTS plans are if they come to fruition and map out a release cycle plan that has ideally has a very stable LTS Sector branch and then an edge Sector branch which will keep pace with core better.
The current system simply led to us falling behind when busy as a hypothetical "Sector 9.4" is supposed to come with some deprecations and changes that we're stalling to Sector 10 in Jan-Mar next year.