Re: [openstack-dev] Gerrit downtime and upgrade on 2014-04-28

2014-04-28 Thread Chmouel Boudjnah
On Fri, Apr 25, 2014 at 6:10 PM, Zaro zaro0...@gmail.com wrote:

 Gerrit 2.8 allows setting label values on patch sets either thru the
 command line[1] or REST API[2].  Since we will setup WIP as a -1 score
 on a label this will just be a matter of updating git-review to set
 the label on new patchsets.  I'm no sure if there's a bug entered in
 our the issue tracker for this but you are welcome to create one.


This probably would need more than just an update since currently
git-review is using (AFAICT) the SSH api  or perhaps a mix.

Chmouel
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] Gerrit downtime and upgrade on 2014-04-28

2014-04-28 Thread Chmouel Boudjnah
On Wed, Apr 23, 2014 at 12:40 AM, James E. Blair jebl...@openstack.orgwrote:

 There are a few changes that will impact developers.  We will have more
 detailed documentation about this soon, but here are the main things you
 should know about:


What plugins are going to be enabled under gerrit?

I am asking that because I know that there is a pycharm/intelij plugin
allowing to do gerrit reviews and it need the 'download-commands' gerrit
plugin (http://is.gd/X9vIJ0) to work properly.

Would love to be able to use that and to look over how to make an emacs
mode out of it.

Chmouel
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] Gerrit downtime and upgrade on 2014-04-28

2014-04-26 Thread Yuriy Taraday
On Fri, Apr 25, 2014 at 11:41 PM, Zaro zaro0...@gmail.com wrote:

 Do you mean making it default to WIP on every patchset that gets
 uploaded?


No. I mean carrying WIP to all new patch sets once it is set just like
Code-Review -2 is handled by default.

Gerrit 2.8 does allow you to carry the same label score forward[1] if
 it's either a trivial rebase or no code has changed.  We plan to set
 these options for the 'Code-Review' label, but not the Workflow label.

 [1]
 https://gerrit-review.googlesource.com/Documentation/config-labels.html


It looks like copyMinScore option for Workflow label will do what I'm
talking about.

-- 

Kind regards, Yuriy.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] Gerrit downtime and upgrade on 2014-04-28

2014-04-25 Thread Yuriy Taraday
Hello.

On Wed, Apr 23, 2014 at 2:40 AM, James E. Blair jebl...@openstack.orgwrote:

 * The new Workflow label will have a -1 Work In Progress value which
   will replace the Work In Progress button and review state.  Core
   reviewers and change owners will have permission to set that value
   (which will be removed when a new patchset is uploaded).


Wouldn't it be better to make this label more persistent?
As I remember there were some ML threads about keeping WIP mark across
patch sets. There were even talks about changing git-review to support this.
How about we make it better with the new version of Gerrit?

-- 

Kind regards, Yuriy.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] Gerrit downtime and upgrade on 2014-04-28

2014-04-25 Thread Roman Podoliaka
Hi all,

 Wouldn't it be better to make this label more persistent?

+1. It's really annoying to press Work in Progress button every time
you upload a new patch set.

Thanks,
Roman

On Fri, Apr 25, 2014 at 11:02 AM, Yuriy Taraday yorik@gmail.com wrote:
 Hello.

 On Wed, Apr 23, 2014 at 2:40 AM, James E. Blair jebl...@openstack.org
 wrote:

 * The new Workflow label will have a -1 Work In Progress value which
   will replace the Work In Progress button and review state.  Core
   reviewers and change owners will have permission to set that value
   (which will be removed when a new patchset is uploaded).


 Wouldn't it be better to make this label more persistent?
 As I remember there were some ML threads about keeping WIP mark across patch
 sets. There were even talks about changing git-review to support this.
 How about we make it better with the new version of Gerrit?

 --

 Kind regards, Yuriy.

 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] Gerrit downtime and upgrade on 2014-04-28

2014-04-25 Thread Ricardo Carrillo Cruz
It would be nice to have a switch on git-review to push patchsets on WIP,
the same way you can do with Draft.

Anyone knows if there is an enhancement request/bug opened against Gerrit
so we could implement it?

Regards


2014-04-25 10:49 GMT+02:00 Roman Podoliaka rpodoly...@mirantis.com:

 Hi all,

  Wouldn't it be better to make this label more persistent?

 +1. It's really annoying to press Work in Progress button every time
 you upload a new patch set.

 Thanks,
 Roman

 On Fri, Apr 25, 2014 at 11:02 AM, Yuriy Taraday yorik@gmail.com
 wrote:
  Hello.
 
  On Wed, Apr 23, 2014 at 2:40 AM, James E. Blair jebl...@openstack.org
  wrote:
 
  * The new Workflow label will have a -1 Work In Progress value which
will replace the Work In Progress button and review state.  Core
reviewers and change owners will have permission to set that value
(which will be removed when a new patchset is uploaded).
 
 
  Wouldn't it be better to make this label more persistent?
  As I remember there were some ML threads about keeping WIP mark across
 patch
  sets. There were even talks about changing git-review to support this.
  How about we make it better with the new version of Gerrit?
 
  --
 
  Kind regards, Yuriy.
 
  ___
  OpenStack-dev mailing list
  OpenStack-dev@lists.openstack.org
  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 

 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] Gerrit downtime and upgrade on 2014-04-28

2014-04-25 Thread Yuriy Taraday
On Fri, Apr 25, 2014 at 8:10 PM, Zaro zaro0...@gmail.com wrote:

 Gerrit 2.8 allows setting label values on patch sets either thru the
 command line[1] or REST API[2].  Since we will setup WIP as a -1 score
 on a label this will just be a matter of updating git-review to set
 the label on new patchsets.  I'm no sure if there's a bug entered in
 our the issue tracker for this but you are welcome to create one.

 [1] https://review-dev.openstack.org/Documentation/cmd-review.html
 [2]
 https://review-dev.openstack.org/Documentation/rest-api-changes.html#set-review


Why do you object making it a default behavior on the Gerrit side?
Is there any issue with making this label pass on to new patch sets?

-- 

Kind regards, Yuriy.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] Gerrit downtime and upgrade on 2014-04-28

2014-04-25 Thread Zaro
Do you mean making it default to WIP on every patchset that gets
uploaded?  That isn't possible with Gerrit version 2.8 because it
doesn't allow you to set a default score.  Also I don't think that
would be appropriate because I definitely would not want that as the
default setting for my workflow.  I think it would be more appropriate
to build that into git-review, maybe a configuration setting that
would set every patchset to WIP upon upload.

Gerrit 2.8 does allow you to carry the same label score forward[1] if
it's either a trivial rebase or no code has changed.  We plan to set
these options for the 'Code-Review' label, but not the Workflow label.

[1] https://gerrit-review.googlesource.com/Documentation/config-labels.html

On Fri, Apr 25, 2014 at 11:58 AM, Yuriy Taraday yorik@gmail.com wrote:
 On Fri, Apr 25, 2014 at 8:10 PM, Zaro zaro0...@gmail.com wrote:

 Gerrit 2.8 allows setting label values on patch sets either thru the
 command line[1] or REST API[2].  Since we will setup WIP as a -1 score
 on a label this will just be a matter of updating git-review to set
 the label on new patchsets.  I'm no sure if there's a bug entered in
 our the issue tracker for this but you are welcome to create one.

 [1] https://review-dev.openstack.org/Documentation/cmd-review.html
 [2]
 https://review-dev.openstack.org/Documentation/rest-api-changes.html#set-review


 Why do you object making it a default behavior on the Gerrit side?
 Is there any issue with making this label pass on to new patch sets?

 --

 Kind regards, Yuriy.

 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] Gerrit downtime and upgrade on 2014-04-28

2014-04-22 Thread James E. Blair
Zaro zaro0...@gmail.com writes:

 Hello All.  The OpenStack infra team has been working to put
 everything in place so that we can upgrade review.o.o from Gerrit
 version 2.4.4 to version 2.8.4  We are happy to announce that we are
 finally ready to make it happen!

 We will begin the upgrade on Monday, April 28th at 1600 UTC (the
 OpenStack recommended 'off' week).

 We would like to advise that you can expect a couple hours of downtime
 followed by several more hours of automated systems not quite working
 as expected.  Hopefully you shouldn't notice anyway because you should
 all be on vacation :)

Hi,

This is a reminder that next week, Gerrit will be unavailable for a few
hours starting at 1600 UTC on April 28th.

There are a few changes that will impact developers.  We will have more
detailed documentation about this soon, but here are the main things you
should know about:

* The Important Changes view is going away.  Instead, Gerrit 2.8
  supports complex custom dashboards.  We will have an equivalent of the
  Important Changes screen implemented as a custom dashboard.

* The Approval review label will be renamed to Workflow.  The +1
  value will still be Approved and will be available to core
  developers -- nothing about the approval process is changing.

* The new Workflow label will have a -1 Work In Progress value which
  will replace the Work In Progress button and review state.  Core
  reviewers and change owners will have permission to set that value
  (which will be removed when a new patchset is uploaded).

* We will also take this opportunity to change Gerrit's SSH host key.
  We will supply instructions for updating your known_hosts file.  As a
  reminder, you can always verify the fingerprints on this page:
  https://review.openstack.org/#/settings/ssh-keys

-Jim

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev