Eduardo, can you explain this a bit more for me:
> For core packages, bug fixes should be committed on the
> current release branch whenever applicable.
The problem with this one is that some developers have to
develop with old code in the stable branch because HEAD
contains bugs. I see many people on the lists that have
these problems.
I think most developers should be developing against 5.1, not HEAD. The rules about bug fixes vs new features only apply to core, not to the other packages. (I know all this could be clearer - it's taken me about two years to understand even as much as I do now, which is still only a subset of the problem space and a smaller subset of the solution space - and I'm going to work on some docs this week.) The only time you should be working on HEAD is if you are doing development directly on core packages. This approach should get you all of the benefits - you can still do whatever you want to your packages. If you are working on the standard packages (file-storage, forums, etc), you can still do minor or even major releases, and you know your releases will be available for most other users much sooner than if they depended on HEAD core.
