<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.5969" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=867155708-06072010>Hi,</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=867155708-06072010></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=867155708-06072010>I
think the PROJECT_GROUP patch could be really nice for many of
us:</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=867155708-06072010></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><A
href="http://public.kitware.com/Bug/view.php?id=3796">http://public.kitware.com/Bug/view.php?id=3796</A></FONT></DIV>
<DIV> </DIV>
<DIV><SPAN class=867155708-06072010><FONT face=Arial color=#0000ff size=2>Best
regards,</FONT></SPAN></DIV>
<DIV><SPAN class=867155708-06072010><FONT face=Arial color=#0000ff
size=2>Fabrice Aeschbacher</FONT></SPAN></DIV>
<DIV><BR></DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=de dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>Von:</B> cmake-bounces@cmake.org
[mailto:cmake-bounces@cmake.org] <B>Im Auftrag von </B>David
Cole<BR><B>Gesendet:</B> Montag, 5. Juli 2010 20:31<BR><B>An:</B> cmake;
cmake-developers@cmake.org<BR><B>Betreff:</B> [CMake] Bug fix requests for the
*next* release of CMake...<BR></FONT><BR></DIV>
<DIV></DIV>Hi all,
<DIV><BR></DIV>
<DIV>Now that we have released CMake 2.8.2 last Monday, and we have switched
to this new workflow using branches in the git repository, *now* would be a
great time to prioritize bug fixes for the next release of CMake.</DIV>
<DIV><BR></DIV>
<DIV>We are leaning towards quarterly releases from now on, scheduling them
every 3 months. That would make the next release of CMake version 2.8.3 and
scheduled to have an "rc1" release candidate in approximately mid-September,
2010.</DIV>
<DIV><BR></DIV>
<DIV>If you have a particular issue that you think should be fixed for
inclusion in 2.8.3, please bring it up now. Ideally, each issue will be
discussed as needed on the mailing list to come to any consensus about what
should be done to fix it, and then an entry in the bug tracker may be used to
keep it on the radar screen, and to track activity related to it.</DIV>
<DIV><BR></DIV>
<DIV>Patches are always welcome. Patches that include testing of any new
features, or tests that prove a bug is really fixed on the dashboards,
basically any patch with testing is preferred over a patch with no testing.
Also, if you are *adding* code, then you also probably need to add *tests* of
that code, so that the coverage percentage stays as is or rises.</DIV>
<DIV><BR></DIV>
<DIV>Please discuss issues here as needed, and add notes to existing issues in
the bug tracker that you are interested in seeing fixed for 2.8.3 -- we will
be looking at the mailing list and activity in the bug tracker to help
prioritize the bug fixes that will occur in the next several weeks.</DIV>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV>Thanks,</DIV>
<DIV>David Cole</DIV>
<DIV>Kitware, Inc.</DIV>
<DIV><BR></DIV></BLOCKQUOTE></BODY></HTML>