-
I want to propose settling on a versioning scheme that I think we are starting to loosely follow already anyway. The main goals I think we want to achieve are:
- Allow customers to roll out new gat…
-
### Context
Shimming Toolbox is set up between 2 repos
- [Shimming Toolbox](https://github.com/shimming-toolbox/shimming-toolbox)
- [FSLeyes plugin](https://github.com/shimming-toolbox/fsleyes-plug…
-
Do we want to version the schema separately from `uv` itself, so that we can support different formats over time?
-
So, something I noticed when getting the latest Beta release is that the versioning is inconsistent.
There are 3 different versions stated at different places...
**3.17.2295** and **3.17.2297** are …
-
-
### Issue 타입(하나 이상의 Issue 타입을 선택해주세요)
☑ 기능 추가
□ 기능 삭제
□ 버그 리포트
□ 버그 수정
□ 의존성, 환경 변수, 빌드 관련 코드 업데이트
### 상세 내용
#### 어떤 기능인가요?
> API versioning(버전 관리)에 필요한 커스텀 어노테이션을 개발합니다
#### 작업 상세 내용
- …
-
Current versioning is somehow misleading and specially in go provides an unfriendly experience.
There are a few challenges with the approach `Y.m.d`:
1. A year bump means a new major release which…
-
Currently, AbsTasks only differ by name.
Whenever we want to update an abstask there are two things we have to make sure:
1. Most people and new tasks use the new version.
2. Results on older tasks…
-
Many times, when you have to downgrade gloo, a user has to remove the CRDs (API contract) so that the downgraded new release will have the correct matching CRDs.
The approach was to delete the CRDs…
-
# CRD Versioning in Rust using Derive / Attribute Macros
## General
Currently, all our CRDs are defined by Rust structs. This works really well for multiple reasons:
- Structs can directly be…