post: Update default branch post-26.05#1024
Conversation
VERSION 1.54.0dev -> 1.54.0. Dockerfile MODEL_ANALYZER_VERSION and
MODEL_ANALYZER_CONTAINER_VERSION ARGs drop the dev suffix. Bump
nvcr.io/nvidia/tritonserver tag references from 26.04-py3* to
26.05-py3* and r26.04 server doc links to r26.05 across README,
helm-chart/values.yaml, docs/{bls,ensemble,mm,quick}_quick_start.md,
docs/config.md, docs/kubernetes_deploy.md, and
model_analyzer/config/input/config_defaults.py.
Refs TRI-1048
…pdate-default-branch
mc-nv
changed the title
| [Max Batch Size](https://github.com/triton-inference-server/server/blob/r26.04/docs/user_guide/model_configuration.md#maximum-batch-size), | ||
| [Dynamic Batching](https://github.com/triton-inference-server/server/blob/r26.04/docs/user_guide/batcher.md#dynamic-batcher), and | ||
| [Instance Group](https://github.com/triton-inference-server/server/blob/r26.04/docs/user_guide/model_configuration.md#instance-groups) | ||
| [Max Batch Size](https://github.com/triton-inference-server/server/blob/main/docs/user_guide/model_configuration.md#maximum-batch-size), |
There was a problem hiding this comment.
should we use the release branch or main here? similar question for quick_start.md - i see we're using release branch not main there?
There was a problem hiding this comment.
It should use main branch, we not always paying attention to those details.
Release branches should point to release branches, default branches to default values.
There was a problem hiding this comment.
i'm not quite following why GitHub doc links in docs/*quick_start.md use release branches but README.md uses main?
There was a problem hiding this comment.
@nv-rinig I think you're confusing container names (which HAVE to contain a release name) and branch names.
looks to me like every branch is being updated to point to main, while all container references are being updated to point to 26.05 since it is the latest release.
4 participants
CI (internal): #52829374
What does the PR do?
Advances the
mainbranch of Model Analyzer after ther26.05cut: bumps base image references to26.05across the Dockerfile, docs, helm chart, and config defaults. Standard post-release sync ofmainwith the latest release branch.Changed files include:
Dockerfile,README.md,docs/*.md,helm-chart/values.yaml,model_analyzer/config/input/config_defaults.py.Checklist
Commit Type:
feat(A new feature)fix(A bug fix)docs(Documentation-only changes)style(Changes that do not affect the meaning of the code — formatting, whitespace, etc.)refactor(A code change that neither fixes a bug nor adds a feature)perf(A code change that improves performance)test(Adding missing tests or correcting existing tests)build(Changes that affect the build system or external dependencies)ci(Changes to CI configuration files and scripts)chore(Other changes that don't modify src or test files)Related PRs:
Where should the reviewer start?
Dockerfile,README.mdTest plan:
Release-maintenance change; no new behaviour introduced.
Caveats:
None.
Background
Part of TRI-1063 post-26.04 release maintenance: advance all Triton
main/masterbranches to track ther26.05release and the 26.06 development cycle.Related Issues:
Resolves: TRI-1063