[Insight-developers] Reminder: 4.3.0 Release Schedule

[Matt McCormick]

Hi Brad,

Yes, the point that release will be merged into master is well taken.
We can discuss more at the TCon's, but let us plan on using the
release branch in the anticipated manner.

Thanks,
Matt

On Mon, Nov 19, 2012 at 2:11 PM, Bradley Lowekamp
<blowekamp at mail.nih.gov> wrote:
> Matt,
>
> Regarding the bringing patches into release instead of a lock for the final week. I still think that will work just fine. If all patches that are intended to be merged into the release are first merged into master for nightly testing on the dashboard. You will still get total coverage. Also remember that master will contain a superset of of the commits in release. In the final week before the release I would not expect any major changes, perhaps some compilation issues, warings or bugs reported by the user. The fixes for specific issues like this should easily be able to be verified from the nightly testing on the master branch before merging into the release branch.
>
> Anyways, what every is going to be easiest and least disruptive to development will likely be best. We still have a couple more regular TCONs to continue this discussion.
>
> Brad
>
>
>
> On Nov 16, 2012, at 1:37 PM, Matt McCormick <matt.mccormick at kitware.com> wrote:
>
>> Hi all,
>>
>> A reminder that the 4.3.0 release cycle process is imminent.  The
>> first RC tagging is scheduled for November 26th.  This means that all
>> new features should be merged by the end of next week.
>>
>> There will be two more release candidates December 3rd and December
>> 10th.  During this time, only fixes to the dashboard, bug fixes, and
>> critical features where there is major consensus on necessity should
>> be merged.  Commits violating this policy will be subject to a revert.
>> Between the third and final RC on December 10th, the repository will
>> be locked, and only dashboard fixes will be allowed.  At the TCon this
>> morning, we discussed bringing patches into the "release" branch
>> instead of a lock, but in hindsight that will not work will because
>> most of the dashboard builds are against "master".
>>
>> Thanks to everyone for all their great work.  We have seen increased
>> activity recently and more community involvement.  There has been good
>> community work towards WrapITK support, and we will have VS2008
>> support for the release, which is a major accomplishment.  After
>> discussion on the TCon this morning, the hard efforts of Hans Johnson,
>> Kent Williams, and Brad King in the DCMTK patch were merged.   It is
>> currently ON by default as we fix any remaining dashboard issues, and
>> we will have to assess default settings as it gets vetted in the RC
>> process.
>>
>> Thanks,
>> Matt
>> _______________________________________________
>> 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://www.itk.org/mailman/listinfo/insight-developers
>