On 7/21/07, Larry Garfield <larry@garfieldtech.com> wrote:
On Saturday 21 July 2007, Vasileios Lourdas wrote:
On Saturday 21 July 2007 20:08:57 Caleb Gilbert wrote:
You said the current 5.x-dev breaks with contributed modules. But you don't see a reason not to release it?!
It's been quite common that contributed modules have required some
updating along with the Drupal core upgrades (even the incremental ones). If there is a new policy which says that a Drupal core upgrade should never result in any contributed modules being broken, that seems like a new precedent.
It depends on the meaning of the word "upgrade". Upgrade should probably stand for 5.x -> 6, whereas update 5.x -> 5.y, where x < y. In the latter case, yes, no modules should ever be broken. That's the meaning of the API freeze in the first place.
As I understand it, the policy for intra-version upgrades (5.x->5.y, etc.) has been "don't break anything unless you really really really have to for security" (e.g., swapping out an XML-RPC library mid-version.) I think that's a good policy to maintain.
Yes, that is the policy. API fixes, such as http://drupal.org/node/135926, are sometimes okay as well, after a bit of scrutiny.
I don't know enough about the supposed 5.x-dev breaks to say if they count, but I am running 5.x-dev on a site that just launched because I needed some of its bugfixes, and so far nothing has blown up. It's even survived an upgrade to jQuery 1.1.3.1. :-)
I am running any sites which I can, including a live clients' site or two, on 5.x. -- Neil Drumm http://delocalizedham.com