[prev in list] [next in list] [prev in thread] [next in thread] 

List:       svk-devel
Subject:    [svk-devel] Data::Hierarchy 0.40, and backwards compatibility
From:       mb.7766 () gmail ! com (Michael Brouwer)
Date:       2006-11-07 12:15:36
Message-ID: 5d51890a0611070915gc8870fmebc49b12dcbf4a50 () mail ! gmail ! com
[Download RAW message or body]

We already break backwards compatibility for reading ~/.svk/config when
going from 1.0x to trunk due to the upgrade from YAML < 0.60 to YAML-Syck in
trunk.  So changing DH to an incompatible format in trunk doesn't really
change anything as far as backwards compatibility with 1.0x is concerned.
It's gone anyway.  Of course it would be nice if 1.0x would know how to use
DH-0.40 as well so that you coud still use 1.0x and trunk at the same time
if you upgraded both YAML to 0.60 or later and DH to 0.40 or later for 1.0x.

Michael


On 11/4/06, Chia-Liang Kao <clkao@clkao.org> wrote:
>
> On 04/11/06, David Glasser <glasser@mit.edu> wrote:
> > However, if you do choose to upgrade to DH 0.40, older versions of SVK
> > may break; at the very least, some of the checkout subcommands like
> > "svk co -l" and "svk co --relocate" did not work on trunk with DH 0.40
> > until r2110; I have no idea how SVK 1.0x behaves with DH 0.40.
>
> We should make sure newer d::h doesn't break old svk.  Possibly by
> releasing new D::H under different name.
>
> Cheers,
> CLK
> _______________________________________________
> svk-devel mailing list
> svk-devel@bestpractical.com
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/svk-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.bestpractical.com/pipermail/svk-devel/attachments/20061107/d69bea26/attachment.htm

[prev in list] [next in list] [prev in thread] [next in thread]