-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Tom Collins wrote:
> The 1.3 branch didn't get off to a good start, and I continued to
> maintain (somewhat) the 1.2 branch. I think that would be the proper
> place to start, perhaps creating a 1.5 dev branch that could become a
> 1.6 release at some point.
The trunk is in a very odd place, and I'm trying to decide how to handle it.
I'm thinking I'll just tag it as a rejected branch and bring the 1.2.13 sources
in just so I have a stable base from which to work with.
As far as a new release, I'm thinking 1.2.13 could be the production stable
and the new development tree for the 5.5 branch of vpopmail could be the new
trunk, where I'd make all the new crazy changes to qmailadmin.
If there are no objections to laying out the source tree this way, I'll move
ahead with that.
> Note that I had started on an attempt at putting all HTML in a html.h
> file, so that a template could have .html files and a matching html.h.
> Ultimately though, we need a new template system that keeps all markup
> in the .html files. I had some ideas on that that we could discuss if
> you're interested.
It's true the template technology utilized by qmailadmin is very old.
I have done a great deal of work on template API for a variety of
projects. I would be very happy to hear your ideas. Please keep the
discussion on-list though.
- --
/*
Matt Brookings <m...@inter7.com> GnuPG Key FAE0672C
Software developer Systems technician
Inter7 Internet Technologies, Inc. (815)776-9465
*/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkqFjFAACgkQIwet2/rgZyz5/gCfXEad/HsAgBQ0JQhtnkpuPoL+
uwEAn0jl5e/thFRf7E5HiIH4hMwQZBJm
=veHV
-----END PGP SIGNATURE-----
