[ITK] [ITK-dev] Patches for the ITK 4.13 Release Candidate 1

[Dženan Zukić]

When doing a normal release cycle, master gets tagged. Once a version is
released (e.g. 4.12), development in master branch continues normally. When
a patch release is wanted (e.g. 4.12.1), then the patches are cherry-picked
from master and merged into the release branch individually.

And we are about to start release cycle for 4.13, meaning feature freeze
(no ENH: commits) until the final 4.13 is released.

Regards,
Dženan

On Mon, Dec 4, 2017 at 12:26 PM, Niels Dekker <niels-xtk at xs4all.nl> wrote:

> Thanks, Francois and Dženan,
>
> If you are just going to tag the master, I don't need to worry about my
> patches being forgotten  :-) I thought that all patches would have to be
> merged from "master" to "release" branch, before getting released. Or has
> the procedure been simplified?
>
> Kind regards, Niels
>
>
> On 2017-12-04 16:25, Francois Budin wrote:
>
>> Thanks Niels for the feedback. When we tag the RC1, please let us know
>> if we missed any of these patch.
>>
>> On Mon, Dec 4, 2017 at 10:20 AM, Dženan Zukić <dzenanz at gmail.com>
>> wrote:
>>
>> Hi Niels,
>>>
>>> the RC1 tag will be added to the current master, which means all the
>>> patches which have been merged to master will be included.
>>>
>>> Regards,
>>> Dženan
>>>
>>> On Mon, Dec 4, 2017 at 5:08 AM, Niels Dekker <niels-xtk at xs4all.nl>
>>> wrote:
>>> Francois Budin wrote on December 1st 2017:
>>> We are planning to tag ITK 4.13 Release Candidate 1 on Monday,
>>> December 4th. If there is any enhancement that you would like to see
>>> included in ITK 4.13.0, please submit your patch as soon as possible
>>> as they need to be reviewed and merged prior. If you have patches
>>> that
>>> have been in the review process for a while and not yet accepted,
>>> mention that you would like these to be integrated in the upcoming
>>> release. As a reminder, this means feature freeze for ‘master’
>>> and, therefore, enhancements should not be merged until after the
>>> release candidate period. The final release is planned for December
>>> 18th.
>>>
>>> Thank you for the information! Can you please make sure all the
>>> Hough Transform patches that I submitted in the last two months will
>>> be included with the release?
>>> ...
>>> I think there is still some more room for improvement, but I hope
>>> that getting these patches into the release will trigger more
>>> feedback from ITK users on how to further improve the ITK Hough
>>> Transform.
>>>
>>> Kind regards, Niels
>>>
>>
> --
> Niels Dekker
> Scientific programmer
> LKEB, Leiden University Medical Center, Netherlands
> The ITK community is transitioning from this mailing list to
> discourse.itk.org. Please join us there!
> ______________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Kitware offers ITK Training Courses, for more information visit:
> http://kitware.com/products/protraining.php
>
> Please keep messages on-topic and check the ITK FAQ at:
> http://www.itk.org/Wiki/ITK_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/insight-developers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/community/attachments/20171204/edc6f2bf/attachment.html>
-------------- next part --------------
The ITK community is transitioning from this mailing list to discourse.itk.org. Please join us there!
______________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html

Kitware offers ITK Training Courses, for more information visit:
http://kitware.com/products/protraining.php

Please keep messages on-topic and check the ITK FAQ at:
http://www.itk.org/Wiki/ITK_FAQ

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/insight-developers