[wp-trac] [WordPress Trac] #64393: Change how we include Gutenberg in Core

[WordPress Trac]

#64393: Change how we include Gutenberg in Core
------------------------------+--------------------------
 Reporter:  youknowriad       |       Owner:  youknowriad
     Type:  task (blessed)    |      Status:  reopened
 Priority:  high              |   Milestone:  7.0
Component:  Build/Test Tools  |     Version:
 Severity:  blocker           |  Resolution:
 Keywords:  has-patch         |     Focuses:
------------------------------+--------------------------

Comment (by dmsnell):

 After more simulation and experimentation, I’d like to perhaps try this
 `svn` commit to restore the version history, and I would really appreciate
 any help to review the plan before I do it.

 Noting:

  - There are no current merge commits in `trunk` in the `git` mirror. This
 means that the merge will be a first.
  - This is a normal thing to do in an `svn` repository, but branching is
 heavy and we haven’t done it, so I don’t know if there are any things I am
 not anticipating that could go wrong. Do any tools rely on an **assumption
 that history is linear only**?
  - Can we create a backup of the `svn` master repo just in case?
  - Can anyone confirm whether the post-commit hook in `svn` leads to a
 `git svn fetch` on the `git` side before performing a `git svn rebase`, or
 whatever the code is that runs?

 @dd32 I know you’ve been wearing a lot of hats recently, but is there any
 way we can review the scripts or the code that pushes changes to `git` so
 can we have an appropriate expectation of what happens if we do this?

 Plan:
  - create an `svn` branch from before the build change on Jan 5.
  - copy the built files from `trunk` into that branch on the files that
 were deleted
  - update the `.gitignore` to add them back in
  - merge that branch back into `trunk`, thus establishing continuity with
 their histories.

 If we don’t have any better assessments then I think at some point we just
 need to try this and deal with the consequences if something doesn’t go
 right. The thing I’m most concerned about is that if we don’t get updates
 on the `git` side that pull in the `svn` branch, then `git svn` is going
 to flatten the changes when we merge the branch and that will be for a
 waste because it won’t restore the history.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64393#comment:188>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform