[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-kimageshop
Subject:    Re: Winding down Phabricator
From:       Nicolás_Alvarez <nicolas.alvarez () gmail ! com>
Date:       2020-06-21 16:49:58
Message-ID: 124F1F99-41AD-4DB4-92FB-6FD0FCD1A53D () gmail ! com
[Download RAW message or body]

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* want people to use GitLab \
merge requests instead for new reviews. We may disable creation of new Phabricator \
reviews in the future.

- Automatic closing of tasks and reviews based on commit messages (like "Fixes \
T1234") doesn't work anymore, so you will have to close them manually.

-- 
Nicolas

> On 21 Jun 2020, at 13:21, L. E. Segovia <amy@amyspark.me> wrote:
> 
> 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
> > 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 Tasks left on Phabricator.
> > As interacting with repositories isn't a core requirement for this
> > functionality, we've now taken the step of disabling all repository
> > functionality on Phabricator.
> > This means that going forward, repositories will no longer be
> > browsable on Phabricator, nor will commit information be visible on
> > Phabricator. Additionally, actions normally taken via hooks (such as
> > "Differential Revision" and "Fixes Txxx") will no longer work.
> > Should anyone have any questions regarding this, please let us know.
> > Thanks,
> > Ben Cooksley
> > KDE Sysadmin
> 
> Best regards,
> 
> amyspark
> -- 
> amyspark 🌸 https://www.amyspark.me


[prev in list] [next in list] [prev in thread] [next in thread]