[Paraview] ANN: Upcoming changes to ParaView Server Manager

Wed Apr 6 16:08:20 EDT 2011

Hey Pat,

In the CMB Project we have been dealing with a release branch (based on ParaView prior to the changes made to Representations) and a master branch (which tracks the current ParaView), and to this day we have been able to keep both in sync (In terms of being able to checkout off of release and do a merge onto master when the changes are identical to both).  I expect that when this happens I will have another branch called maintenance (which represents the current release branch), as well as a release branch (representing the current master), and master that tracks ParaView after this big change.

Bob

Robert M. O'Bara, MEng.
Technical Leader

Kitware Inc.
28 Corporate Drive
Suite 101
Clifton Park, NY 12065

Phone: (518) 881- 4931

On Apr 6, 2011, at 2:54 PM, pat marion wrote:

> Hi Seb,
> 
> Could you give some advice as to how we start topic branches after the collaboration merge?  Paraview has branches "master" and "release", which in my mind map to "bleeding edge" and "stable, release ready" branches.  It seems the best practice is to start topics from release and merge them into master.  After the collaboration merge, it might not be a good idea to start topics from release anymore, is that correct?
> 
> Any plans to move to a next, master, release branch scheme?
> 
> Pat
> 
> On Wed, Apr 6, 2011 at 3:43 PM, Sebastien Jourdain <sebastien.jourdain at kitware.com> wrote:
> Hi Folks,
> 
> The time has gone and we plan to merge the Collaboration branch to
> master this Friday (April 8th 2011).
> So if anyone has something to say, please do it before Friday or it
> will be too late. ;-)
> 
> Seb
> 
> PS: We will also update the Version number to be 3.11.1.
> 
> On Mon, Mar 28, 2011 at 3:29 PM, Sebastien Jourdain
> <sebastien.jourdain at kitware.com> wrote:
> > Folks,
> >
> > For those of you who haven't follow the topic in the
> > paraview-developers mailing list here is a quick summary on what's
> > going on in the coming weeks.
> > We've been working for a while now on restructuring the Server Manager
> > of ParaView to make it more efficient as well as allowing it to
> > support collaborative workflows.
> > The API has undergone major changes and may cause some minor rewrite
> > of your own code. Before we merge these changes to master, please try
> > out the Collaboration branch with your code and let us know if you
> > experience any issue.
> > Please see below for the details on how to checkout the Collaboration branch.
> >
> > Thanks for your support,
> >
> > Seb
> >
> > ============= From the ParaView-developer list ===============
> >
> > Following up the mail from Utkarsh on the changes to ParaView Server Manager :
> >
> > http://public.kitware.com/pipermail/paraview-developers/2011-February/000951.html
> >
> > We finally push our branch to the stage. That branch will only be
> > merged to master in the coming month.
> > But if you have developed a plugin or any code based on ParaView and
> > you want to test it against
> > that major update, please follow the coming instructions and don't
> > hesitate to send us your feed back.
> >
> > In order to fetch our ParaView branch from stage, you will need to
> > execute the following command line:
> >
> > $ git clone --recursive git://paraview.org/stage/ParaView.git -b Collaboration
> >
> > Then, as any regular ParaView source directory, you should be able to
> > configure and build it.
> > As some directory and kit renaming occurred, you may need to update
> > the name of the ParaView library that you are linking against. Now the
> > ParaViewCore package which used to be called "Servers" contains the
> > following kits:
> > vtkPVCommon, vtkPVClientServerCore, vtkPVServerImplementation,
> > vtkPVServerManager, vtkPVVTKExtensions.
> >
> > Please remember, these do not affect 3.10 or even 3.10.1. These will
> > make into the
> > official ParaView 4.0 release, nothing sooner.
> >
> > Seb
> >
> > PS: Additional informations on those changes are available here
> > http://paraview.org/ParaView3/images/2/24/ParaViewCollaborationChanges.pdf
> >
> _______________________________________________
> Powered by www.kitware.com
> 
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
> 
> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView
> 
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview
> 
> _______________________________________________
> Powered by www.kitware.com
> 
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
> 
> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView
> 
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20110406/21336d45/attachment-0001.htm>