[CMake] Bug fix requests for the *next* release of CMake...

[Marcel Loose]

Here's my list of issues that I would like to see fixed.

0010771 FindMPI does not set all required compile flags - Modules -
2010-05-28 03:50 
0010335 FIND_XXX problem with symlinks when using ENV - CMake -
2010-02-26 08:42 
0010202 CMAKE_CONFIGURATION_TYPES and CMAKE_BUILD_TYPE weird behaviour -
CMake - 2010-01-29 05:55 
0010201 FindSubversion: new Subversion_WC_UPDATE macro - Modules -
2010-01-29 05:25 
0010200 FindSubversion: Subversion_WC_INFO macro should not do
SEND_ERROR - Modules - 2010-01-29 03:51 
0010199 FindSubversion: mismatch between code and documentation -
Modules - 2010-01-29 03:45 
0010198 FindSubversion does not always handle REQUIRED option correctly
- Modules - 2010-01-29 03:40 
0008466 Provide finer control than pass/fail for a test program - CTest
- 2009-09-15 03:57 

Best regards,
Marcel Loose.

On Mon, 2010-07-05 at 14:31 -0400, David Cole wrote:
> Hi all,
> 
> 
> 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.
> 
> 
> 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.
> 
> 
> 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.
> 
> 
> 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.
> 
> 
> 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.
> 
> 
> 
> 
> Thanks,
> David Cole
> Kitware, Inc.
> 
> 
> _______________________________________________
> Powered by www.kitware.com
> 
> Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
> 
> Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
> 
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake