[Ctk-developers] Permanent branch / tag policy

[Steve Pieper]

Hi Marco -

Either option sounds fair to me.  Probably a tag for the exact version that
corresponds to the MITK release is a good idea even if you also keep a
branch.

-Steve

On Wed, Jun 24, 2015 at 8:15 AM, Nolden, Marco <M.Nolden at dkfz-heidelberg.de>
wrote:

> Hi CTK'ers,
>
> for our recent MITK 2015.05 release we used a specific CTK hash which
> includes some branches that were at that time not yet ready for merging
> into master. The integration branch we used is currently living outside
> of the github commontk organization, but to keep things together and
> make them easier accessible for external users I would like to add it to
> commontk and also create some permanent reference to it. I thinking
> about two options:
>
> 1. create a tag, like ctk-for-mitk-2015.05
> 2. create an integration branch on commontk, and after everything has
> been included through the outstanding pull requests, merge that branch
> with the "ours" merge policy just to keep the reference
>
> What do you think, any other ideas?
>
> Marco
>
> _______________________________________________
> Ctk-developers mailing list
> Ctk-developers at public.kitware.com
> http://public.kitware.com/mailman/listinfo/ctk-developers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/ctk-developers/attachments/20150626/78e472d2/attachment.htm>