Hi Ben,
We GSoC students (at least in the Krita project) have been requested to
keep track of our progress via Phabricator tasks. Must we manually link
to changes now?
On 21/06/2020 03:38, Ben Cooksley wrote:
Hi all,
With the completion of Phase 1 of our move to Gitlab, all code review
acti
Phabricator will stay running for now since there are many pending tasks and
reviews on it. We also need to archive reviews for read-only access before we
shut it down, which will take some time.
- You can continue using Phabricator tasks.
- Phabricator code reviews still work, but we *really*
Hi,
thanks for putting so much effort in the transition.
We, as the German translation team, use Phabricator for reviewing the
work of casual contributors. I wonder how other teams handle this.
I am not saying, Phabricator going away will break our workflow
completely but it is a good way to
Hi all,
With the completion of Phase 1 of our move to Gitlab, all code review
activity should now be taking place on Gitlab, with only residual
reviews being cleaned out of Phabricator (which hopefully we're
already well underway with - please start this if you haven't already)
This leaves just T
