1:50 p.m.
I'm planning to upgrade gerrit to version 2.3 on Sunday.
will send an email before and after the downtime.
plan is to upgrade to "clean" version of 2.3, and after we see
everything is working ok, upgrade it with the patch for better emails.
thoughts/comments?
Thanks,
Itamar
1:56 p.m.
On 05/30/2012 08:50 PM, Itamar Heim wrote:
I'm planning to upgrade gerrit to version 2.3 on Sunday.
will send an email before and after the downtime.
plan is to upgrade to "clean" version of 2.3, and after we see
everything is working ok, upgrade it with the patch for better emails.
thoughts/comments?
one comment that 2.4 was released last friday (and has a cool feature of
rebasing[1].
but i prefer to give it a bit of time for testing, and not delay our
upgrade.
so I prefer to upgrade to 2.3.
question is if to apply the email patch on 2.3, or upgrade to 2.4 first.
in any case I want to first upgrade to a clean 2.3 environment.
Itamar
[1]"issue 1035 Add rebase button to the change screen
This change adds a rebase button along with the rest of the action
buttons in the change page. When pressing the button, the most recent
patch set will be rebased onto the tip of the destination branch or the
latest patchset of the change we depend upon. A new patch set containing
the rebased commit will be produced and added to the change.
Rebasing of a change in web UI is restricted to change owner, submitter
or those with the (new) rebase permission."
4:10 p.m.
adding the steps we did downstream just in case:
0. backup configuration files under gerrit home dir (review_site/etc/gerrit.config and
secure.config)
backup postgres db
1. /home/gerrit2/review_site/bin/gerrit.sh stop
2. su - gerrit2
3. wget http://gerrit.googlecode.com/files/gerrit-2.3.war
4. unlink gerrit.war; ln -s gerrit-2.3.war gerrit.war
5. java -jar gerrit.war init -d review_site/
- this will now show you interactive questions about gerrit configuration,
you should just keep current configuration (press enter).
and compare the new conf after to make sure nothing was changed.
6. /home/gerrit2/review_site/bin/gerrit.sh start
docs: http://gerrit-documentation.googlecode.com/svn/Documentation/2.3/index.html
here are the 2.3 release notes:
http://gerrit-documentation.googlecode.com/svn/ReleaseNotes/ReleaseNotes-...
----- Original Message -----
From: "Itamar Heim" <iheim(a)redhat.com>
To: "infra" <infra(a)ovirt.org>
Sent: Wednesday, May 30, 2012 8:56:14 PM
Subject: Re: updating gerrit to 2.3
On 05/30/2012 08:50 PM, Itamar Heim wrote:
> I'm planning to upgrade gerrit to version 2.3 on Sunday.
> will send an email before and after the downtime.
>
> plan is to upgrade to "clean" version of 2.3, and after we see
> everything is working ok, upgrade it with the patch for better
> emails.
>
> thoughts/comments?
>
one comment that 2.4 was released last friday (and has a cool feature
of
rebasing[1].
but i prefer to give it a bit of time for testing, and not delay our
upgrade.
so I prefer to upgrade to 2.3.
question is if to apply the email patch on 2.3, or upgrade to 2.4
first.
in any case I want to first upgrade to a clean 2.3 environment.
Itamar
[1]"issue 1035 Add rebase button to the change screen
This change adds a rebase button along with the rest of the action
buttons in the change page. When pressing the button, the most recent
patch set will be rebased onto the tip of the destination branch or
the
latest patchset of the change we depend upon. A new patch set
containing
the rebased commit will be produced and added to the change.
Rebasing of a change in web UI is restricted to change owner,
submitter
or those with the (new) rebase permission."
_______________________________________________
Infra mailing list
Infra(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
8:20 a.m.
On 30/05/12 20:56, Itamar Heim wrote:
On 05/30/2012 08:50 PM, Itamar Heim wrote:
> I'm planning to upgrade gerrit to version 2.3 on Sunday.
> will send an email before and after the downtime.
>
> plan is to upgrade to "clean" version of 2.3, and after we see
> everything is working ok, upgrade it with the patch for better emails.
>
> thoughts/comments?
>
one comment that 2.4 was released last friday (and has a cool feature of rebasing[1].
but i prefer to give it a bit of time for testing, and not delay our upgrade.
so I prefer to upgrade to 2.3.
question is if to apply the email patch on 2.3, or upgrade to 2.4 first.
+1 on upgrading to 2.4 first. It does have some needed improvements,
and emails can stay as we currently see them. So no degradation from mail point of view,
it will only get better.
in any case I want to first upgrade to a clean 2.3 environment.
Itamar
[1]"issue 1035 Add rebase button to the change screen
This change adds a rebase button along with the rest of the action buttons in the change
page. When pressing the button, the most recent patch set will be rebased onto the tip of
the destination branch or the latest patchset of the change we depend upon. A new patch
set containing the rebased commit will be produced and added to the change.
Rebasing of a change in web UI is restricted to change owner, submitter or those with the
(new) rebase permission."
_______________________________________________
Infra mailing list
Infra(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
--
/d
Why doesn't DOS ever say "EXCELLENT command or filename!"
4:48 a.m.
On 06/01/2012 03:20 PM, Doron Fediuck wrote:
On 30/05/12 20:56, Itamar Heim wrote:
> On 05/30/2012 08:50 PM, Itamar Heim wrote:
>> I'm planning to upgrade gerrit to version 2.3 on Sunday.
>> will send an email before and after the downtime.
>>
>> plan is to upgrade to "clean" version of 2.3, and after we see
>> everything is working ok, upgrade it with the patch for better emails.
>>
>> thoughts/comments?
>>
>
> one comment that 2.4 was released last friday (and has a cool feature of
rebasing[1].
>
> but i prefer to give it a bit of time for testing, and not delay our upgrade.
>
> so I prefer to upgrade to 2.3.
> question is if to apply the email patch on 2.3, or upgrade to 2.4 first.
>
+1 on upgrading to 2.4 first. It does have some needed improvements,
and emails can stay as we currently see them. So no degradation from mail point of view,
it will only get better.
to upgrade to 2.4 i'd expect at least a week of it being tested by
someone maintaing a different gerrit.
and still sounds safer to upgrade to 2.3, then to 2.4 (even if a week
later).
so unless there is a good reason not to, I still plan to upgrade to 2.3
this week.
we can discuss upgrade to 2.4 for next week.
> in any case I want to first upgrade to a clean 2.3 environment.
>
> Itamar
>
>
>
>
> [1]"issue 1035 Add rebase button to the change screen
>
> This change adds a rebase button along with the rest of the action buttons in the
change page. When pressing the button, the most recent patch set will be rebased onto the
tip of the destination branch or the latest patchset of the change we depend upon. A new
patch set containing the rebased commit will be produced and added to the change.
>
> Rebasing of a change in web UI is restricted to change owner, submitter or those with
the (new) rebase permission."
>
> _______________________________________________
> Infra mailing list
> Infra(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
4586
days inactive
4590
days old
4 comments
3 participants
participants (3)
-
Doron Fediuck -
Eyal Edri -
Itamar Heim