[Paraview-developers] how to tag VTK, PV and PVSB changes destined for 5.5.0.RC2?

[Cory Quammen]

On Wed, Feb 28, 2018 at 11:36 AM, Ben Boeckel <ben.boeckel at kitware.com>
wrote:

> On Wed, Feb 28, 2018 at 11:19:23 -0500, David E DeMarle wrote:
> > How should we be flagging our changes to ensure that they get into the
> next
> > release?
>
> Mark them as being backported to the relevant branch in the description
> of the MR (at the end; they work just like the `Do:` commands):
>
> VTK:
>
>     Backport: paraview/release
>

Also make sure you base your VTK changes off VTK commit 9f073177 or
earlier. The robot will check to make sure you have done this.


>
> ParaView and the superbuild:
>
>     Backport: release
>

Please also base your ParaView changes off of the release branch. Again,
the robot will check.

Cory


>
> --Ben
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Search the list archives at: http://markmail.org/search/?q=
> Paraview-developers
>
> Follow this link to subscribe/unsubscribe:
> https://public.kitware.com/mailman/listinfo/paraview-developers
>



-- 
Cory Quammen
Staff R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://public.kitware.com/pipermail/paraview-developers/attachments/20180228/6d4ef4f2/attachment.html>