Sebastian Pettke skrev den 2018-01-24 16:36:
unfortunately I don't have the permission to push and according to
this:
https://community.kde.org/Infrastructure/Phabricator#Workflow
I also can't use arc land without a full KDE Developer Account (I
don't have one).
Might someon
unfortunately I don't have the permission to push and according to this:
https://community.kde.org/Infrastructure/Phabricator#Workflow
I also can't use arc land without a full KDE Developer Account (I don't have
one).
Might someone else with the necessary permissions please p
> >> Sebastian Pettke skrev den 2018-01-22 21:00:
> >> > Hi,
> >> >
> >> > I tried to submit a patch using Phabricator:
> >> > https://phabricator.kde.org/D10014
> >> >
> >> > but it won't appear on this page:
>
Sebastian Pettke skrev den 2018-01-23 23:38:
On January 23, 2018 at 10:30 AM Dag wrote:
Sebastian Pettke skrev den 2018-01-22 21:00:
> Hi,
>
> I tried to submit a patch using Phabricator:
> https://phabricator.kde.org/D10014
>
> but it won't appear on this page:
> h
> On January 23, 2018 at 10:30 AM Dag wrote:
>
> Sebastian Pettke skrev den 2018-01-22 21:00:
> > Hi,
> >
> > I tried to submit a patch using Phabricator:
> > https://phabricator.kde.org/D10014
> >
> > but it won't appear on this page:
Sebastian Pettke skrev den 2018-01-22 21:00:
Hi,
I tried to submit a patch using Phabricator:
https://phabricator.kde.org/D10014
but it won't appear on this page:
https://phabricator.kde.org/project/profile/23/
Is this expected behaviour or is there anything I am missing or should
d
Hi,
I tried to submit a patch using Phabricator:
https://phabricator.kde.org/D10014
but it won't appear on this page:
https://phabricator.kde.org/project/profile/23/
Is this expected behaviour or is there anything I am missing or should do now?
Best regards,
Sebastian Pettke
On Friday August 25 2017 07:33:43 Ben Cooksley wrote:
Hi,
>> Note that due to how Reviewboard stores diffs and reproduces them for
>> use, some reviews may have decayed and may no longer be readable. This
>> is due to short-hashes which are used by Git/Reviewboard in diffs now
>> having collision
On Mon, Aug 28, 2017 at 8:20 PM, René J.V. Bertin wrote:
> On Friday August 25 2017 07:33:43 Ben Cooksley wrote:
>
> Hi,
Hi Rene,
>
>>> Note that due to how Reviewboard stores diffs and reproduces them for
>>> use, some reviews may have decayed and may no longer be readable. This
>>> is due to s
On 25/08/2017 5:41 AM, "Albert Astals Cid" wrote:
El dijous, 24 d’agost de 2017, a les 21:07:49 CEST, Ben Cooksley va
escriure:
> Hi all,
>
> The following is Sysadmin's suggested plan for the retirement of
> Reviewboard now that Phabricator is fully up and running fo
El dijous, 24 d’agost de 2017, a les 21:07:49 CEST, Ben Cooksley va escriure:
> Hi all,
>
> The following is Sysadmin's suggested plan for the retirement of
> Reviewboard now that Phabricator is fully up and running for hosting
> of code reviews.
>
> Phase 1:
Hi all,
The following is Sysadmin's suggested plan for the retirement of
Reviewboard now that Phabricator is fully up and running for hosting
of code reviews.
Phase 1: Commences September 2: All repositories are closed for
accepting new reviews on Reviewboard. A notice is added to the top o
Hi everyone,
Just repeating my last email on this subject as it seems some folks
have missed the previous memo.
All issues with Phabricator should be logged at
https://phabricator.kde.org/tag/phabricator/ - not with upstream.
This is being done to avoid duplicate tasks, and to allow us to
2017-02-02 7:23 GMT-03:00 René J.V. Bertin :
> On Thursday February 2 2017 22:09:34 Ben Cooksley wrote:
>
>>For those who dismiss decay as an issue - problems with previous
>>Reviewboard upgrades not taking cleanly have resulted in some reviews
>>being damaged, causing their diffs to become unavail
On Fri, Feb 3, 2017 at 11:37 PM, René J.V. Bertin wrote:
> On Thursday February 2 2017 21:50:38 Nicolás Alvarez wrote:
>
>>You missed the point. This "bit rot" is not about disk damage but
>>about software incompatibility. ZFS doesn't help with that...
>
> You mean diffs that no longer apply clean
René J.V. Bertin ha scritto:
> On Thursday February 2 2017 21:50:38 Nicolás Alvarez wrote:
>
>> You missed the point. This "bit rot" is not about disk damage but
>> about software incompatibility. ZFS doesn't help with that...
>
> You mean diffs that no longer apply cleanly? In that case you miss
On Thursday February 2 2017 21:50:38 Nicolás Alvarez wrote:
>You missed the point. This "bit rot" is not about disk damage but
>about software incompatibility. ZFS doesn't help with that...
You mean diffs that no longer apply cleanly? In that case you missed our point.
Being able to consult inte
Could this be of any help?
https://www.cloudpipes.com/integrations/phabricator/reviewboard
A paying service, but if the integration allows migration of existing
ReviewBoard stuff into Phabricator a well-timed 2-month trial (or multiple
thereof ;)) might suffice?
There's also this:
Hi all,
As a starting point: keeping the software itself running is a
non-starting option from my perspective. It's going to be shutdown.
This is purely to reduce the amount of maintenance effort we have to
expend in keeping our systems running.
There is an enormous amount of software and other s
On Thu, 2 Feb 2017 07:45:15 +1300
Ben Cooksley wrote:
[snip]
>
> I think that we need some cleanup on the old reviews (Albert Astal Cid
> started
> some time ago) and more important strongly tell new users (and old
> users) to use Phabricator. I don't think that anyone want
On Wednesday February 01 2017 23:03:53 Albert Astals Cid wrote:
> You'd be surprised (yes i have a script that actually applies the MRs and
> lots
> of them even very old apply).
Old also doesn't mean unmaintained. I have a number of RRs that I keep rebasing
because I'm still waiting for a gre
El dijous, 2 de febrer de 2017, a les 7:45:15 CET, Ben Cooksley va escriure:
> Anything older than that usually won't apply to the code anymore.
You'd be surprised (yes i have a script that actually applies the MRs and lots
of them even very old apply).
Cheers,
Albert
>>
>> Hi Rene,
>>
>> > >From this point forward, communities should be moving away from
>> >>
>> >>Reviewboard to Phabricator for conducting code review. Sysadmin will
>> >>be announcing a timeline for the shutdown of Reviewboard in
we need some cleanup on the old reviews (Albert Astal Cid
started
some time ago) and more important strongly tell new users (and old users) to
use Phabricator. I don't think that anyone wants to lose the work, but if a
review has not been touched in a few months maybe it's time to see it
ffline for good.
I'd offer to help during that period but without any experience with the
associated kind of sysadminship I'm not convinced that would be of much
value.
I take it you investigated whether there is any existing way to transfer
existing records from ReviewBoard to Phabricato
ote:
> >
> > Hi,
>
> Hi Rene,
>
> >
> > >From this point forward, communities should be moving away from
> >>Reviewboard to Phabricator for conducting code review. Sysadmin will
> >>be announcing a timeline for the shutdown of Reviewbo
communities should be moving away from
> >>
> >>Reviewboard to Phabricator for conducting code review. Sysadmin will
> >>be announcing a timeline for the shutdown of Reviewboard in the near
> >>future.
> >>
> > I hope that shutdown doesn't mean complete disc
Astal Cid started
some time ago) and more important strongly tell new users (and old users) to
use Phabricator. I don't think that anyone wants to lose the work, but if a
review has not been touched in a few months maybe it's time to see it is still
interesting.
If we start doing this now (o
On Wednesday, 1 February 2017 11:52:01 CET Alexander Zhigalin wrote:
> Completely agreeing with Rene, Luigi and Milian.
> All this sounds very sad to me.
> Phabricator is indeed very powerful and better for management stuff.
> But Differential is not even merely comparable to RB by
x27;d offer to help during that period but without any experience with the
associated kind of sysadminship I'm not convinced that would be of much value.
I take it you investigated whether there is any existing way to transfer
existing records from ReviewBoard to Phabricator? That would make the whole
issue moot.
R.
On Wed, Feb 1, 2017 at 9:26 PM, René J.V. Bertin wrote:
> On Wednesday February 1 2017 20:59:46 Ben Cooksley wrote:
>
> Hi
>
>>
>>While I have yet to test it, Reviewboard does use quite a bit of AJAX
>>and other dynamic resources - so I won't be surprised to find out that
>>the usual mechanisms fo
On Wednesday February 1 2017 20:59:46 Ben Cooksley wrote:
Hi
>
>While I have yet to test it, Reviewboard does use quite a bit of AJAX
>and other dynamic resources - so I won't be surprised to find out that
>the usual mechanisms for creating static copies of sites don't produce
>a workable result.
t;>>
>>> >From this point forward, communities should be moving away from
>>>> Reviewboard to Phabricator for conducting code review. Sysadmin will
>>>> be announcing a timeline for the shutdown of Reviewboard in the near
>>>> future.
>>&g
only resource also makes it possible to
download patchfiles and other resources that were added to reviews (which are
*not* available via mailing list archives).
And last but not least: knowing myself I'm quite likely (and surely not the
only one) to forget transfering open reviews to Phabricato
Ben Cooksley ha scritto:
> On Tue, Jan 31, 2017 at 11:36 PM, René J.V. Bertin
> wrote:
>> On Sunday January 29 2017 08:32:21 Ben Cooksley wrote:
>>
>> Hi,
>
> Hi Rene,
>
>>
>> >From this point forward, communities should be moving away from
&g
On Tue, Jan 31, 2017 at 11:36 PM, René J.V. Bertin wrote:
> On Sunday January 29 2017 08:32:21 Ben Cooksley wrote:
>
> Hi,
Hi Rene,
>
> >From this point forward, communities should be moving away from
>>Reviewboard to Phabricator for conducting code review. Sysadmi
rom
> >Reviewboard to Phabricator for conducting code review. Sysadmin will
> >be announcing a timeline for the shutdown of Reviewboard in the near
> >future.
>
> I hope that shutdown doesn't mean complete disconnect; it would probably
> be a loss of as-yet unknown i
On Sunday January 29 2017 08:32:21 Ben Cooksley wrote:
Hi,
>From this point forward, communities should be moving away from
>Reviewboard to Phabricator for conducting code review. Sysadmin will
>be announcing a timeline for the shutdown of Reviewboard in the near
>future.
I hope t
Hi everyone,
We've just completed the registration of all mainline repositories
(not including Websites or Sysadmin namespaced ones) on Phabricator.
Thanks go to Luigi Toscano for providing significant assistance with
this process.
>From this point forward, communities should be moving a
no answers, so start to
> wonder if reviewers has bee notified at all.
> Thought I added all, but can't really find out through phabricator, so
> consider this a ping :)
>
> Also, if somebody has a good workflow for this, please give me some hints!
>
> Cheers, Dag
--
regard
Add a patch for review some time ago, but have had no answers, so start
to wonder if reviewers has bee notified at all.
Thought I added all, but can't really find out through phabricator, so
consider this a ping :)
Also, if somebody has a good workflow for this, please give me some
16 at 07:46
Subject: [kde-community] Sunsetting of Infrastructure and the Phabricator
migration
To: kde-core-devel , informing about and discussing
non-technical community topics , kde-devel <
kde-de...@kde.org>, kde-doc-engl...@kde.org
Cc: "sysad...@kde.org"
== This mail is
On Wed, Jul 8, 2015 at 7:55 AM, Jaroslaw Staniek wrote:
> Hi,
Hi Jaroslaw,
> I am not sure this is a part of docs already, gogole does not confirms
> this. So putting here:
> "Special commands in comments can cause various effects, like closing
> a related task when a commit is pushed."
>
> http
Hi,
I am not sure this is a part of docs already, gogole does not confirms
this. So putting here:
"Special commands in comments can cause various effects, like closing
a related task when a commit is pushed."
https://secure.phabricator.com/T5132#69200
What do you think? Are these spells useful?
On 21 June 2015 at 22:45, Ben Cooksley wrote:
> On Mon, Jun 22, 2015 at 7:18 AM, Jaroslaw Staniek wrote:
>> On 21 June 2015 at 10:44, Ben Cooksley wrote:
@Ben I think the list is complete: master, calligra/x.y, frameworks.
>>>
>>> It should now be configured to do so.
>>> Autoclose Onl
On Mon, Jun 22, 2015 at 7:18 AM, Jaroslaw Staniek wrote:
> On 21 June 2015 at 10:44, Ben Cooksley wrote:
>>>
>>> @Ben I think the list is complete: master, calligra/x.y, frameworks.
>>
>> It should now be configured to do so.
>> Autoclose Only: master, frameworks, regexp(/^calligra\//)
>
> Ben, t
On 21 June 2015 at 10:44, Ben Cooksley wrote:
>>
>> @Ben I think the list is complete: master, calligra/x.y, frameworks.
>
> It should now be configured to do so.
> Autoclose Only: master, frameworks, regexp(/^calligra\//)
Ben, thanks!
One thing that probably needs clarification. From the ticket
On Sat, Jun 20, 2015 at 10:47 AM, Jaroslaw Staniek wrote:
> On 18 June 2015 at 10:30, Boudewijn Rempt wrote:
>> On Thu, 18 Jun 2015, Jaroslaw Staniek wrote:
>>
>>> Hi,
>>> We started to use/try phabricator for reviews, task management [1].
>>> During the
On 18 June 2015 at 10:30, Boudewijn Rempt wrote:
> On Thu, 18 Jun 2015, Jaroslaw Staniek wrote:
>
>> Hi,
>> We started to use/try phabricator for reviews, task management [1].
>> During the KDE admins, namely Ben Cooksley, are more than helpful to
>> tune things
On Thu, 18 Jun 2015, Jaroslaw Staniek wrote:
Hi,
We started to use/try phabricator for reviews, task management [1].
During the KDE admins, namely Ben Cooksley, are more than helpful to
tune things up to our workflows.
The difference between it and the reviewboard.kde.org in that
'autoc
Hi,
We started to use/try phabricator for reviews, task management [1].
During the KDE admins, namely Ben Cooksley, are more than helpful to
tune things up to our workflows.
The difference between it and the reviewboard.kde.org in that
'autocloses' revews (so-called revisions [2]) whe
On Friday, May 29, 2015 06:13:47 PM Jaroslaw Staniek wrote:
> Hi,
> I recommend spending a few minutes playing with Phabricator /
> Differential. Integrated reviews with plan/task tracking!
> Unlike gerrit, it does not seem a technocrats' tool that stays in the
> way and brea
Hi,
I recommend spending a few minutes playing with Phabricator /
Differential. Integrated reviews with plan/task tracking!
Unlike gerrit, it does not seem a technocrats' tool that stays in the
way and breaks your daily habits. Serious command line functionality
is included.
My simpl
Hi, Boud!
We should create a Calligra project on Phabricator then :)
On Thu, Apr 30, 2015 at 1:18 PM, Boudewijn Rempt wrote:
> Hey...
>
> We're supposed to be testing phabricator. So I would propose that we
> actually start using phabricator instead of reviewboard.
>
>
Hey...
We're supposed to be testing phabricator. So I would propose that we
actually start using phabricator instead of reviewboard.
Please take a look at https://phabricator.kde.org!
Boudewijn
___
calligra-devel mailing list
calligra-devel@kd
Your KDE identity account works: login with the ldap login block.
On Sat, 18 Apr 2015, Yue Liu wrote:
how to get an account?
2015-04-17 23:59 GMT-07:00 Boudewijn Rempt :
Hi!
We've got a running instance of Phabricator now: phabricator.kde.org.
It's still a test setup,
how to get an account?
2015-04-17 23:59 GMT-07:00 Boudewijn Rempt :
> Hi!
>
> We've got a running instance of Phabricator now: phabricator.kde.org.
> It's still a test setup, but we're one of the projects doing the testing
> :-). The possibilities look great,
Hi!
We've got a running instance of Phabricator now: phabricator.kde.org. It's
still a test setup, but we're one of the projects doing the testing :-).
The possibilities look great, I'm really glad we can test it already.
So, now's the time to start using Phabricat
58 matches
Mail list logo
