Backlog for Express 6.x

[UlisesGascon]

This issue includes a reference to all the PRs/issues or pending tasks for Express and dependencies needed to finally ship new versions of Express@6.x

Rules (WIP):

• If something is completed, just marked
• If there is a PR/Issue/Discussion please add it (try to use one item)
• If there is someone taking ownership on it, please add it. Ownership means to be the focal point for it not necessarily the person who makes the final change.
• If there is no leader, feel free to claim it.
• If you can no longer lead something, just let others claim it back
• As this issue can have many comments, feel free to address them and then mark the original comment as "outdated" (details) so it is easier to follow.

If you think that any reference is missing, please edit this comment (@expressjs/express-tc) or reply with a comment if you don't have the permissions.

Agreed to be part of Express 6.x

none yet

Whislist / Ideas:

New (require discussion)

• Support http/2. express#3730
• Moves req/res out of the repo express#3214
• Settings functionality moved out of core express#3218
• Remove direct http dependency express#3213
• separate locals from config values express#2648
• rebase: Generic Body Parser implemented body-parser#524
• response is only finished if socket is detached jshttp/on-finished#31 (@UlisesGascon)

Discarted

none

Won't happen

none

[bjohansebas]

Since we want to support HTTP2 in this version, we probably want to include in the backlog adding tests to all the dependencies that are direct to Express.

Which is something I want to work on

[dpopp07]

Adding this discussion to the backlog: Discussion: Logging and diagnostics in v6

[wesleytodd]

I created a project to track this: https://github.com/orgs/expressjs/projects/7

It is private to members for now, but we can start adding these to that and maybe close this out?

[bjohansebas]

It seems that i'm not allowed to add issues from other organizations. i tried adding jshttp/on-finished#31, but it wouldn't let me. Maybe it's due to permissions. i've seen that other organizations have been able to reference issues from other organizations.