Am 23.02.2018 um 02:10 schrieb Eduard Braun:
Am 22.02.2018 um 18:13 schrieb Maren Hachmann:
Just an update on this:
I've updated the installation instructions for the master branch on the website, and added them for the 0.92.x branch.
So you can now guide your testers to the website's download section.
What still needs some work is the macOS part, as I have no clue what a Mac user is meant to do with the artifact files they can download (aside from unpacking them, that is). I've messaged Tim Sheridan for help with instructions, and I hope that Miguel will be able to try them out as a user once we have them.
Link for 0.92.x branch: https://inkscape.org/en/release/0.92.x/
Link for master branch: https://inkscape.org/en/release/master/
Maren
Cool! I like the landing pages, they look welcoming and are concise while having most of the important information. A minor issue: I'd drop the "+devel" from the "0.92.x" release background (0.92.x+devel" is not a thing).
- Yeah, I know. I thought of it as an option to make it visually clear that it's a development version, in case someone ends up on that page unintentionally, thinking they'd be downloading a released version. I've removed the +devel now, but if anyone wants to change the picture to make it better, that would be fine, too.
On that matter: The term "0.92+devel" is not that great to start with - people unfamiliar with it wondered before if "0.92.2" is not more recent than "0.92+devel", so maybe we should make it extra clear in the description that "master" is the latest (unstable) development version and 0.92.x is the latest (mostly stable) release branch.
- I've tried to make it clearer - if you like, you can still improve on it, I think you've got access, Eduard. (tbh. I'm wondering, too, why it's not called after the next version, but after the previous one - or why it's not just 'master' everywhere)
What I don't like are the AppVeyor CI build download notes for Windows - they are complicated as hell :-D I actually hope I can simplify that at some point (e.g. by storing the link to the latest successful build somewhere so it can be downloaded directly).
- Good idea :)
It's also not exactly helpful that the information is always scattered across three pages ("Release", "Platform", and "ReleasePlatform" pages) but that's a general issue I see with the Releases App that is true for stable releases, too.
- Yeah, it was complicating things that the parent versions were filled in. E.g. there was the Windows store download included in the description of 'Windows', and to get rid of that for development versions, I had to put it into its own release platform. Also, I've had to copy some of the more general info into the child releases, to make them show all the important content.
We should really not have any information in parents that does not apply to *all* of their children. Else it's not helping, but means useless duplication of contents.
@Martin: One idea I just have - do you think those could be unified to be on the same page? More like a tree view with sections that expand when clicked rather than individual pages for all of the levels? Roughly like https://www.gimp.org/downloads/ but more structured (so the "parent" information always stays visible and the child is expanded per user-selection down through all the three levels).
- I think Jabier wrote most of the UI for releases. Any layout (within html, CSS and javascript limits) is possible, only takes someone to create it.
Regards, Maren
Regards, Eduard