Now that 8.0.x is branched, we should make sure people are using it instead of 8.x. If you notice someone using 8.x, think about why, and what would nudge them to use 8.x; leave a comment here or update the issue summary.

Here are some ideas, in rough order of ease/priority:

  1. [DONE] Announce on various channels, like https://groups.drupal.org/core. [Core post made: https://groups.drupal.org/node/436178]
  2. Documentation - #586146-115: [policy, no patch] Decide if and how to implement semantic versioning for Drupal 8.x requests a change notice.
  3. [done] Git - drumm pushed http://cgit.drupalcode.org/drupal/commit/?h=8.x&id=cffa8d0a8258c88c4e079... to introduce the new branch. This is not hugely noticeable however... see below...
  4. [done] Drupal.org - delete the release node so 8.x-dev is no longer available for issues. [done]
  5. [done] Git - Deleting the branch will force people to switch branches, breaking git pull until they switch. Release node must be delete first. [Wait until after next alpha, as announced in Core post.]

Comments

jhodgdon’s picture

jhodgdon
she/her
Primary language English
CreditAttribution: jhodgdon commented

I was going to write up a Core post right now, but I realized I wasn't sure exactly what it should say.

Here's what I am coming up with; not sure if it's accurate:

------------
You may have noticed that as of a few days ago that there is a new branch in the Git source code repository for Drupal Core: 8.0.x!

This branch introduces "Semantic Versioning" for Drupal 8, which will allow us to have an 8.0.x release line, followed by an 8.1.x release line, and possibly more along the same lines. Unlike the drastic API and architecture changes that would accompany a 7.x -> 8.x or 8.x -> 9.x major release update, and correspondingly long timelines, the changes between 8.0.x and 8.1.x are expected to be more incremental (adding features and minor API refinements). Also, the time between 8.0.x and 8.1.x is expected to be correspondingly shorter. This change in philosophy will take some of the pressure off developers to make sure absolutely everything they want gets into the 8.0.x release, because new features can be added in the 8.1.x line.

Practical implications:
- All of the existing 8.x issues in the Drupal Core issue queue have been moved to the 8.0.x branch.
- Some issues may be pushed off to 8.1.x or 9.x by the branch maintainers: 8.1.x for more incremental changes, and 9.x for more drastic changes; in both cases, for issues that will not make it into 8.0.0.
- Do not file any more 8.x branch issues.
- Switch your local git repositories to use the 8.0.x branch. The 8.x branch will be emptied and deleted sometime soon [DATE????]

For more information: [Link?????????????????]
---------

(and there is also a 8.1.x, which isn't yet being used, but is there

catch’s picture

catch
he/him
Primary language English
CreditAttribution: catch commented

I think we should delete the 8.x branch shortly after the next alpha (which will be August 6th now).

We could link to https://www.drupal.org/node/2135189 for the release cycle changes maybe? Not sure if some of that has already made it to the handbook or not?

jhodgdon’s picture

jhodgdon
she/her
Primary language English
CreditAttribution: jhodgdon commented
Issue summary: View changes

Posted this in the Core group: https://groups.drupal.org/node/436178

xjm’s picture

xjm
she/her
Primary language English
CreditAttribution: xjm commented

Yes, I also think we should just delete the 8.x branch after the next alpha. Before beta in any case. Edit: And yeah, #2135189: Proposal to manage the Drupal core release cycle never has made it into the handbook; someone needs to write that up. Not volunteering. :)

tim.plunkett’s picture

tim.plunkett
he/him
Primary language English
Location Philadelphia
CreditAttribution: tim.plunkett commented

The dangerous part is when issues are against 8.x, they run against the old code. This is frustrating when your patch doesn't apply, and dangerous when it does.

xjm’s picture

xjm
she/her
Primary language English
CreditAttribution: xjm commented
Title: Encourage use of 8.0.x over 8.x » Require use of 8.0.x over 8.x and remove 8.x
Category: Feature request » Task

We'll need to make sure anything in this list gets fixed before we delete the branch
https://www.drupal.org/project/issues/drupal?status=All&version=8.x-dev

jhodgdon’s picture

jhodgdon
she/her
Primary language English
CreditAttribution: jhodgdon commented
Version: 8.x-dev » 8.0.x-dev
Issue summary: View changes

Good idea. I just went through the about 5 issues currently there and this one is the only remaining. Should check again before removing the branch. Added to issue summary too.

xjm’s picture

xjm
she/her
Primary language English
CreditAttribution: xjm commented

The alpha is out, so it's time for step #4. :)

drumm’s picture

drumm
he/him
Location NY, US
CreditAttribution: drumm commented

I do recommend deleting the release on git7site first and spot checking. I can do that, later in the day or tomorrow for me.

drumm’s picture

drumm
he/him
Location NY, US
CreditAttribution: drumm commented

There's no problem with deleting the release node, and Git branch, that I can see. I tested it out on git7site. And remembered that this happens often enough for other projects.

I'll go ahead and delete the release node. I'll leave any 8.x Git commits, or deleting the remote branch, to the D8 maintainers, unless I'm asked to put on my 8.x maintainer hat on again.

drumm’s picture

drumm
he/him
Location NY, US
CreditAttribution: drumm commented
Issue summary: View changes

https://www.drupal.org/node/572834 is now deleted and redirected to 8.0.x-dev.

catch’s picture

catch
he/him
Primary language English
CreditAttribution: catch commented
Status: Active » Reviewed & tested by the community

I'll probably delete the 8.x branch later today, moving this to RTBC for visibility.

alexpott’s picture

alexpott
he/they
Primary language English
Location 🇪🇺🌍
CreditAttribution: alexpott commented

+1

catch’s picture

catch
he/him
Primary language English
CreditAttribution: catch commented
Status: Reviewed & tested by the community » Fixed

Done.

jhodgdon’s picture

jhodgdon
she/her
Primary language English
CreditAttribution: jhodgdon commented
Issue summary: View changes
Status: Fixed » Active

#2 in the issue summary -- is that done? Where is it?

alexpott’s picture

alexpott
he/they
Primary language English
Location 🇪🇺🌍
CreditAttribution: alexpott commented
Status: Active » Fixed

This has been done but in order to update your local repo you need to execute:

git fetch --prune
alexpott’s picture

alexpott
he/they
Primary language English
Location 🇪🇺🌍
CreditAttribution: alexpott commented

And...

git remote set-head origin 8.0.x

will fix the dangling HEAD

jhodgdon’s picture

jhodgdon
she/her
Primary language English
CreditAttribution: jhodgdon commented
Status: Fixed » Active

The reason I moved this back to "Active" is item #2 in the issue summary: something about a change notice.

valthebald’s picture

valthebald
Location Sofia
CreditAttribution: valthebald commented
Status: Active » Fixed

Item #2 is fixed now, safe to mark as fixed again?

Status: Fixed » Closed (fixed)

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