[Bf-committers] Should we change the splash image when the version number changes?

[Gaia Clary]

Maybe it is as simple as displaying the splash screen in greyscale...
What about something like this:

if version_cycle == "Alpha":
   display_the_splash_in_grey_scale(saturation=0.1) #Almost black&white

see: http://pasteall.org/pic/show.php?id=a18beb5d36f5dfd320f091278489a294

That would be automatic.
Just a stupid thought before coffee :)
Gaia

On 10/11/2019 5:37 PM, Brecht Van Lommel wrote:
> We could consider adding a new splash at the start of the release cycle,
> instead of at the end. It makes some sense for a specific Blender version
> to always have the same splash.
>
> On Fri, Oct 11, 2019 at 5:29 PM Dalai Felinto <dfelinto at gmail.com> wrote:
>
>> Hi Antonio,
>>
>> What you propose is not really solving the problem. To have a new
>> splashscreen from 2.81 and still use the 2.80 splashscreen for 2.82
>> (master) would be even more strange in my opinion.
>>
>> In a way what we have now is no different than having a stable Blender with
>> a splash, and master with the same one. Which is how we did for ages,
>> without any major complication.
>>
>> So initially the plan is to change the splash only when we enter bcon5. You
>> do see a different alpha/beta version in the splashscreen, and that will
>> have to suffice for now.
>>
>> All that said, I actually believe that the true reason to change the splash
>> at the very last moment is because there is a lot of expectations in regard
>> to that. So it is nice to align the hype of the splash reveal with the
>> release of a new version of Blender.
>>
>> Regards,
>> Dalai
>>
>> --
>> blendernetwork.org/dalai-felinto
>> www.dalaifelinto.com
>>
>>
>> Em sex, 11 de out de 2019 às 10:44, antonioya blend <blendergit at gmail.com>
>> escreveu:
>>
>>> Hi all,
>>>
>>> Until now, when we had a version, the splash was changed at the end when
>>> the release was made. With the new way of working, the version is changed
>>> at the beginning and appears in the splash, and we follow the development
>>> in the master branch. The release of the previous one has its own branch
>>> (blender-v2.81-release).
>>>
>>> If we decide that master is the new version (in this case 2.82), the
>>> logical thing would be to change the splash at the same time that the
>>> version change is made, so the developing version would have a different
>>> splash. Now it is very strange to have a different version in the splash,
>>> but with the same image from the previous version. Perhaps that splash
>>> could be the definitive of 2.82 or something more generic like the one we
>>> used during the development of 2.80.
>>>
>>> This is just an idea that I wanted to share with you to see the different
>>> opinions. Anyway, if you think it is not necessary, forget it.
>>>
>>> Regards,
>>> Antonio Vazquez
>>> _______________________________________________
>>> Bf-committers mailing list
>>> Bf-committers at blender.org
>>> https://lists.blender.org/mailman/listinfo/bf-committers
>>>
>> _______________________________________________
>> Bf-committers mailing list
>> Bf-committers at blender.org
>> https://lists.blender.org/mailman/listinfo/bf-committers
>>
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> https://lists.blender.org/mailman/listinfo/bf-committers