On Sun, Mar 24, 2019 at 8:46 AM Tomaz Canabrava wrote:
>
> People, and the apps that are still in svn, like kmldonkey, will be migrated
> too ?
Subversion will not be impacted in any form.
They'll remain outside of Gitlab.
Cheers,
Ben
>
> Em sáb, 23 de mar de 2019 às 03:31, Ben Cooksley escre
People, and the apps that are still in svn, like kmldonkey, will be
migrated too ?
Em sáb, 23 de mar de 2019 às 03:31, Ben Cooksley
escreveu:
> On Tue, Mar 19, 2019 at 9:26 PM Ben Cooksley wrote:
> >
> > Hi all,
> >
> > Over the past few weeks we've had a discussion on whether we'd like to
> >
On Tue, Mar 19, 2019 at 9:26 PM Ben Cooksley wrote:
>
> Hi all,
>
> Over the past few weeks we've had a discussion on whether we'd like to
> migrate from Phabricator to Gitlab, for handling both our code reviews
> as well as internal tasks (user facing bug reports are explicitly out
> of context a
On Tue, Mar 19, 2019 at 10:47 PM Nate Graham wrote:
>
> One thing I'd really like to not lose is the review status feature
> (approved/changes requested/etc). I've head that this is EE only. Is there
> any word on getting that added to our package?
We'll look into discussing this with them.
>
One thing I'd really like to not lose is the review status feature
(approved/changes requested/etc). I've head that this is EE only. Is there any
word on getting that added to our package?
Other than that, I think I think what Gitlab offers over Phabricator is either
a significant win or else j
Hi all,
Over the past few weeks we've had a discussion on whether we'd like to
migrate from Phabricator to Gitlab, for handling both our code reviews
as well as internal tasks (user facing bug reports are explicitly out
of context at this time)
Based on the comments the overall consensus seems to
