[cmake-developers] Freeze and review?

David Cole david.cole at kitware.com
Mon Sep 5 16:14:06 EDT 2011


Merging to next triggers testing on the CMake dashboard clients.

If the maintainer may object to something that shouldn't be in there,
then please contact him first.

You may always merge to 'next' -- but we ask that you use your best
judgment. If something has no chance of being accepted into the
upcoming CMake 2.8.6 release, then it may be wiser to defer even
putting it on the stage until after we finalize the release.

Think about it this way: if it's not on the stage, and not in 'next',
then it cannot possibly be accidentally merged into 'master' and
included in the next rc or the final release. If it is on the stage,
and it is in 'next' then Brad and I may merge it in even though you
didn't intend it, unless we are communicating well enough to avoid
misunderstandings.

On the other hand, Brad and I tend to get stricter about what we merge
to 'master' as we approach the final release, so you can trust us to
act conservatively in that respect.

It's nice (for us) to have the dashboards and 'next' represent to a
very close degree, the content of what is in the upcoming release, so
that the dashboard testing gives us an accurate picture of the state
of the project.

Let me know if you still have a question I have not answered, or it
any of this seems confusing.


Thanks,
David


On Mon, Sep 5, 2011 at 4:02 PM, Stephen Kelly <steveire at gmail.com> wrote:
>
> Hi,
>
> I was wondering if stage/next is ever to be considered frozen around RC
> time, or is it always 'summer' in next?
>
> I have pushed a patch adding features from the KDE version of
> Qt4Macros.cmake to a branch in stage (qt_dbus_interface_args). As I don't
> maintain that file, should I contact the maintainer before I put it in next,
> or should I put it in next first?
>
> Thanks,
>
> Steve.
>
> _______________________________________________
> cmake-developers mailing list
> cmake-developers at cmake.org
> http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
>



More information about the cmake-developers mailing list