Skip to content

TODO

Jump to bottom
TheAssassin edited this page Jul 17, 2023 · 2 revisions
  1. create branch v1 from master
  2. in v1 branch: delete all type-2 specific stuff from spec documents
  3. create release from v1: 1.0
  4. rename master to v2
  5. in v2 branch: delete all type-1 specific stuff that no longer applies to v2
  6. create release from v2: 2.0
  7. add features to v2 branch: mandatory static linking for runtimes, TARGET_APPIMAGE, additional version marker (*)
  8. create release from v2: 2.1
  9. rename repository type2-runtime to runtime in branch v2 (which becomes default)
  10. create issue to discuss v2.2 change: squashfs as mandatory payload format (optionally requiring zstd as the only option)

less urgent

  1. discuss introduction of resource system (similar to elfres) for v3.0 or even v2.x (TODO: dig out that one issue where we discussed that zip in between runtime and payload)
  2. create branch v3: remove magic bytes at offset 0x8 (to restore compatibility with ld-linux)

(*): add magic bytes 0x41 49 02 01 00 to different offset (using linker script), offset needs to be discussed (suggestions: 0x100, 0x400, 0x64, let's check what works)

spec releases

"semver 2.0.0 lite" -> no patch levels (chances we need patch releases are SO small we accept the risk of having to do a minor release instead)

runtime source code releases

semver 2.0.0

runtime release 1.0.0 initially releases spec v1.0 runtime release 1.1.0 initially releases spec v1.1 runtime release 2.0.0 initially releases spec v2.0 runtime release 2.0.1 initially releases spec v2.0 runtime release 2.0.1 fixes a bug in the code, but still implements spec v2.0

prereleases follow semver spec: 2.0.1-alpha.2 prepares release of runtime 2.0.1

runtime binary releases

semver v2.0.0 + build metadata

extends source code version by build number, e.g. runtime-x86_64-2.0.1+gha12345

timeline

  • release spec v2.1 (and all intermediate steps) by the end of KW 29
  • have runtime v2.1 feature complete by the end of KW 30 (that means if need be with the existing questionable build system)
  • have AppImageLauncher v3 released by end of KW 31
  • release new appimagetool v14.0.0/point release by date/whatever by end of KW 32
Clone this wiki locally