Hi all,
I hope this is a complete no-event, but we'd like to give you a heads-up, in
case something unexpected comes up. We Gerrit admins are currently working
towards moving us to Gerrit 3.0.2.
The plan is to upgrade on Monday next week, the 30th of September.
There are no huge improvements in
On 25.6.2019 17.07, James McDonnell wrote:
> Is HTTPS access still supposed to work?
>
> git push gerrit HEAD:refs/for/5.12
> fatal: https://jmcdonn...@codereview.qt-project.org/p/qt/qtbase/info/refs not
> valid: is this a git repository?
>
> Did the paths change?
Yes, it's still supposed to w
On 2019-05-06, 8:16 AM, "Development on behalf of Frederik Gladhorn"
wrote:
Hello,
We've been working on the Gerrit Upgrade for a while now and we are finally
getting ready to deploy the new goodness.
We have all patches in our fork (yes, sadly we continue diverging a
Il 06/05/19 14:16, Frederik Gladhorn ha scritto:
We will collect some documentation here, currently it's just a placeholder
page, not yet worth visiting, unless you know the newer Gerrit and want to
help out documenting what is new:
https://wiki.qt.io/Gerrit_Upgrade_2019
Wow, this is a very wel
On Tuesday, 7 May 2019 02:11:55 PDT Jukka Jokiniva wrote:
> If someone want to see the new UI in action, the Gerrit code is reviewed in
> Gerrit: https://gerrit-review.googlesource.com/ Just a note that the site
> is using the very latest 3.0 RC, and we will be using 2.16.7, but the UI is
> pretty
The new Gerrit version will use Polymer-based UI, the "old style UI" will be
disabled.
If someone want to see the new UI in action, the Gerrit code is reviewed in
Gerrit: https://gerrit-review.googlesource.com/
Just a note that the site is using the very latest 3.0 RC, and we will be using
2.16
I hope you have at least two backups in two different locations. : )
> On 7. May 2019, at 11:02, Jukka Jokiniva wrote:
>
>
> On 06/05/2019, 22.46, "Development on behalf of Sergio Ahumada"
> wrote:
>>
>> On 06.05.19 14:16, Frederik Gladhorn wrote:
>>> We aim to do the Upgrade to Gerrit 2.
On 06/05/2019, 22.46, "Development on behalf of Sergio Ahumada"
wrote:
>
>On 06.05.19 14:16, Frederik Gladhorn wrote:
>> We aim to do the Upgrade to Gerrit 2.16.7 around the 20th of May (yes,
> that's
>> a Monday, we assume Gerrit will be down for the full day that day).
>
>Did
Are we planning to use Polymer-based UI, as currently used by Chromium and
Android,
or the "old" one (which is probably still a default)? I believe "old" one has a
horrible UX,
while Polymer one is a bit nicer. Also, Polymer's patch viewer plays nicely
with X selection
buffer, while "old" does n
On 06.05.19 14:16, Frederik Gladhorn wrote:
> Hello,
>
> We've been working on the Gerrit Upgrade for a while now and we are finally
> getting ready to deploy the new goodness.
>
> We have all patches in our fork (yes, sadly we continue diverging a bit from
> mainstream, adding our own state ha
Hello,
We've been working on the Gerrit Upgrade for a while now and we are finally
getting ready to deploy the new goodness.
We have all patches in our fork (yes, sadly we continue diverging a bit from
mainstream, adding our own state handling for the CI).
The good news is that there are very f
On 14-5-2014 9:45, Haataja Ismo wrote:
>> -Original Message-
>> From: Verbruggen Erik
>> Looks nice! Would it be possible to update the logo and the image saying
>> "Qt Open Governance / Code Review" with a HiDPI version? They look
>> really fuzzy on my screen, especially next to the text t
> -Original Message-
> From: Verbruggen Erik
> Looks nice! Would it be possible to update the logo and the image saying
> "Qt Open Governance / Code Review" with a HiDPI version? They look
> really fuzzy on my screen, especially next to the text that's showing
> crisp and clear.
I changed
Looks nice! Would it be possible to update the logo and the image saying
"Qt Open Governance / Code Review" with a HiDPI version? They look
really fuzzy on my screen, especially next to the text that's showing
crisp and clear.
-- Erik.
On 12-5-2014 16:08, Haataja Ismo wrote:
>> And to see/try
> -Original Message-
> The Unified field is open two extra windows. Not very convenient.
Sorry, the standard Gerrit way was in use instead of our one page review. Fixed
now.
___
Development mailing list
Development@qt-project.org
http://lists.q
Hi
The Unified field is open two extra windows. Not very convenient.
It would be nice to have the conflict feature of 2.9 too. ;-)
Otherwise the new gerrit it really nice.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.
When will the new Gerrit version be deployed to production?
--
Jake Petroules - jake.petroules at petroules.com
Chief Technology Officer - Petroules Corporation
On 2014-05-12, at 10:08 AM, Haataja Ismo wrote:
>> And to see/try all the changes in action, everything is deployed to
>> https://dev-
> And to see/try all the changes in action, everything is deployed to
> https://dev-codereview.qt-project.org for testing.
Sorry, my bad, just got informed this is not publicly available.
___
Development mailing list
Development@qt-project.org
http://lis
On Mon, May 12, 2014 at 01:57:16PM +, Haataja Ismo wrote:
> And to see/try all the changes in action, everything is deployed to
> https://dev-codereview.qt-project.org for testing.
>
that testing request applies only to digia employees due to the host
being firewalled.
___
Hi,
For upcoming Gerrit (Code Review) upgrade all the changes are pushed for review:
https://codereview.qt-project.org/#q,status:open+project:qtqa/gerrit+branch:v2.7.0-based,n,z
We'd like to call everybody to participate for reviewing. So, if interested,
you are very welcome to share your persona
20 matches
Mail list logo
