[vtk-developers] ANN: VTK moving to topic reviews in Gerrit on Wednesday

[Marcus D. Hanwell]

On Wed, Feb 1, 2012 at 8:43 AM, Brad King <brad.king at kitware.com> wrote:
> On 1/31/2012 9:38 AM, Marcus D. Hanwell wrote:
>>
>> This does mean that there will be some time tomorrow where it is not
>> possible to merge changes into VTK while we make the switch and verify
>> that things are working as expected. I will announce on the developer
>> list when merges will be disabled, along with when they should be back
>> up and running.
>
> We will begin the process at 9am EST.  It should be completed by noon
> unless there are unforeseen problems.

The modifications have been completed.  We have updated the main VTK
Git instructions:

http://www.vtk.org/Wiki/VTK/Git

for the new workflow. Gerrit is now the main entry point for changes
to go in master. The topic stage is dead, long live Gerrit!

We will be bringing the automated build testing for topics online this
afternoon for VTK, and hope to have this working by the end of the day
for new VTK submissions. This will be for members of the VTK-core
group. Any existing changes in Gerrit review can be marked as +2 for
code review and then submitted to have it merged. Alternatively, if
you need to modify/extend the topic pushing will create a new topic
for review.

To find members of the VTK-core group, able to give +2 on code review
and submit changes please see the group here:

http://review.source.kitware.com/#/admin/groups/11,members

Any topics prepared for the topic stage can be sent to Gerrit. We will
push an updated SetupForDevelopment.sh script to mark the old aliases
as deprecated, git gerrit-push will act in much the same way as git
stage-push did. If you haven't run the script in a while, running it
again will give you the opportunity to setup the Gerrit alias
correctly and update local hooks etc.

Please get in touch if you encounter any issues.

Thanks,

Marcus