No objections, seems like a really good idea.
I am *highly* in favor of a bot to do this automatically in response to
the presence of the "cherry-pick" label and appropriate milestone to
cherry-pick to being defined, which would also help with people
remembering to do those things.
Nate
O
Hi Michael, I've been asking to make a new latte-dock bugfix release to
include this Wayland fix
https://invent.kde.org/plasma/latte-dock/-/commit/1d468a94e931d684f1ec180584eaa1d25765f100
I've made a tar from that 0.10 branch, could you check and tell me it's
good to release?
http://embra.edinbur
+1, thanks for bringing this up, this is also something I'd pondered at times.
Adding sysadmin on CC as automating this has been brought up and
AFAIR this was something they'd been working on before.
Aleix
On Wed, Nov 16, 2022 at 11:12 AM Vlad Zahorodnii
wrote:
>
> Hi,
>
> At the moment, we ha
Hi,
> I propose to make creating MRs for bugfix backports mandatory:
Agreed. I have also been guilty of cherry-picking changes on a whim from
my phone before going to bed, which is not something we want for the
stable branch.
Back when we were still forward-merging I was at least compiling t
Hi,
At the moment, we have the following bugfixing workflow in plasma:
* fix a bug in master
* cherry pick the fix to stable branch(es)
The last step is usually done without creating a MR. If there is a merge
conflict, some people do create a MR though.
I propose to make creating MRs for bug
