On 17/04/2013 18:07, git(a)lrde.epita.fr wrote:
This is an automated email from the git
hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Olena, a generic and efficient image processing platform".
Even if I'm in favor of rapid integration of small changes/corrections
into `next', I recommend we always use another branch to push new
changes over it and ensure they pass the build on TeamCity *before*
advancing `next'. This way we'll maintain the project in a reasonable
state for people checking out `next'.
Another reason to do so is to preserve the ability to apply a small fix
by rewriting a commit (instead of introducing the fix as a new commit)
in the working branch (we don't want to alter `next', as it is tagged as
a ``public branch'').
The bottom line is that `next' should always build.
(I'd also like each change be reviewed before it gets merged into
`next', but past experience shows that it delays the integration way too
much. We probably need better tools to review patches.)