On 08/06/2012 12:33, Jonas Smedegaard wrote: > On 12-06-08 at 11:52am, Jérémy Lal wrote: >> Hi, >> it's now clearer  to me how upstream v8 release their library : >> 1 - They start a new branch, say 3.10 >> 2 - the first minor versions can break API (3.10.2, 3.10.4, 3.10.6) >> 3 - at some point they only make patch-level versions, keeping API, >> and very probably ABI compatibility too. (3.10.8.x) >> The only proof i have of that is the analysis done in . >> >> I suggest libv8 debian package reflects this by: >> * start packaging a new branch only when upstream is at stage 3 >> * having a soname libv8.so.3.10.8 instead of libv8.so.126.96.36.199 >> >> That will have the nice effect of being able to update patch-level >> versions without having to recompile reverse dependencies each time. >> >> The risk is letting an ABI incompatibility slip in. It would however >> be caught quite early by the reverse dependencies anyway, so it seems >> okay unless it happens often... >> >> Any advise on this please ? > > Are you talking about releases to unstable, or also to experimental? > Seems to me that it might make sense to release to experimental right > away, and then _change_ to target unstable when judged stable.