Add some clarifications based on DPO feedback

[warsaw]

• Add an Atomic Publication and Conflicts section. Specify that publication is atomic with respect to
  the release's filename namespace: the server reserves the session's filenames for the duration of a
  publish so that concurrent uploads (including through the legacy API) receive a 409 Conflict, and
  releases the reservation if the publish fails. Clarify that the conflict check at file upload session
  creation is best-effort and that the authoritative check happens atomically at publish time, reported
  synchronously as a 409 Conflict or, for a deferred publish, by moving the session to the error
  state with the reason in notices.
• Add a Session Status Retention section. Specify that after a session reaches a terminal
  (published or canceled) state, the server SHOULD keep serving its status URL reporting the
  terminal status for an index-specific retention period, after which it MAY return 404 Not Found,
  and that clients must be prepared for such a 404. Reconcile the cancellation rules accordingly: the
  data-bearing and action URLs may become unavailable once purged, while the status URL is retained.
  Tie file upload session status URL retention to the parent publishing session: while the parent is
  non-terminal the server SHOULD keep its file upload session status URLs valid, and once the parent
  terminates they are retained no longer than the parent's status URL.
• Expand the "Why is the project name required" FAQ to note that single-project sessions still improve
  multi-project releases (all projects can be fully staged before a final step publishes each one) and lay a
  foundation for a possible future "publish multiple projects" endpoint.

[read-the-docs-community]

Documentation build overview

📚 pep-previews | 🛠️ Build #33364301 | 📁 Comparing 43052c0 against latest (113a0a5)

  🔍 Preview build  

1 file changed

± pep-0694/index.html