Grzegorz Kossakowski wrote:
Carsten Ziegeler pisze:
Agreed. I would add one (quite obvious) rule: if some module gets
relesed and artifact is available at central other modules should
always update its dependencies ASAP. This applies to patch releases.
No, I don't think so :)
Example (it's fictional): we have the ajax block released as 1.0 and
the forms block 1.1 depends on the ajax api 1.0.
Now, for some reason we update the ajax api to 1.1 and add some features.
There is no need to change the dependency from the forms block to the
new ajax api. As the ajax api 1.1 is assumed to be compatible to 1.0
(and it really should be), you can run the forms block with both
api's. And it is better to indicate the lowest version you require.
On APIs I agree but I if API changes then it's not a patch release, right?
Ah, ok, sorry I overread this. You're right with patch releases of course.
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
