good news :) This week I stopped working on Krusader waiting for this.
I have no relevant tasks to migrate/complete, so they could be abandoned. I have 3 revisions open, one of them require more tests (keyboard widget focus), the other two could be commited but I want to do that on Gitlab to check that all is working well.
We have also some old Revisions that Toni is handling, but as Phabricator will remain read-only for a while, we could migrate them manually without rush.
I think we'll handle the commits through issues/merge requests (I'm lurking major teams/repo to see how they work). As we are a small team, the basic idea is to create an issue (optional, because we could keep the discussion on the merge request) and a related marge request (directly on master branch). I still didn't get if Bugzilla will integrate with invent, I'm sure that normal users won't open issues.
I haven't tested yet if forked repositories can be synced upstream (it's a paid feature on gitlab); this means we could create merge requests from the fork directly to the upstream/master; this will keep the main repo cleaner, but as long as we delete branch when doing the merge requests, this feature is not essential (it could be messy when there are many requests opened).
On domenica 10 maggio 2020 09:56:54 CEST Yuri Chornoivan wrote:
> ---------- Forwarded message ---------
> Тема: Migration to Gitlab -- Update
> Дата: неділя, 10 травня 2020 р., 10:48:50 EEST
> Від: Ben Cooksley <bcoo...@kde.org>
> Кому: kde-core-devel <kde-cor...@kde.org>, kde-devel <kde-...@kde.org>
> Копія: sysadmin <sysa...@kde.org>
> Good morning all,
You received this message because you are subscribed to the Google Groups "krusader-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to krusader-deve...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/krusader-devel/24458123.1r3eYUQgxm%40slayer.gengisdave.org.
P.S. https://invent.kde.org/websites/krusader-org has also been created.
> Hi all,
> Looking at other projects, we should create some labels to use on merge
> requests; take a look at Krita
> (https://invent.kde.org/graphics/krita/-/labels), they use Gitlab since
> the beginning of the year.
I've looked for other label systems in:
and, for Krusader, the label system that is seen in https://invent.kde.org/graphics/krita/-/labels seems to be better, at least for me. Thank you all!
> I've created some label:
> Needs Review, Needs Changes and Approved will refer to the usual MR
> Bugfix, Wishlist, Feature Request and Documentation are the applied to
> describe what the MR does; the first two are related with bugs.kde.org and
> Documentation is used when we change something in doc/
> You are free to change descriptions/names/colours.
Just a question, is the meaning of the "Feature Request" label very different from the "Wishlist" one?
> The slight difference is that wishlist is related to a bug filled, while
> feature request isn't. On a second thought, I would drop the "wishlist"
> label using "feature request" paired with "bugfix" to point a wishlist bug,
It looks good to me (TM😊).
> I would also add a new label called "Improvement" for janitor works (like
> code improvement, compiler fixes, etc.).
I'm thinking that, since practically everything committed somehow improves Krusader, and because that label is also not used in the Krita label system, not adding that label would clarify the processes. In the commits I would keep the system of adding texts like "FIXED:", "ADDED:", etc. that allows later executing
$ git log v2.7.2.. | grep 'FIXED:\|ADDED:\|UPDATED:\|CHANGED:\|REMOVED:' | sort
to get information for the ChangeLog file, and to get a general impression.
In https://invent.kde.org/websites/krusader-org we can use the same labels in order to simplify its maintenance (e.g. everything applied to one label system it would be easily applied to the other one), or do you think that it would be better to use different ones?
> For the website we don't have to clarify with a label what the MR
> does, I think the title itself will be enough.
> On the other hand, the status labels "Needs review", "Needs changes" and
> "Approved" are useful.
All right! I've added those labels to https://invent.kde.org/websites/krusader-org
using the same names, descriptions and colors.