-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Finish work to make bootstrap
only use startFrame
#7205
Finish work to make bootstrap
only use startFrame
#7205
Conversation
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
5519ab3
to
5b014cd
Compare
Conflicts have been resolved. A maintainer will review the pull request shortly. |
cb07fb0
to
60b2831
Compare
6bfb929
to
00958ca
Compare
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
00958ca
to
be2350a
Compare
60b2831
to
1fb32e0
Compare
Conflicts have been resolved. A maintainer will review the pull request shortly. |
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
1116de6
to
24ff05b
Compare
Conflicts have been resolved. A maintainer will review the pull request shortly. |
78aebbb
to
ca9ba58
Compare
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
24ff05b
to
f6b49db
Compare
Signed-off-by: Sebastian Malton <sebastian@malton.name>
Signed-off-by: Sebastian Malton <sebastian@malton.name>
Signed-off-by: Sebastian Malton <sebastian@malton.name>
Signed-off-by: Sebastian Malton <sebastian@malton.name>
Signed-off-by: Sebastian Malton <sebastian@malton.name>
Signed-off-by: Sebastian Malton <sebastian@malton.name>
Signed-off-by: Sebastian Malton <sebastian@malton.name>
Signed-off-by: Sebastian Malton <sebastian@malton.name>
Signed-off-by: Sebastian Malton <sebastian@malton.name>
Signed-off-by: Sebastian Malton <sebastian@malton.name>
Signed-off-by: Sebastian Malton <sebastian@malton.name>
Signed-off-by: Sebastian Malton <sebastian@malton.name>
Signed-off-by: Sebastian Malton <sebastian@malton.name>
Signed-off-by: Sebastian Malton <sebastian@malton.name>
- Fixes tests that relied on root frame being initialized before cluster frames Signed-off-by: Sebastian Malton <sebastian@malton.name>
Signed-off-by: Sebastian Malton <sebastian@malton.name>
Signed-off-by: Sebastian Malton <sebastian@malton.name>
Signed-off-by: Sebastian Malton <sebastian@malton.name>
Signed-off-by: Sebastian Malton <sebastian@malton.name>
Signed-off-by: Sebastian Malton <sebastian@malton.name>
Signed-off-by: Sebastian Malton <sebastian@malton.name>
Signed-off-by: Sebastian Malton <sebastian@malton.name>
Signed-off-by: Sebastian Malton <sebastian@malton.name>
645f7f6
to
23a0465
Compare
I was thinking that do we want to do this because it opens up a possibility to regressions and even if we would do it, we would have to extract stuff to own Features. So what I'm suggesting, is that we would start extracting immediately, one by one and after everything is extracted, we remove the bootstrap. In my opinion, it would be easier to control and wouldn't lead to massive PRs because we can create one for introducing the Feature and one for removing the old implementation and switching to use the Feature. WDYT? |
Okay sure we can do that. I'll close this PR then. |
Signed-off-by: Sebastian Malton sebastian@malton.name
This PR also replaces the work done in #7189.