pjfanning opened a new pull request, #1408:
URL: https://github.com/apache/pekko-http/pull/1408

   ### Motivation
   2.0.0 is due for release. The release notes had separate sections for the 
2.0.0-M1 and 2.0.0-M2 milestones, and the migration guide did not cover changes 
merged since 2.0.0-M2.
   
   ### Modification
   - Replace the milestone sections in `releases-2.0.md` with a single 2.0.0 
section that combines the milestone notes and the changes merged since 2.0.0-M2 
(main changes, additions, Java DSL improvements, bug fixes, performance, 
dependency changes). It links the M1, M2 and M3 GitHub milestones and the 
migration guide.
   - Rename the release notes index entry from "2.0 Milestone Releases" to "2.0 
Releases".
   - Add the post-M2 changes to the 1.x to 2.x migration guide:
     - Java DSL `ConnectionPoolSettings.withHostOverrides` takes `japi.Pair` 
(#1377), widened Java generic parameters (#1379–#1384) and new Java DSL 
alternatives to Scala types (#1373, #1375, #1376)
     - whitespace before header list separators (#1395)
     - HTTP/2 client `:scheme`/`:authority` for relative URIs (#1342) and the 
503 response when a persistent connection gives up (#1368)
     - graceful termination preserving pending responses (#1398, #1400)
     - WebSocket `receive-idle-timeout` / `send-idle-timeout` settings (#1369)
   
   ### Result
   Users get one set of 2.0.0 release notes and a migration guide that matches 
the release.
   
   ### Tests
   - Not run - docs only
   
   ### References
   None - 2.0.0 release preparation
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to