[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Allura/SourceForge to Gitlab migration
From: |
Carl Sorensen |
Subject: |
Re: Allura/SourceForge to Gitlab migration |
Date: |
Mon, 9 Apr 2018 18:13:22 +0000 |
User-agent: |
Microsoft-MacOutlook/10.b.0.180311 |
On 4/9/18, 12:06 PM, "lilypond-devel on behalf of James Lowe" <address@hidden
on behalf of address@hidden> wrote:
Hello,
Does Gitlab really only just have 2 status for an 'issue' (Open and Closed)
or can this be refined/configured so I (as Patch Meister) can keep track of
what is 'making its way through' the patch countdown and is at the one of the
three basic states?
For example how would one know of the ~1000 issues which ones need to be
reviewed and which ones are ready to push?
In my GitLab usage we use tags. We'd just tag it Review, or Needs Work, or
Countdown, or Push. It's pretty easy to do that, and GitLab now has a front
page that allows you to easily create lists of all Review, Needs Work,
Countdown, Push issues.
Thanks,
Carl
- Allura/SourceForge to Gitlab migration, Federico Bruni, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration, Karlin High, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration, Karlin High, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration, James Lowe, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration, Urs Liska, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration, Carl Sorensen, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration, Karlin High, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration, Karlin High, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration, Karlin High, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration, Federico Bruni, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration, Urs Liska, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration, Karlin High, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration, Carl Sorensen, 2018/04/09