search

backdrop / backdrop-issues

Issue tracker for Backdrop core.
144 stars 39 forks source link

[meta] Drupal 8 Backport Master List #1 #106

Closed quicksketch closed 9 years ago

quicksketch commented 10 years ago
oadaeh commented 10 years ago

824eb3c "Deleting taxonomy vocabulary bug" is already in Backdrop. It went into D8 on February 20, 2012.

oadaeh commented 10 years ago

e3847c1 "Fixed noderevision_access() static usage." links to the wrong issue. It should link to https://drupal.org/node/1064954

oadaeh commented 10 years ago

I created an issue for e3847c1 "Fixed noderevision_access() static usage.", here: #112.

maxpearl commented 10 years ago

Question - commits to the 7.x branch after the fork - those also need to be included in the backport list as well?

I've gotten through a whole two weeks of commits to the 8.x branch. This is going to be a loooooong list. Just sayin'. :-)

oadaeh commented 10 years ago

There will be lots of things that can be ignored wholesale, like pretty much anything dealing with Symfony.

maxpearl commented 10 years ago

Oh, I've been ignoring lots. :-) Luckily it's easier than I thought to pick out what we need. But there still is a sh*tton of relevant commits.

oadaeh commented 10 years ago

I removed a few duplicates and marked as close those that have been committed.

quicksketch commented 10 years ago

Question - commits to the 7.x branch after the fork - those also need to be included in the backport list as well?

Yes, absolutely. Though I would imagine most of those are in 8.x as well? After a point some things obviously have only been affecting 7.x and not 8.x, so yes the 7.x history is important as well.

Also, @michellemurrain: you are my hero.

mkalkbrenner commented 10 years ago

Beside the commits we need the 7.x bug fixes that have not been committed because nobody has ported or committed to 8.x. I started a list at https://github.com/mkalkbrenner/drupal_docs/blob/master/d6_d7_issues_blocked_by_d8.md

maxpearl commented 10 years ago

So I was crazy bored dealing with my GUI git client and cutting and pasting into this issue, so I scripted the output of 'git log' for branches 8.x and 7.x into GitHub flavored markup with links, and it turns out that the number of issues exceed what will fit in the github issue text.

Suggestions for how to deal with them? The files for 8.x and 7.x are 1.7 M and 355K respectively. The worry, really is the 7.x file, which is about 6x too long to fit. The 8.x file I'll be picking and choosing issues, so it might end up fitting when I'm done (and it might not.)

oadaeh commented 10 years ago

I would just create multiple "child" issues to this meta issue, breaking up the list how ever it makes the most sense, and make sure this issue links to them and they link here.

quicksketch commented 10 years ago

@oadaeh's suggestion is a good one. We'll probably have several categories of patches: CMI conversions, i18n, WYSIWYG, etc. For each topic that has a large number of issues, make a new meta issue.

Nice thinking @michellemurrain on scripting the whole process. :)

sirkitree commented 10 years ago

Child tickets could also start out as a checklist using GitHub's checkbox syntax.

I would imagine you could start with writing a new ticket entitled something like "CMI conversions", link to this ticket in the first line (which will automatically create a back link here) and then write out the checkboxes like demonstrated above.

Then if any of those need to split out into their own ticket, you do a similar process; create a new ticket, link to that one, and then within the ticket that has the checkboxes, edit the description and put a link (#ticket-number) beside the checkbox.

Let me know if you want help. Love to see the script you're working with @michellemurrain.

quicksketch commented 10 years ago

Yeah I wanted to use the checkbox syntax on this page, but it doesn't work within tables. :(

maxpearl commented 10 years ago

7.x bugfixes, etc. are in issues #132, #134, and #135.

@sirkitree - the script is here: https://github.com/michellemurrain/gitlog_parse/blob/master/gitlog.php (it's not elegant, and definitely screws up when dealing with some things. But it got the job done (mostly.) I'm finding that it might come in handy for other things, so I might work on generalizing it.)

maxpearl commented 10 years ago

Hey there,

I've been hanging on to this hoping that I'd get to finish, but sadly, I don't have the time right now, and it doesn't make sense for me to sit on this until I do.

The rest of the log from October 2012 through November 2013 is here: https://gist.github.com/michellemurrain/9358038

That gist has the drupal 8 branch commits that have not been either reviewed for their relevance to backdrop, nor put in the current list of backdrop backport issues.

The php file I used to parse the log and create the tabular output for github issues is in the above comment.

I know that a lot of these (and the others in the backport lists) have become moot given the work on CMI and views, etc. in backdrop core. Sorry I can't complete this list. :-(

quicksketch commented 10 years ago

Hi @michellemurrain! Don't worry about it! The lists you've provided already have been invaluable. We've nearly completely finished the first D7 list and are over half way through the other 2. Just getting the lists started was a huge help. Jen or I will work on filtering down the D8 lists to applicable issues and prioritizing them. Thanks for letting us know your situation!

jenlampton commented 9 years ago

Closing this issue as it is no longer very important for the release of backdrop 1.0.0