Re: No Issue Tracker - Say it Ain't So! - Mailing list pgsql-hackers

From Steve Crawford
Subject Re: No Issue Tracker - Say it Ain't So!
Date
Msg-id CAEfWYyxzkkqaVC7kB3g7HQRieQiMbkm8vGN-HreQdqWTFR+cPg@mail.gmail.com
Whole thread Raw
In response to Re: No Issue Tracker - Say it Ain't So!  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: No Issue Tracker - Say it Ain't So!
List pgsql-hackers

On Mon, Sep 28, 2015 at 4:41 PM, Jim Nasby <Jim.Nasby@bluetreble.com> wrote:
Note that since they also offer a hosted solution we should use that to play with instead of trying to install it at this point.

Integrating the issue tracker looks like it's just a call to this API: http://doc.gitlab.com/ce/api/issues.html#new-issue. I don't normally do web development myself so I'd rather not figuring out how to setup a copy of the website to hack on, but if no one else wants to try it I can take a stab at it.

Presumably mirroring our git repository would work the same as it does for mirroring to GitHub. My guess is that would be enough to get the basic git/issue tracker integration working.

Commitfest could be tied in as well. Presumably each commitfest would be a milestone (http://doc.gitlab.com/ce/api/milestones.html) and each submission an issue.


One of the issues identified with  Github is that it is closed and commercial which goes against the expressed desires of the PostgreSQL community. As such, it's important to note that Gitlab seems to be in the "freemium" model with a "community" and an "enterprise" version so for comparison purposes we should only look at the features in the open-source community version:

Cheers,
Steve

pgsql-hackers by date:

Previous
From: Petr Jelinek
Date:
Subject: Re: track_commit_timestamp and COMMIT PREPARED
Next
From: Alvaro Herrera
Date:
Subject: Re: Rework the way multixact truncations work