We can now use gitlab issues, how are we going to use them?

Dmitry Kazakov dimula73 at gmail.com
Tue Jul 22 09:59:17 BST 2025


Well, no, I was not talking about your specific issues :) I was talking
about an abstract case of a finished "milestone" and how it should be
transitioned to the release milestone.

The problem is that we have a problem of noting what came into release and
what not. I personally had problems with keeping notes for the release
announcement for the upcoming release. We need a place to keep them.

Generally, I'm trying to approach the "issues problem" from a different
side: from the side of the management problems we have. Here is the
tentative problems we have that could be addressed with the help of GitLab
issues:

1) It is difficult to track status of big projects.
2) It is difficult to discuss some individual issues/bugs/problems we have
(we have to use IRC for that and it breaks over timezone differences).
3) It is difficult to track what fixes/features reached which release
4) It is difficult to plan what issues/features should have a priority to
reach some specific release (well, we currently don't really have enough
manpower to plan so deep, but it used to be an issue before)
5) It is difficult to leave notes for the release notes for the upcoming
release, e.g. " AppImage runtime has changed, use this manual if you have
any issues"

Looking at this list of "requirements", it doesn't look mandatory to have
milestones for the releases, though I'm not very sure.

On Tue, Jul 22, 2025 at 10:49 AM Wolthera <griffinvalley at gmail.com> wrote:

> On Tue, Jul 22, 2025 at 10:45 AM Dmitry Kazakov <dimula73 at gmail.com>
> wrote:
> >
> > Then how should we transition your "Text Tool" milestoned tasks into
> "Release 5.3.0"? Only the "root" issue should belong to "Release 5.3.0"?
> > --
> > Dmitry Kazakov
>
> I was hoping we'd first get an idea of how we want to use issues and
> milestones and the like, before we transition the issues. :) Might
> even be some don't get transitioned, I think we need to figure out
> what is comfortable first.
>
> Do you have a preference we move those issues into Krita main?
>
> --
> Wolthera
>


-- 
Dmitry Kazakov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kimageshop/attachments/20250722/80c64bdf/attachment-0001.htm>


More information about the kimageshop mailing list