Bump to v1.0 (stable semver release)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by reviewing the repository's current 0.x release and versioning setup, then assess the proposed breaking-change and deprecation questions, including no_extract and old auth patterns. Done means the 1.0 scope and semver policy are agreed, including whether a deprecation pass is required first.
Written by the indexing model from the issue text.
Description
TSC has been versioned as 0.x since its initial release, despite being a widely-used, production-grade library. Staying at 0.x implies instability and allows semver-breaking changes without a major version bump, which is confusing for users who depend on it.
Proposal: release the next version as 1.0, signalling stability and committing to semver conventions going forward. This means:
- Breaking changes require a major version bump (2.0, etc.)
- Non-breaking additions use minor bumps (1.1, 1.2, ...)
- Bug fixes use patch bumps (1.0.1, ...)
This aligns with the approach used by other Tableau SDKs (e.g. the Migrations SDK).
Open questions:
- Are there any known breaking changes we'd want to ship before locking 1.0?
- Should we do a deprecation pass first (e.g.
no_extract, old auth patterns)?
- Dominant language
- Python
- Stars
- 716
- Forks
- 446
- Avg merge
- 8d 8h
- Merged PRs (30d)
- 2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from tableau/server-client-python
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
tableau/server-client-python#1865 ·
-
in-progress
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
tableau/server-client-python#1829 · 1 comment ·
-
enhancement gap needs investigation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
tableau/server-client-python#1322 · 1 comment ·
-
[Type2] Allow Incremental Refresh type schedules to be added via `server.schedules.add_to_schedule` Openhelp wanted Server-Side Enhancement ui-exists
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
tableau/server-client-python#1101 · 3 comments ·
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
tableau/server-client-python#783 · 5 comments ·
All issues in tableau/server-client-python
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
🐛 Bug 🔔 Pending processing
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
jumpserver/jumpserver#17584 ·