public/obsidian-livesync
1
0
Fork 0
mirror of https://github.com/vrtmrz/obsidian-livesync.git synced 2026-07-18 02:26:02 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update: beta tagging

Browse Source
This commit is contained in:
vorotamoroz
2026-04-06 11:46:51 +01:00
parent 3e4db571cd
commit 4d0203e4ca
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
devs.md
+5 -5
View File
@@ -153,17 +153,17 @@ export class ModuleExample extends AbstractObsidianModule {
## Beta Policy ## Beta Policy
- Beta versions are denoted by appending `-patched-N` to the base version number. - Beta versions are denoted by appending `+patchedN` to the base version number.
- `The base version` mostly corresponds to the stable release version. - `The base version` mostly corresponds to the stable release version.
- e.g., v0.25.41-patched-1 is equivalent to v0.25.42-beta1. - e.g., v0.25.41+patched1 is equivalent to v0.25.42-beta1.
- This notation is due to SemVer incompatibility of Obsidian's plugin system. - This notation is due to SemVer incompatibility of Obsidian's plugin system.
- Hence, this release is `0.25.41-patched-1`. - Hence, this release is `0.25.41+patched1`.
- Each beta version may include larger changes, but bug fixes will often not be included. - Each beta version may include larger changes, but bug fixes will often not be included.
- I think that in most cases, bug fixes will cause the stable releases. - I think that in most cases, bug fixes will cause the stable releases.
- They will not be released per branch or backported; they will simply be released. - They will not be released per branch or backported; they will simply be released.
- Bug fixes for previous versions will be applied to the latest beta version. - Bug fixes for previous versions will be applied to the latest beta version.
This means, if xx.yy.02-patched-1 exists and there is a defect in xx.yy.01, a fix is applied to xx.yy.02-patched-1 and yields xx.yy.02-patched-2. This means, if xx.yy.02+patched1 exists and there is a defect in xx.yy.01, a fix is applied to xx.yy.02+patched1 and yields xx.yy.02+patched2.
If the fix is required immediately, it is released as xx.yy.02 (with xx.yy.01-patched-1). If the fix is required immediately, it is released as xx.yy.02 (with xx.yy.01+patched1).
- This procedure remains unchanged from the current one. - This procedure remains unchanged from the current one.
- At the very least, I am using the latest beta. - At the very least, I am using the latest beta.
- However, I will not be using a beta continuously for a week after it has been released. It is probably closer to an RC in nature. - However, I will not be using a beta continuously for a week after it has been released. It is probably closer to an RC in nature.