-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sun, 8 Oct 2006, Daniel Fagerstrom wrote:
Joerg Heinicke skrev:
Both approaches are probably not backwards compatible. For 2.2 this is not
that problem, but as long as we share blocks with 2.1 it is. I wonder how
long we will go this way. IMO we should decouple both before releasing 2.2
to clean up trunk as much as possible.
Agree as well. If there is interest we should try to get out a new (last?)
2.1.x release. And after that 2.1.x and trunk should stop sharing code so
that we can clean up trunk if we feel like it. It would, as an example, be a
good idea to start de-avalonizing some of the more important blocks.
I'd support your release plan as well the de-avalonizing of
important blocks.
- --
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFKWTTLNdJvZjjVZARAqgoAKCvJod/m9zTHWxajTTSV4GYxdmdQACgkYVI
1PtJoxEUI0ECo69ZOQDZoDM=
=z6NF
-----END PGP SIGNATURE-----
