Re: Moving bugs to Phabricator

Hi, On 3 February 2016 at 20:27, Bryce Harrington wrote: > On Wed, Feb 03, 2016 at 12:25:26PM +, Daniel Stone wrote: >> On 2 February 2016 at 20:28, Bill Spitzak wrote: >> The workboard columns aren't fixed in the current single-column >> format:

Re: Moving bugs to Phabricator

Hi, On 2 February 2016 at 20:28, Bill Spitzak wrote: > Can you make a clone of the current Bugzilla state in Phabricator so that we > can see what it looks like? Good idea! Here they are: https://phabricator.freedesktop.org/project/board/100/

Re: Moving bugs to Phabricator

On Wed, Feb 03, 2016 at 12:25:26PM +, Daniel Stone wrote: > Hi, > > On 2 February 2016 at 20:28, Bill Spitzak wrote: > > Can you make a clone of the current Bugzilla state in Phabricator so that we > > can see what it looks like? > > Good idea! Here they are: >

Re: Moving bugs to Phabricator

Hi, It seems that opening any of these links requires a login. A valid use case for bug trackers is something like: * user searches web for issue keywords (eg. "wayland has no ssd!") * results include link to bug * user views bug report Requiring a login will create more hassle and reduce the

Re: Moving bugs to Phabricator

Hi, On 3 February 2016 at 15:56, Mike Blumenkrantz wrote: > It seems that opening any of these links requires a login. A valid use case > for bug trackers is something like: > > * user searches web for issue keywords (eg. "wayland has no ssd!") > * results include link to bug

Re: Moving bugs to Phabricator

Can you make a clone of the current Bugzilla state in Phabricator so that we can see what it looks like? On Tue, Feb 2, 2016 at 7:43 AM, Daniel Stone wrote: > Hi, > As previously discussed with a few people (when it was much more in > its infancy than now), I'd like to

Moving bugs to Phabricator

Hi, As previously discussed with a few people (when it was much more in its infancy than now), I'd like to move our bug tracking from Bugzilla to Phabricator. There's a few reasons behind this. Phabricator is actually a pretty decent suite of utilities, including repository browsing and code

Re: Moving bugs to Phabricator

The current major issue with Phabricator for me currently is that it doesn't support patch-based code review, unless this has changed in the meantime: http://stackoverflow.com/questions/20756320/how-to-prevent-phabricator-from-eating-my-commit-history ( The linked article has since moved to