gerrit will be upgraded to 2.6.1
On 08/04/2013 02:45 PM, Itamar Heim wrote:
a small service interruption is expected
upgrade is done. please report any issues. changes worth noting: - 42x improvement on git clone and git fetch - Completely customizable workflow Individual projects can add (or remove) score categories through labels and Prolog rules. http://gerrit-documentation.googlecode.com/svn/ReleaseNotes/ReleaseNotes-2.6...
Hi, There is new permission "View Drafts"[1]. If we add "Registered Users" this permission, we can get rid of the WIP patches and submit these are drafts. Drafs has major advantage, apart the fact that it cannot be mistakenly consider as final... it can be actually deleted... the entire draft or specific changesets within. So it does not bloat the database. Regards, Alon [1] http://gerrit-documentation.googlecode.com/svn/Documentation/2.6/access-cont... ----- Original Message -----
From: "Itamar Heim" <iheim@redhat.com> To: "infra" <infra@ovirt.org>, "arch" <arch@ovirt.org> Sent: Sunday, August 4, 2013 2:50:35 PM Subject: Re: gerrit will be upgraded to 2.6.1
On 08/04/2013 02:45 PM, Itamar Heim wrote:
a small service interruption is expected
upgrade is done. please report any issues.
changes worth noting: - 42x improvement on git clone and git fetch - Completely customizable workflow Individual projects can add (or remove) score categories through labels and Prolog rules.
http://gerrit-documentation.googlecode.com/svn/ReleaseNotes/ReleaseNotes-2.6... _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
Also, it might help jenkins differ from real patches pending to be merged (thus require a verification) from a draft WIP that doesn't need verification. Types of events from gerrit jenkins listens too: (currently set to patchset created) Draft Published: Sent when a change moves from draft state to new. (only available in version 2.5 or higher of Gerrit). Patchset Created: Sent when a new patchset arrives on a change. Before version 2.6.0, this was the only event you could trigger on. Change Merged: Sent when a change is merged on the Gerrit server. Comment Added: Sent when a comment is added to a change. Which category and value to trigger on can be configured. Ref Updated: Sent when a ref is updated on the Gerrit server, i.e. someone pushes past code review. ----- Original Message -----
From: "Alon Bar-Lev" <alonbl@redhat.com> To: "Itamar Heim" <iheim@redhat.com> Cc: "arch" <arch@ovirt.org>, "infra" <infra@ovirt.org> Sent: Sunday, August 4, 2013 5:03:13 PM Subject: Re: gerrit will be upgraded to 2.6.1
Hi,
There is new permission "View Drafts"[1].
If we add "Registered Users" this permission, we can get rid of the WIP patches and submit these are drafts.
Drafs has major advantage, apart the fact that it cannot be mistakenly consider as final... it can be actually deleted... the entire draft or specific changesets within. So it does not bloat the database.
Regards, Alon
[1] http://gerrit-documentation.googlecode.com/svn/Documentation/2.6/access-cont...
----- Original Message -----
From: "Itamar Heim" <iheim@redhat.com> To: "infra" <infra@ovirt.org>, "arch" <arch@ovirt.org> Sent: Sunday, August 4, 2013 2:50:35 PM Subject: Re: gerrit will be upgraded to 2.6.1
On 08/04/2013 02:45 PM, Itamar Heim wrote:
a small service interruption is expected
upgrade is done. please report any issues.
changes worth noting: - 42x improvement on git clone and git fetch - Completely customizable workflow Individual projects can add (or remove) score categories through labels and Prolog rules.
http://gerrit-documentation.googlecode.com/svn/ReleaseNotes/ReleaseNotes-2.6... _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
_______________________________________________ Arch mailing list Arch@ovirt.org http://lists.ovirt.org/mailman/listinfo/arch
On 08/04/2013 05:03 PM, Alon Bar-Lev wrote:
Hi,
There is new permission "View Drafts"[1].
If we add "Registered Users" this permission, we can get rid of the WIP patches and submit these are drafts.
Drafs has major advantage, apart the fact that it cannot be mistakenly consider as final... it can be actually deleted... the entire draft or specific changesets within. So it does not bloat the database.
any reason to limit this to registered users (we allow everyone to see all patches currently without logging in)?
----- Original Message -----
From: "Itamar Heim" <iheim@redhat.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: "infra" <infra@ovirt.org>, "arch" <arch@ovirt.org> Sent: Sunday, August 4, 2013 5:14:16 PM Subject: Re: gerrit will be upgraded to 2.6.1
On 08/04/2013 05:03 PM, Alon Bar-Lev wrote:
Hi,
There is new permission "View Drafts"[1].
If we add "Registered Users" this permission, we can get rid of the WIP patches and submit these are drafts.
Drafs has major advantage, apart the fact that it cannot be mistakenly consider as final... it can be actually deleted... the entire draft or specific changesets within. So it does not bloat the database.
any reason to limit this to registered users (we allow everyone to see all patches currently without logging in)?
No... I thought we require users to login anyway...
On 08/04/2013 05:17 PM, Alon Bar-Lev wrote:
----- Original Message -----
From: "Itamar Heim" <iheim@redhat.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: "infra" <infra@ovirt.org>, "arch" <arch@ovirt.org> Sent: Sunday, August 4, 2013 5:14:16 PM Subject: Re: gerrit will be upgraded to 2.6.1
On 08/04/2013 05:03 PM, Alon Bar-Lev wrote:
Hi,
There is new permission "View Drafts"[1].
If we add "Registered Users" this permission, we can get rid of the WIP patches and submit these are drafts.
Drafs has major advantage, apart the fact that it cannot be mistakenly consider as final... it can be actually deleted... the entire draft or specific changesets within. So it does not bloat the database.
any reason to limit this to registered users (we allow everyone to see all patches currently without logging in)?
No... I thought we require users to login anyway...
done
On 08/04/2013 02:50 PM, Itamar Heim wrote:
On 08/04/2013 02:45 PM, Itamar Heim wrote:
a small service interruption is expected
upgrade is done. please report any issues.
changes worth noting: - 42x improvement on git clone and git fetch - Completely customizable workflow Individual projects can add (or remove) score categories through labels and Prolog rules.
http://gerrit-documentation.googlecode.com/svn/ReleaseNotes/ReleaseNotes-2.6...
there are some reports on bad performance with the chrome browser. please report if so. no such reports so far for firefox
On Sun, Aug 04, 2013 at 02:50:35PM +0300, Itamar Heim wrote:
On 08/04/2013 02:45 PM, Itamar Heim wrote:
a small service interruption is expected
upgrade is done. please report any issues.
changes worth noting: - 42x improvement on git clone and git fetch - Completely customizable workflow Individual projects can add (or remove) score categories through labels and Prolog rules.
The down size of this is that currently old searches, with the likes of CodeReview>=1 have to be updated to label:Code-Review>=1 (notice the annoying dash in the middle) I suppose we can configure the server side for backward compatibility, but I do not think that we should bother.
http://gerrit-documentation.googlecode.com/svn/ReleaseNotes/ReleaseNotes-2.6... _______________________________________________ Arch mailing list Arch@ovirt.org http://lists.ovirt.org/mailman/listinfo/arch
----- Original Message -----
From: "Dan Kenigsberg" <danken@redhat.com> To: "Itamar Heim" <iheim@redhat.com> Cc: "arch" <arch@ovirt.org>, "infra" <infra@ovirt.org> Sent: Sunday, August 4, 2013 6:26:36 PM Subject: Re: gerrit will be upgraded to 2.6.1
On Sun, Aug 04, 2013 at 02:50:35PM +0300, Itamar Heim wrote:
On 08/04/2013 02:45 PM, Itamar Heim wrote:
a small service interruption is expected
upgrade is done. please report any issues.
Maybe I missed this before, Maybe old habit - but, can we do something about the color scheme? or was that intentional?
changes worth noting: - 42x improvement on git clone and git fetch - Completely customizable workflow Individual projects can add (or remove) score categories through labels and Prolog rules.
The down size of this is that currently old searches, with the likes of CodeReview>=1
have to be updated to label:Code-Review>=1
(notice the annoying dash in the middle)
I suppose we can configure the server side for backward compatibility, but I do not think that we should bother.
http://gerrit-documentation.googlecode.com/svn/ReleaseNotes/ReleaseNotes-2.6... _______________________________________________ Arch mailing list Arch@ovirt.org http://lists.ovirt.org/mailman/listinfo/arch
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
On 08/05/2013 08:01 AM, Yair Zaslavsky wrote:
----- Original Message -----
From: "Dan Kenigsberg" <danken@redhat.com> To: "Itamar Heim" <iheim@redhat.com> Cc: "arch" <arch@ovirt.org>, "infra" <infra@ovirt.org> Sent: Sunday, August 4, 2013 6:26:36 PM Subject: Re: gerrit will be upgraded to 2.6.1
On Sun, Aug 04, 2013 at 02:50:35PM +0300, Itamar Heim wrote:
On 08/04/2013 02:45 PM, Itamar Heim wrote:
a small service interruption is expected
upgrade is done. please report any issues.
Maybe I missed this before, Maybe old habit - but, can we do something about the color scheme? or was that intentional?
I try to not do any unneeded changes from upstream to avoid overhead on upgrades, etc. so this is "how it looks" out of the box (for each version/change so far). if it will get worse, we can consider re-themeing, etc.
On Mon, Aug 05, 2013 at 04:11:43PM +0300, Itamar Heim wrote:
On 08/05/2013 08:01 AM, Yair Zaslavsky wrote:
----- Original Message -----
From: "Dan Kenigsberg" <danken@redhat.com> To: "Itamar Heim" <iheim@redhat.com> Cc: "arch" <arch@ovirt.org>, "infra" <infra@ovirt.org> Sent: Sunday, August 4, 2013 6:26:36 PM Subject: Re: gerrit will be upgraded to 2.6.1
On Sun, Aug 04, 2013 at 02:50:35PM +0300, Itamar Heim wrote:
On 08/04/2013 02:45 PM, Itamar Heim wrote:
a small service interruption is expected
upgrade is done. please report any issues.
Maybe I missed this before, Maybe old habit - but, can we do something about the color scheme? or was that intentional?
I try to not do any unneeded changes from upstream to avoid overhead on upgrades, etc. so this is "how it looks" out of the box (for each version/change so far). if it will get worse, we can consider re-themeing, etc.
Personally I think the new design is an improvement over the old so +1 for keeping the defaults.
participants (6)
-
Alon Bar-Lev -
Dan Kenigsberg -
Ewoud Kohl van Wijngaarden -
Eyal Edri -
Itamar Heim -
Yair Zaslavsky