-
Notifications
You must be signed in to change notification settings - Fork 18
Discussion: Separate or merge the changelogs on the website #305
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
Comments
Personally, I think it's better to handle it the way I did in that PR, but if you don't agree, we can always change it to whatever the majority agrees on. |
The way it turned out seems better to me, because we don't have a page for 3x or 2x. And it would have a clearer view of the evolution of the versions |
We discussed today and agreed to defer to the @expressjs/docs-wg folks to decide what is best. With a general approval of the way it is on the website currently. |
Several weeks ago, expressjs/expressjs.com#1656 was merged into the main branch, with the goal of consolidating the two changelogs (v4 and v5) into a single page to avoid managing two separate pages for the same purpose (informing about Express changes). However, I fear that this may not have been the best decision according to expressjs/expressjs.com#1656 (comment), which mentions that there was a different approach in how it was handled on the page in the past.
cc: @expressjs/docs-captains @expressjs/docs-wg
The text was updated successfully, but these errors were encountered: