>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #1015704. --> Reported by: [dww](https://www.drupal.org/user/46549) >>> <p>Dries sent me an email asking about the steps it's going to take to open up HEAD for D8. Not sure exactly when he wants to do that, but I wanted to open an issue to document everything I can think of that would care (and hopefully get other infra team folks thinking about this) so that whenever that finally happens, everyone's ready...</p> <h4>A) Release nodes</h4> <p>When you create the DRUPAL-7 branch we're going to want to fix two -dev release nodes:</p> <p><a href="http://drupal.org/node/156281">http://drupal.org/node/156281</a> (7.x-dev) will need to be edited to point it to the DRUPAL-7 branch once that exists. Dries should be able to do that himself by editing the node, or anyone with super-uber 'project administrator' perms should be able to edit as well. If not, it can be done via mysql (see below). ;)</p> <p><a href="http://drupal.org/node/572834">http://drupal.org/node/572834</a> (8.x-dev) will need to be manually edited to point to the real HEAD branch, not the bogus "branch" it's pointing to now. These future release nodes are a bit of a hack, and there's not good support in project_release for them (since they come up so infrequently). So, the best (only?) way to do this is at the mysql prompt:</p> <p><code>UPDATE project_release_nodes SET tag = 'HEAD' WHERE nid = 572834;</code></p> <p>To fix the other, you can just run this while you're at it:</p> <p><code>UPDATE project_release_nodes SET tag = 'DRUPAL-7' WHERE nid = 156281;</code></p> <p>Afterwards, probably wouldn't hurt to run the hudson job that rebuilds -dev releases for core so that they get updated tarballs.</p> <h4>B) Make "8.x" an "active Drupal core version"</h4> <p><a href="http://drupal.org/admin/project/project-release-settings">http://drupal.org/admin/project/project-release-settings</a></p> <p>When one of the Drupal core version taxonomy terms is "active", the following are true:</p> <p>B1) "8.x" will be available on the release node form when creating HEAD releases (this won't be an issue once we move to Git, but for now, it might still matter).</p> <p>B2) When administering releases for a given project, there will be options for 8.x-based branches (if any exist), e.g. at <a href="http://drupal.org/node/3060/edit/releases">http://drupal.org/node/3060/edit/releases</a></p> <p>B3) There's a "- 8.x issues -" special grouping for issue queue views</p> <p>B4) There will be a 8.x option in the various solr-based project browsing pages:<br> <a href="http://drupal.org/project/modules">http://drupal.org/project/modules</a><br> <a href="http://drupal.org/download">http://drupal.org/download</a></p> <p>B5) Usage stat display pages will start having 8.x as an option, e.g. at <a href="http://drupal.org/project/usage/drupal">http://drupal.org/project/usage/drupal</a></p> <p>I think that's it, there might be a few other uses of this bit that I'm not finding on a quick grep...</p> <h4>C) Consider changing the contributors block links</h4> <p>On the dashboard's "Contributor links" block, there are a bunch of D7-specific issue counts and links. We should consider changing these. This is from drupalorg_project.module. These issues should pretty much tell you how they work:</p> <p><span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/drupalorg/-/work_items/383356" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/drupalorg/-/work_items/383356</a></span><br> <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/drupalorg/-/work_items/987068" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/drupalorg/-/work_items/987068</a></span></p> <h4>D) Testbot?!</h4> <p>No idea. I think we need DamZ and/or boombatower to weigh in on this one. Seems potentially problematic.</p> <h4>E) localize.d.o</h4> <p>Not sure. I doubt they care, but they might. Gabor?</p> <p>That's all I can think of. Other infra team members are strongly encouraged to think if anything they deal with touches CVS HEAD and is going to care if all of a sudden it's D8, not D7, or other places on the site that are going to care when D8 is open for development.</p> <p>Thanks,<br> -Derek</p>