David Crossley wrote:
Nicola Ken Barozzi wrote:
Imagine that all cutting-edge users can use the trunk in production. A
patch is just a couple of actions away. And after incorporation, the
check is instantaneous, and on a *real* test, as it actually get used.
I like your general drift. We should also have our own continuous
integration testing by having our own services at forrest.zones.apache.org
+10000
(I cannot devote time to this until after ApacheCon - or at the Hackathon?)
This can only work if the trunk is always *usable*, and not only
_buildable_. This can make our trunk be really bug-free, as there would
really be a lot of eyes looking at the code.
I would thus propose that the trunk be always *releaseable* at all
times, and that all new functionality that interferes with usage of
prior features be developed on separate branches.
I hope that you are still talking about the Branch-When-Needed system.
http://svn.collab.net/repos/svn/trunk/doc/user/svn-best-practices.html
That is the closest to what we have been doing until now.
However, we are not diligent enough at the test-before-commit phase.
Forrestbot on the server would assist, but not replace that need.
+100000
we must all do:
cd FORREST_HOME/main/build test
*before* any major commit and forrest.zones must do frequent builds to
ensure nobody forgot.
We have also not been branching enough, although we have been
much better lately.
I'm reviewing the best practices document Tim and David have linked to
in order to learn when and why we should branch. Perhaps everyone else
who hasn't read it should do the same.
http://svn.collab.net/repos/svn/trunk/doc/user/svn-best-practices.html
Good stuff. We must document the outcome of this thread.
There is a deliberate hole at our project guidelines because we
did not yet put this effort into deciding a good management.
http://forrest.apache.org/guidelines.html#code
Yes, please someone document this (menaing I'm afraid I don't have the
time).
Ross
