Issue tracking thoughts

[Thomas Braun]

The recent bash vulnerabitlity showed that most of the
git-on-windows-based-on-msysgit users don't find the correct issue
tracker. And it is not only the
5-second-creation-time-issue-noob-creator but also more experienced people.

This is therefore a constant point of annoyance for the devs, as it is
work, and for the users, as they are send from A to B and don't really
understand the structure.

And as we now have three different projects in the git-for-windows
organization, this will become an even bigger problem.

Therefore this is something I like to tackle differently for the
git-for-windows organization.

Some options spring to my mind:

- Make it possible to move issues from one project to the other.

- One issue tracker together with labels. Preferrably in the
git-for-windows/git project. Issues belonging to sdk or sdk-packages are
tagged appropriatley. PRs are oviously opened at the appropriate projects.

- External issue tracker. I guess we all have some webspace available.

- Without issue tracker, just mails on the mailinglist as git upstream does.

Thoughts?

[Johannes Schindelin]

Hi Thomas,

I agree that we need something that relieves us from the burden to manage
tickets.

Personally, I'd be in favor of the "git-for-windows/git with labels"
solution.

Ciao,
Dscho

[Sebastian Schuberth]

On Tue, Sep 30, 2014 at 12:00 PM, Thomas Braun
<thomas...@virtuell-zuhause.de> wrote:

> - One issue tracker together with labels. Preferrably in the
> git-for-windows/git project. Issues belonging to sdk or sdk-packages are
> tagged appropriatley. PRs are oviously opened at the appropriate projects.

That basically sounds fine, but are you able to auto-close issues with
PRs [1] then if issues and PRs are in different projects?

> - Without issue tracker, just mails on the mailinglist as git upstream does.

That would be my second choice.

[1] https://help.github.com/articles/closing-issues-via-commit-messages

--
Sebastian Schuberth

[Thomas Braun]

Am Di, 30.09.2014, 23:10 schrieb Sebastian Schuberth:
> On Tue, Sep 30, 2014 at 12:00 PM, Thomas Braun
> <thomas...@virtuell-zuhause.de> wrote:
>
>> - One issue tracker together with labels. Preferrably in the
>> git-for-windows/git project. Issues belonging to sdk or sdk-packages are
>> tagged appropriatley. PRs are oviously opened at the appropriate
>> projects.
>
> That basically sounds fine, but are you able to auto-close issues with
> PRs [1] then if issues and PRs are in different projects?

Yes, the reference you cited has even an example on that.

[Sebastian Schuberth]

On Thu, Oct 2, 2014 at 12:20 AM, Thomas Braun

<thomas...@virtuell-zuhause.de> wrote:

>>> - One issue tracker together with labels. Preferrably in the
>>> git-for-windows/git project. Issues belonging to sdk or sdk-packages are
>>> tagged appropriatley. PRs are oviously opened at the appropriate
>>> projects.
>>
>> That basically sounds fine, but are you able to auto-close issues with
>> PRs [1] then if issues and PRs are in different projects?
>
> Yes, the reference you cited has even an example on that.

Hehe, thanks for checking ;-)

[Thomas Braun]

Okay, so it is decided that we enable issues only on git-for-windows/git
and use labels to distinguish the responsible repository.

I'll enable issues in the following days, if nobody speaks up.

Thomas

--