Skip to content

Align the site with the 6.0.0 dataset: re-point download links and sizes, drop stale references #133

Description

@gsvgit

dev works towards v6.0: the dataset on S3 is at the 6.0.0/graph/ prefix (self-contained archives), but the site still points at 5.0.0 artifacts. No package version bump in this task (that happens in the rename task, 49) — this is preparation: make all site references consistent with the 6.0.0 dataset.

  • Re-point every download link from 5.0.0/graph/ to 6.0.0/graph/: the 113 per-graph pages (docs/graphs/data/*.rst, "Direct download") and the eight category tables (docs/graphs/*.rst, "Download" column).
  • Update the Size (MB) columns against the 6.0.0 archives with utils/archive_sizes.py --update (sizes differ, e.g. xz_field_sensitive_alias 27.7 KB -> 536 KB); verify with the check mode afterwards.
  • docs/utils.rst: update the current-state prefix references to 6.0.0/graph/ (upload key example, archive_sizes coverage description, --audit example). The migrate_gdrive_to_s3 section describes the historical migration — leave it untouched.
  • AGENTS.md "Package layout": cfpq_data/dataset/ no longer has download_grammars/download_benchmark (removed in 48-S6) — fix the line to match the current API (download, reachable_pairs).
  • Benchmark page related stuff stays removed from dev: do not re-introduce any benchmark page or reference as part of this alignment. Historical changelog entries and the flpq.rst design references stay; LICENSE-DATA.txt keeps "benchmarks" because the 4.0.0/benchmark/ data is still distributed.

Verification: utils/archive_sizes.py (check mode) passes; no 5.0.0/graph link remains in docs/ outside historical text; docs build green.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    taskTask tracking issue for the project workflow (see the workflow-management skill)

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions