Releases App: Blocking issues for 0.92.2
I'm opening this in order not to lose what we were/are discussing on IRC (feel free to add things).
If we want to use the releases app for the 0.92.2 release the following issues should be addressed:
-
Landing page: Where does the user land when clicking the "download" link on the main page?
On https://inkscape.org/en/release/0.92.2/ ? Beyond that We could probably detect OS from the browser but everything more specific will will likely not work (i.e. on Windows we can't decide if users want to have an exe/msi/7z package, the portable version or even the AppStore version. 32/64 bit is intertwined into all of these and as 64-bit installers do not update 32-bit versions we can also not do that decision. -
A content box for HTML content is needed at many platform pages, e.g. - https://inkscape.org/en/release/0.92.2/source/archive/bz2/dl/ to hold information on how to build and how to get involved in the project
- https://inkscape.org/en/release/0.92.2/??? to hold the notes from https://inkscape.org/en/download/linux/
- https://inkscape.org/en/release/0.92.2/windows to hold the notes from https://inkscape.org/en/download/windows/
- https://inkscape.org/en/release/0.92.2/mac-os-x/ to hold the notes from https://inkscape.org/en/download/mac-os/
- and potentially others (e.g. https://inkscape.org/en/release/0.92.2/windows/64-bit/ if we keep the current tree structure as we need to explain .exe vs .msi (but might change? see next point...)
-
The structure /windows/32-bit/portable and /windows/64-bit/appx does not work.
While portable and AppStore versions are 32-bit and 64-bit respectively it is a distinction the user can not know. The user decides "Standalone vs. Portable (vs. AppStore)". -
The source package is platform independent.
Depending on the answer on landing page (i.e. if it detects OS) - from where would the source package be linked?
Apart from those there are a few more which would've been nice to have but which we probably can do without if really necessary:
-
Translations - Most navigational elements don't have translations (including the download buttons!). Are they even translatable?
- Same goes for content boxes - can they be translated (and if yes - where would translators go)?
-
The editor for content boxes is quite limited (i.e. no possibility to add images; at least that works from source, though, see example. -
The preformatted release notes look inelegant and make a bad impression. Could markdown be supported here?
Edited by Patrick Storz