Re: Maintenance Policy?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


> For what it's worth I find it hard to believe anyone's really
> surprised by this. Nearly all other open source projects stop
> supporting old branches as soon as there's a newer branch is released.

I'm not surprised at all. Our product holds data - and that's an
extremely valuable resource to end users (e.g. companies). Nobody wants
to risk problems and/or suffer long downtimes. Our complete lack of an
in-place upgrade is what is really making us do the extra effort to support
old versions. Thankfully, it looks like we've finally started down the
road to a serious attempt at an upgrade process.

For what it's worth, I think our release history and current necessarily
ad-hoc and somewhat arbitrary release process makes it difficult to make
anything but the vaguest statement on dates, and I'd rather we didn't.

- --
Greg Sabino Mullane greg@turnstep.com
End Point Corporation
PGP Key: 0x14964AC8 200907122044
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAkpahQkACgkQvJuQZxSWSsjehACg7208VOSWEoJuHWMORnhAg82t
IugAn0vSGBI9qUvAUDb3msMeyRzjjuy7
=tcmE
-----END PGP SIGNATURE-----