Issues that would still be valid for D8 should still remain in the core issue queue. Please copy those issues into new nodes here rather than moving them. It's perfectly valid for someone else to take up any of those issues for D8, but we can't do that if they're not in the queue. Thanks.

Comments

sun’s picture

Status: Active » Closed (works as designed)

Thanks for raising this issue. However, the issues were deliberately moved and not copied:

Since D8 is years away and will look entirely different, none of the issues will apply to D8. So if anything remains to be valid for D8 or beyond, then we will have to follow the usual procedure, like for any other Drupal core change request.

chx’s picture

Status: Closed (works as designed) » Active

That's not how we work. When the D8 issue queue opens, patches will be applied and they will still apply. They might get a backport. Dries has indicated he is willing to consider more backporting this cycle than before.

sun’s picture

Status: Active » Fixed

So chx and me quickly discussed. To clarify: I'm solely moving my very own issues into this module (which is not a fork, just a module).

And we discussed that we can move back the issues into the Drupal core queue after tackling them here.

sun’s picture

Title: Please copy issues rather than move them from Drupal core issue queue » Move issues back to Drupal core after resolving them

Better title.

sun’s picture

Project: » Edge
Version: » 7.x-1.x-dev

Status: Fixed » Closed (fixed)

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