microsoft / microsoft/ltp-platform

V1.4.0 Release Plan

Open
#114 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
11
Forks
5
Avg merge
3m
Merged PRs (30d)
1

Description

Endgame

  • Code freeze: Nov. 07, 2025
  • Bug Bash date: Nov. 10, 2025
  • Testing start date: Nov. 17, 2025
  • Release date: Nov. 28, 2025

Main Features

Platform Features & Stability

    • Blobfuse2 installation failure (#94 )
    • LTP rest-server data auth (#112 )
    • Containers losing access to NVIDIA GPUs
    • Slow portal response (#104)
    • Fix deployment on arm64 architecture (#109 )
    • Alert manager deployment bugfix (#106 )
    • add image regex to support valid image limitation (#107 )
    • Add webportal plugin for cluster local storage (#69 )
    • Add tolerance and priority class in cluster-local-storage (#119 )
    • Create postgresql backend and support backend switch with kusto (#117)

Inference

    • Inference plugin support model proxy (#101 )
    • Support training/inference job type in restserver (#105 )
    • Support training/inference job type in webportal (#113 )
    • New Inference Job template implementation in model proxy (#118 )

CI/CD

    • CI/CD to build all service image (#102, #120 )
    • enable imagelist argument for image build script (#95 )
    • fix copy error of building image(#97)

Security

    • Upgrade Dockerfile with system update (#96)
    • Credentials in source code PR (#108,#99 )
    • Cilium update(#56)

User Experience

    • Add user manual doc (#111 )
    • Improve copilot test experience (#100 )

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue is a release checklist covering platform, inference, CI/CD, security, and user-experience work, but it names no source files or tests. Start by checking the linked issues, especially the two unchecked items, and consider the release plan complete only when its listed work is resolved and the release status is updated.

Written by the indexing model from the issue text.

Assessment

Tech stack
dockerfile, postgresql
Domain
devops, release
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.