-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I'm about to merge my SQLAlchemy branch to the trunk. I'm happy
enough with where this is going to commit to this approach going
forward. I wrote about it a bit in a news article on wiki.list.org
and I'll try to elaborate there when things settle down.
This stuff could definitely use more testing, but the web u/i and
sending mail through the system work for me. If you're using the
trunk regularly now, you will notice that there's no migration path
yet for moving from the pickle-based storage to SQLAlchemy based
storage. This is what the import/export scripts are for. You notice
though that only bin/export is written yet. bin/import is tops on my
list after the merge.
I've also committed bin/export.py to the Mailman 2.1 branch. This
will be how you migrate MM2.1 lists to the MM trunk. Our next
release of MM2.1 will have this, so my plan for migration will be to
install the latest 2.1.x (x > 9), run bin/export.py, then feed the
resulting XML to the trunk's bin/import. For now, you can start from
scratch with bin/newlist or creating a list through the web. From
there the trunk should look and act just like you're used to.
As always, let us know what you find. I'm eager to fix problems
quickly. Please don't use the SF bug tracker for problems you
encounter on the trunk. It would also be interesting to know if you
try a SQLAlchemy backend other than SQLite.
- -Barry
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRZWUFHEjvBPtnXfVAQIEJwP/WkB2jY3Ww2YR96oDejC/ZSSWwbct8ENb k/kpcoYm9V2ra36WUiHt0pfFLyhMk0pRXtBh/oScooLiZJu9AA2wnD046I5AJZLt 5DS+YJI2B5c4pn4pO80w5JeAUgQfiYIhafs6u/Oy3fDzag6Rp698Dt/Bv62V8Mly hteE9Iu8xcs= =plDI -----END PGP SIGNATURE-----