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

[Dave Partyka]

I am not sure if this is a reported bug (I can report it now if it isn't
reported already).

Using ExternalProject with a git repo and specifying a sha1 revision via
GIT_TAG will blow away the entire source directory whenever the revision is
changed. This leads to complete rebuilds of said project.

On Thu, Nov 4, 2010 at 3:34 PM, David Cole <david.cole at kitware.com> 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!)
>
> _______________________________________________
> cmake-developers mailing list
> cmake-developers at cmake.org
> http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20101104/9e3e09be/attachment.htm>