On Thu, Jan 9, 2014 at 4:21 PM, David Cole <dlrd...@aol.com> wrote: > If all the tests pass for you locally, and you are pretty sure they will > all pass on other machines too, then you can do it whenever you think it's > ready
Thanks, I merged it as described here: http://www.cmake.org/Wiki/CMake/Git/Develop#Merge_a_Topic_for_Testing > . (Unless somebody else has given you feedback that you need to address > first...) > > The primary thing is to monitor the Continuous dashboards for the hour or > two after you do so, and then the check on the Nightly dashboards the next > day. > > Can you give a link to monitor? If any build or test failures occur on dashboard builds, you should get > emails from the CDash server, but it doesn't hurt to check the dashboard > yourself and get in the habit of checking there frequently. > > And then: just be ready to update the topic with any fixes necessary for > other platforms in a timely fashion. > > NP > If you don't have time to monitor the dashboards for the day or two after > you merge a topic, then you should wait until you do have time. Or have a > coding buddy that can help you make tweaks to the topic to get it right on > all platforms. > > > > Hope this helps, > David C. > > > Thanks! -- Eran Ifrah Author of codelite, a cross platform open source C/C++ IDE: http://www.codelite.org wxCrafter, a wxWidgets RAD: http://wxcrafter.codelite.org
-- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
