[Paraview-developers] [Paraview] ParaView GateKeeper Review Summary

Moreland, Kenneth kmorel at sandia.gov
Wed Nov 28 11:02:37 EST 2012


Is there a formal feedback mechanism to let developers know their topic has been kicked out of next and the reason for it?  For example, a note in the bug tracker that pushes the status back to todo or an email to the developer if the reason is because there is no open issue for the change?

-Ken

From: Sebastien Jourdain <sebastien.jourdain at kitware.com<mailto:sebastien.jourdain at kitware.com>>
Date: Wednesday, November 28, 2012 8:01 AM
To: "paraview at paraview.org<mailto:paraview at paraview.org>" <paraview at paraview.org<mailto:paraview at paraview.org>>, "paraview-developers at paraview.org<mailto:paraview-developers at paraview.org>" <paraview-developers at paraview.org<mailto:paraview-developers at paraview.org>>
Subject: [EXTERNAL] [Paraview] ParaView GateKeeper Review Summary

Caution, from now on, topics that were in next before the gatekeeper
review and that haven't been merged to master will be automatically
removed from next so next will basically be equivalent to master.

The reason is to give any contributor the opportunity to rebase their work on top of master in order to get a cleaner history or even remove their branch.
Therefore, from now on, branch that are on stage should be manually
pushed by their owner to next after gatekeeper review. The following command can be run to do so:

# To push without rebasing your work (don't need to be in git repo)
# -------
$ ssh git at paraview.org<mailto:git at paraview.org> stage ParaView merge YOUR_STAGE_BRANCH_NAME


# To rebase your work on top of master
# -------
$ git fetch origin
$ git checkout -b YOUR_STAGE_BRANCH_NAME stage/YOUR_STAGE_BRANCH_NAME
$ git rebase origin/master
$ git push stage :YOUR_STAGE_BRANCH_NAME
$ git stage-push
$ git stage-merge


Topics remaining on stage: (NOT in NEXT)
---------------------------------------------
  12742_scalar_bar_improvements
  13024-debug-leaks-view
  13047_java_wrapping_for_paraviewcore_and_eclipse_swt_rendering
  13374-slac-multiple-modes
  streaming-temporal-AMR
  13598-VRGrabWorldFix
  AddTransformsToRepresentations
  topic_commandproperty_314
  amr_streaming_pass2
  update_manta_test
  array-calculator-field-data-support
  use_more_precise_value_to_describe_interactive_render_timeout
  co-processing-fortran-utilities
  vr_improvements
  fix-use-directory-name-hint


Topics merged into master:
---------------------------------------------
        0013683_fix_vtkForceTime
(VTK)   13225_make_vtkPVDataInformation_more_robust
        13229_fix_connect_button_enabled_status
        13439_fix_interactive_render_delay
        13494-multi-apply
        13671_spreadsheet_cell_connectivity
        13673_cleanup_pointsprite_plugin
        13674_fix_static_qt_plugins
(VTK)   13681-matplotlib-python-interp
        13684_enh_csv_reader
        cgns-patch
        fix-coprocessing-tests
        fix-gmv-test
        integrate_gmv_reader_contribution
        minor_fix
        update_nightly_testing_to_RC3

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20121128/f47bbc15/attachment.htm>


More information about the Paraview-developers mailing list