Also, I believe Brad already put these in next, but I figure I should mention 
them anyway:

        FindMPI sometimes fails because it checks for non-existing libraries    
        http://www.cmake.org/Bug/view.php?id=9093

        Related fix for other flags, not just -l:
        http://cmake.org/gitweb?p=cmake.git;a=log;h=d84cbd0f

-Todd


On Jul 5, 2010, at 1:00 PM, Todd Gamblin wrote:

> I'd like to see this one:
> 
>       CMake needs a BlueGene/P Platform File
>       http://*www.*itk.org/Bug/print_bug_page.php?bug_id=10897
> 
> As well as the bootstrap patch that Brad King made for properly finding 
> compiler pairs on, e.g., the Power6 frontends of our BG/P systems.  I'm not 
> sure if there is a specific issue in Mantis for that one.
> 
> Todd Gamblin
> Center for Applied Scientific Computing
> Lawrence Livermore National Laboratory
> 
> 
> 
> On Jul 5, 2010, at 11:31 AM, 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
> 
> _______________________________________________
> 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
> 

_______________________________________________
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

Reply via email to