-
Notifications
You must be signed in to change notification settings - Fork 7k
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
1.14 Merge Order #9831
Comments
Where does the move to socket API support in the networking subsystems land in this list? |
nice table :) |
which PR is that? |
@galak added some additional info, thanks for creating this. |
This is more or less for everything that is either complete or semi-complete and intrusive in nature, i.e. touches multiple components. Everything else continues as usual. |
That's how I understand this list too. For sockets, stuff-before-sockets remains there for the foreseeable future, so socket tasks aren't for this list. (Unlike e.g. logging, which, if we decided to switch too, needs to be done, or it's really a pain to deal with 2 systems). @mike-scott ^^ |
ok |
I'm confused about the relationship between the various pull requests regarding code generation:
I'm also confused about what the problems that are trying to be solved are, and which of these PRs are dependencies versus competing implementations. Variously, I see attempts to:
There isn't an umbrella issue on GitHub named in the table here that describes the problem, solution space, etc. Can someone point me in the right direction? There appears to be quite a lot of vigorous discussion in the PRs and it's overwhelming. If this is going to be an intrusive change, it would be great to have a single place with a clear summary of the problem, proposed solutions, etc., especially if at least the problem statement has buy-in from all the parties involved. |
Thank you @erwango for the clarification! I will study the issue in #8499. @galak could you please add the issues related to each PR to your table if it's not too much trouble? I imagine this table will be read by many people since it's the comprehensive list of highly intrusive changes for v1.14, so it should be worth the effort. |
Being the author of numerous logging pull-requests, I am also waiting for @nordic-krch's pull-request: #9761 to be reviewed to rebase and refactor my pull-requests on |
meeting minutes:
|
one other big and intrusive change:
|
This Issue is to track which changes should try and get merged in which order early on so we can reduce churn & conflicts:
The text was updated successfully, but these errors were encountered: