Re: Misleading message on download page of our spin
Am 27.11.2018 um 07:51 schrieb Miro Hrončok:
On 26. 11. 18 20:18, Kevin Fenzi wrote:
> On 11/26/18 6:32 AM, Johannes Lips wrote:
>> Hi all,
>>
>> when preparing for installing fedora on my new laptop, I stumbled
>> across
>> this weird message on the download page
>> https://spins.fedoraproject.org/xfce/download/index.html.
>> "Although this spin failed to compose for the final release, this test
>> compose contains fixes over the final content to allow for a successful
>> compose and should meet most users' needs. You can verify the test
>> compose image with a dedicated CHECKSUM file for 64-bit
>>
<https://dl.fedoraproject.org/pub/alt/unofficial/releases/29/x86_64/Fedora...
>>
>> and 32-bit
>>
<https://dl.fedoraproject.org/pub/alt/unofficial/releases/29/i386/Fedora-U...
>>
>> images."
>> To me this is totally confusing for new users and I don't really
>> know if
>> it's a really good idea to show this message there. Of course I think
>> it's good to be honest and transparent, but this message needs a
>> certain
>> level of understanding of the fedora release process and without it, it
>> just confuses people.
>> I mean who cares if the final compose failed, if updated images are now
>> available and are working? Is it mandatory to display such a message if
>> the final release is updated?
>>
>> I really think we can do better, since the spins do look like an
>> unloved
>> stepchild enough already.
>
> Well, I agree it's confusing... do you have a recommendation for better
> wording? Or you suggest we just don't say anything?
"This spin was built after the official Fedora 29 release. Hence the
images are placed in the /unofficial/ directory on the mirrors, but
you shouldn't worry about that."
Another option would be to just drop the
following: "..., this test
compose contains fixes over the final content to allow for a successful
compose and should meet most users' needs." to emphasize that's it not
just a test build, but rather a tested update, which was necessary to
get a working image.
Perhaps sell it more like an update to the final release, which then
needs to be in the unofficial directory, but is still the real thing.
Johannes
> If we don't say anything the 'unofficial' might cause some issues.
>
> Really the best thing would be to make sure everything is actually built
> and tested before release. ;(
Well... Shit happens.