[Housekeeping]: Release 2.0 - Tracking Issue (scope • dependencies • status)

[pheus]

Purpose

Coordinate the NetBox ACL Plugin v2.0 work in one place: scope, dependencies, merge order, testing, and docs. This issue is meta/housekeeping (not a feature request); individual changes are tracked in their own issues/PRs and linked here.

Status legend

• 🔁 Implemented (rebase → dev-2.0 pending) — development done on a feature branch; not yet integrated into dev-2.0
• 🧩 Implemented (in dev-2.0) — integrated into the fork’s integration branch; awaiting upstream PR/merge
• 🔍 Investigating — validating scope, reproducing, and exploring solutions; not yet in implementation
• 🟡 In progress — active development or pending review/approval
• ⏳ Planned — confirmed for 2.0 but not started
• ✅ Merged (upstream release-2.0) — landed in the official 2.0 branch
• ⛔ Blocked

---

Scope (confirmed for v2.0)

🔁 Implemented (rebase → dev-2.0 pending)

• 🔁 [Housekeeping]: Use NetBox’s default get_absolute_url() implementation #286
• 🔁 [Housekeeping]: Validate AccessList.name with validate_slug (replace custom regex) #287
• 🔁 [Feature]: Reflect ACL rule modifications in the parent ACL’s changelog #288

🧩 Implemented (in dev-2.0, pending upstream merge)

• 🧩 [Feature]: Add assigned_object models in GraphQL API similar to the REST API #41
• 🧩 [Feature]: Logging option #57
• 🧩 [Feature]: Assign a ACL to multiple devices  #72
• 🧩 [Feature]: List all interfaces an acl is applied to on the acl page #127
• 🧩 [Feature]: source and destination range for acl have to be a prefix in Netbox? #129
• 🧩 [Feature]: port ranges #135 - see latest comment for current findings and next steps
• 🧩 [Feature]: Add IP to the protocol list #142
• 🧩 [Housekeeping]: Move forms to use selector in place of various params #156 - will be fixed by [Feature]: Assign a ACL to multiple devices  #72 and [Feature]: source and destination range for acl have to be a prefix in Netbox? #129
• 🧩 [Bug]: ACL Interface Assignment Should Be Unique per Interface and Direction #258 - will be fixed by [Feature]: Assign a ACL to multiple devices  #72
• 🧩 [Feature]: Global Search Functionality #281
• 🧩 [Feature]: Add ACL "family" field (IPv4 / IPv6 / Dual) #282
• 🧩 [Feature]: Support ACLRule‑attached remarks (sharing sequence) #283
• 🧩 [Bug]: ACLExtendedRule allows out‑of‑range port numbers (0 or >65535) in source_ports / destination_ports #291 - will be fixed by [Feature]: port ranges #135

🔍 Investigating

• 🔍 none yet

🟡 In progress — needs maintainer approval

• 🟡 [Housekeeping]: Standardize linting on Ruff (remove legacy linters/formatters) #284
• 🟡 [Housekeeping]: Move CI off NetBox Docker images; install NetBox during workflow (generic runner) #285
• 🟡 [Feature]: Rename ACLRule fields for clarity: index → sequence, action → rule_type #290

✅ Merged upstream (release-2.0)

• ✅ none yet

⏳ Planned / not started

• ⏳ none yet

If an item has an open PR, please note it in a comment (e.g. “PR: #XYZ”). Inter‑issue dependencies can also be noted inline (e.g. “depends on #ABC”).

---

Integration queue (short‑term actions)

• Rebase [Housekeeping]: Use NetBox’s default get_absolute_url() implementation #286 onto dev-2.0 and merge into dev-2.0
• Rebase [Housekeeping]: Validate AccessList.name with validate_slug (replace custom regex) #287 onto dev-2.0 and merge into dev-2.0
• Rebase [Feature]: Reflect ACL rule modifications in the parent ACL’s changelog #288 onto dev-2.0 and merge into dev-2.0

---

Gating items before tagging v2.0

• Branch & milestone: Upstream release-2.0 branch and v2.0 milestone exist
• Docs: Upgrade notes (breaking changes, migrations, deprecations)
• README: Update with new features and supported versions (NetBox & Python)
• Screenshots: Refresh UI screenshots in README/docs
• Migrations: Schema/data migrations verified on representative datasets
• CI: Test matrix green on release-2.0
• Manual QA: Create/update/delete flows (UI & API), permissions/RBAC, search, and performance smoke tests
• Changelog: Drafted and reviewed
• Compatibility: Confirm supported NetBox & Python versions (documented)

---

Proposed workflow & merge order (when release-2.0 exists)

1. Merge foundational refactors first (items other work depends on)
2. Merge dependent features next (call out dependencies in PR descriptions)
3. Merge docs/cleanup and finalize upgrade notes
4. Cut pre‑release (beta/rc), gather feedback, then tag v2.0

Please mark PR descriptions with:
• Closes #<issue> to auto‑close on merge
• Depends on #<PR/issue> when order matters

---

How to test (early adopters)

• Install the plugin from a fork/branch that aggregates 2.0 work (dev-2.0)
  pheus/netbox-acls/dev-2.0
• Share findings on this thread; include NetBox version, steps, and logs.

---

Running changelog (draft)

Added

• (populate as items merge)

Changed

• (populate as items merge)

Deprecated/Removed

• (populate as items merge)

Migration notes

• (populate as items merge)