[...] > > I have a personal policy of "never send stuff to the server if it > doesn't build and pass all tests". It's something of a habit from where > I work, but I find it is quite good.
I can understand where this come from but as much at work everything has to build and pass (unit tests etc.) in the /trunk as much on an open source project I think it's ok to have the /trunk in an unstable state if you back it up with stable branches and tags either way, it's always interesting for the user to see what's going on all the time eg. "ah ha! they refactor this way..." cheers, zwetan -- You received this message because you are subscribed to the Google Groups "Project Hosting on Google Code" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=en.
