Krita.org - update wording/description for Krita Next and Krita Plus
Closed, ResolvedPublic

Description

With the state of these two branches that point to these versions of Krita, we might need to update the text a bit to be more descriptive. This is the conversation that was held on IRC.

<halla> Should we take the krita plus download down until the 5.0 release?
<Wolthera_laptop> I am neutral in this.
<emmetpdx[m]> Why?
<windragon> maybe not take it down, because it serves as the actual alpha build of 5.0
<dmitryK|quack> halla: but Krita Plus is already linked to krita/5.0, isn't it?
<halla> It's not reallty stable + bugfixes anymore
<halla> dmitryK|quack: yes, it is
<dmitryK|quack> halla: it can be used by translators
<emmetpdx[m]> Oh I see
<windragon> I think the wording should be changed
<windragon> but hiding it might be too much
<windragon> *description wording
<dmitryK|quack> halla: translators cannot use master builds for translations, afaict
<raghukamath> dmitryK|quack: translators can use both master and stable
<raghukamath> right now 5.0 is in stable branch of translation
<windragon> scottyp: ping, can the description for Krita Plus be changed on the website?
<raghukamath> and master is trunk
<scottyp> windragon: yes
<halla> windragon: do you have a suggestion for the text?
<raghukamath> it is one of the headache of the translation team lead, to figure out which app uses which branch :(
<windragon> actually, maybe we should hide Krita Next and use its description for Krita Plus?
<dmitryK|quack> I would prefer to hide Krita Plus then
<scottyp> krita next is how people are currently testing nightly builds of Krita 5.0, right?
<windragon> or, just write "daily builds that contains new features that will be included in Krita 5.0" and keep Krita Next
<scottyp> we can start a task for it

I am not quite sure how the branches have changed...so we need to clarify what these builds actually mean now.

This is what it currently says

scottpetrovic claimed this task.
scottpetrovic updated the task description. (Show Details)
scottpetrovic added subscribers: rempt, dkazakov.
rempt added a comment.Jul 13 2021, 6:41 AM

I would propose

Krita Plus: what will become Krita 5. Install at your own risk! It's alpha!
Krita Next: still mostly the same as Krita Plus, but will start having new features soon. Install at your own risk!

Might be worth making the message more generic so we can switch back and fro without having to write a new one every time?

When stable branch just branched from master and is significantly ahead of the last release:

  • Krita Plus: Daily builds of what will become Krita ${next_release_version}. Install at your own risk! It's alpha!
  • Krita Next: Daily builds mostly the same as Krita Plus, but may be slightly ahead with some new features. Install at your own risk!

When stable branch is really mostly bugfixes:

  • Krita Plus: Daily builds that only contain bug fixes on top of ${last_release_version}.
  • Krita Next: Daily builds that contain new features for ${next_release_version}, could be unstable.

I would rather keep this simple, so just having one version of the text for each would be better. I would rather change the text...or make the text a variable, than having some type of branching logic.

Maybe for now, I could create two new variables in WordPress that can control this.

  1. krita-plus-description
  2. krita-next-description

That way it will be easy to change it depending on what branches we are pointing to in the future. It is hard to know what change we might make next.

rempt added a comment.Jul 20 2021, 2:39 PM

Sounds good to me

scottpetrovic closed this task as Resolved.Jul 22 2021, 10:00 PM

I just created two new variables on the krita download page where you can change out the Krita Plus and Next descriptions.

Each language has their own variable, so you can do translations on those pages as well for the text. For now the other languages are just using what they previously had.

Hi @scottpetrovic I noticed that the description for "Krita Next" doesn't seem to be using the custom variable. It's in English for zh-hk and zh-tw.

@alvinhochun - woops. Good catch. I just updated the template so it should be working now.

We have two types of site variables. Sometimes the English version controls all languages, other times languages do their own thing. For example when we update the download link we want that to update the link across all languages, not just the english site.