[Opengeoscience-developers] branch approval process

[Ben Burnett]

I'm in the middle of working on a new style for the workflow UI (Adding
input directly to the modules), so it's not quite ready for review. After I
get this done (which might not be this week because a lot of UVCDAT GUI
bugs have cropped up that have priority), then you can review and I can try
to break down the remaining tasks for the workflow (front end and back end)
and start those subtasks each on their own feature branch.

-Ben


On Thu, Jun 27, 2013 at 10:03 AM, Aashish Chaudhary <
aashish.chaudhary at kitware.com> wrote:

> I just wanted to clear that the moment you merge  your branch into next,
> you are automatically
> asking for approval on that branch.
>
> If you don't anyone to approve that branch, drop an email.
>
> Said that @Ben do I need to look into your branch of workflow for
> approval?
>
> - Aashish
>
>
> --
> | Aashish Chaudhary
> | R&D Engineer
> | Kitware Inc.
> | www.kitware.com
>
> _______________________________________________
> Opengeoscience-developers mailing list
> Opengeoscience-developers at public.kitware.com
>
> http://public.kitware.com/cgi-bin/mailman/listinfo/opengeoscience-developers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/opengeoscience-developers/attachments/20130627/86c2f77a/attachment.html>