Skip to content

P1 Expand ArbOS 60 upgrade notice with [TBD] placeholders (TW-736)#3239

Draft
anegg0 wants to merge 1 commit intoArbos60from
tw-736-p1-expand-arbos-60-upgrade-notice-with-tbd-placeholders
Draft

P1 Expand ArbOS 60 upgrade notice with [TBD] placeholders (TW-736)#3239
anegg0 wants to merge 1 commit intoArbos60from
tw-736-p1-expand-arbos-60-upgrade-notice-with-tbd-placeholders

Conversation

@anegg0
Copy link
Copy Markdown
Contributor

@anegg0 anegg0 commented Apr 24, 2026

Description

Expands the ArbOS 60 upgrade notice from a one-line stub to the full structure matching arbos51-upgrade-notice.mdx. All version- and date-sensitive fields use [TBD] placeholders — per Derek's scratchpad, shipping placeholders before the DAO vote outcome is explicitly acceptable.

Structure:

  • Intro paragraph

  • Actions required admonition (Nitro version, Docker image, release notes — all [TBD])

  • Important dates table (Sepolia + One/Nova, dates [TBD])

  • Context paragraph summarizing the 5 feature areas

  • Linear: TW-736

  • Notion drafting page: https://www.notion.so/arbitrum/30d01a3f59f880ac91dbfcc89602eab9

  • Template: docs/notices/arbos51-upgrade-notice.mdx

Document type

  • Gentle introduction
  • Quickstart
  • How-to
  • Concept
  • FAQ
  • Troubleshooting
  • Reference
  • Third-party content
  • Not applicable (notice)

Checklist

  • I have read the CONTRIBUTE.md guidelines
  • My changes follow the style conventions outlined in CONTRIBUTE.md
  • I have used sentence-case for titles and headers
  • I have used descriptive link text (not "here" or "this")
  • I have separated procedural from conceptual content where appropriate
  • I have tested my changes locally — Vercel preview will verify build
  • My code follows the existing code style and conventions
  • I have added/updated frontmatter for new documents
  • I have checked for broken links — relative paths match existing arbos51 notice pattern
  • I have verified that my changes don't break the build — pending Vercel preview
  • Third-party docs only:
    • Yes
    • Not applicable

Additional Notes

  • DRAFT — all [TBD] markers to be filled when DAO vote outcome + activation dates are known.
  • Targets `Arbos60` staging branch, not `master`.
  • File is already registered in `sidebars.js:1927` on `Arbos60`, so no sidebar changes needed.
  • Once Nitro version, Docker tag, release-notes URL, and activation dates are finalized, update this PR and mark ready for review.

Replaces the sparse stub with the arbos51 notice structure:
- intro paragraph
- actions required admonition
- important dates table
- context paragraph

All version- and date-sensitive fields use [TBD] placeholders per
Derek's scratchpad — OK to ship before DAO vote outcome.
@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 24, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
arbitrum-docs Error Error Apr 24, 2026 7:31pm

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant