New Krita Stable Branch: krita/4.0

[Alvin Wong]

Hi all,

When you make a commit on either branch and it needs to be on both branch, here
are some suggestions:

- If you already knew the commit should go onto both branches, I suggest making
  it on the `master` branch first.
- Push the commit on the first branch before cherry-picking it to the other, so
  that the commit hash is fixed.
- Cherry-pick the commit to the other branch by running:
      git cherry-pick -x <commit_hash>
  The `-x` flag will append the hash of the original commit to the new commit
  message so that they can be cross-referenced on Phabricator.

Please do cherry-pick your commits when appropriate to reduce Boud's workload!

Best Regards,
Alvin

2018-03-02 2:17 GMT+08:00 Boudewijn Rempt <boud at valdyas.org>:
>
> Hi!
>
> We're going to release Krita 4.0 in two weeks, if all goes well, so I've made
> a Krita 4.0 stable branch. This replaces the old krita/3.3 stable branch.
>
> I need to find my notes to figure out all the places where this should be
> changed for ci, translations and things like that.
>
> For development, until we release, please do your bug fixes in the branch, and
> make sure those commits are also available in master. Master is now open for
> new stuff, too!
>
> --
> Boudewijn Rempt | https://www.valdyas.org | https://www.krita.org
>
>