Skip to content

[DOC] Add a v1 to v2 migration guide - #2349

Open
echo-xiao wants to merge 7 commits into
sktime:mainfrom
echo-xiao:migration-guide-v2
Open

[DOC] Add a v1 to v2 migration guide#2349
echo-xiao wants to merge 7 commits into
sktime:mainfrom
echo-xiao:migration-guide-v2

Conversation

@echo-xiao

Copy link
Copy Markdown
Contributor

Adds docs/source/migration_v2.rst (a v1 to v2 migration guide) and registers it in the api_v2 toctree. Addresses #2288, part of the v2 docs umbrella #2304. Includes a v1-to-v2 concept mapping table, an end-to-end TFT before/after example (v1, v2 package wrapper, v2 explicit layers), a what-stays-the-same section, and a whats-new section with an auto-generated model-overview table. Example code runs on load_toydata and the docs build cleanly.

@codecov

codecov Bot commented Jul 21, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (main@a4068ff). Learn more about missing BASE report.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2349   +/-   ##
=======================================
  Coverage        ?   87.34%           
=======================================
  Files           ?      171           
  Lines           ?    10080           
  Branches        ?        0           
=======================================
  Hits            ?     8804           
  Misses          ?     1276           
  Partials        ?        0           
Flag Coverage Δ
cpu 87.34% <ø> (?)
pytest 87.34% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

…ide (rename to migration_v1_to_v2, move under tutorials)
Comment thread docs/source/api_v2.rst Outdated
Tutorials <tutorials_v2>

.. seealso::
Porting a v1 model implementation to v2? See :doc:`migration_v1_to_v2`.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this guide should be in the boxes at the top of every page which shows v2 is in works. WHat do you think?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants