I have an idea for a feature that might help resolve some of the
"Find***" issues. I would like to see CMake implement some sort of
"Software Update" mechanism where you could tell CMake to check a
central server for any updated FindXXX.cmake files and then download
them into the cmake installation directory. This would alleviate some
issues (cough ** FindBoost.cmake *** cough) where a critical fix gets
implemented but a user has to either compile from HEAD or wait for the
*next* release, which might be 3 months away. I would venture to guess
that most of the tweaks to the FindXXX.cmake files are CMake Major
version independent. This would be a nice way to push out small
updates that don't actually require a full recompile or newer version
of CMake to be installed.
Just my thoughts for this friday morning.
___________________________________________________________
Mike Jackson www.bluequartz.net
Principal Software Engineer mike.jack...@bluequartz.net
BlueQuartz Software Dayton, Ohio
On Nov 4, 2010, at 3:34 PM, David Cole wrote:
Hi all,
Now that we have released CMake 2.8.3, *now* would be a great time
to prioritize bug fixes for the next release of CMake.
Replies requested. Read on. Just a short reply with bug numbers or
links to the bugs is all we need here. Please move specific
discussions into the bugs themselves or start a new thread to talk
about it... Replies on this thread should just be a collector for
bug numbers.
We are aiming for quarterly releases from now on, scheduling them
every 3 or 4 months. That would make the next release of CMake
version 2.8.4 and scheduled to have an "rc1" release candidate in
approximately mid-January, 2011, target date: Wed. 1/12/2011.
If you have a particular issue that you think should be fixed for
inclusion in 2.8.4, 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.4 -- 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.
P.S. - as a nice summary of what we've accomplished in the CMake
2.8.3 release, see here: http://public.kitware.com/Bug/changelog_page.php
-- it lists 89 issues that we resolved: nice job, everybody!
(About 45 of those were specifically addressed because somebody
brought it up in response to my similar email from just after
2.8.2... Don't be shy!)
_______________________________________________
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
