On Wed, Apr 07, 2004 at 09:17:12AM -0600, Jim Ramsay wrote:
That said, there will be a huge overlap of code between the two, and when I add a new feature to one, I don't want it to be a huge chore to add the same feature again to the other. Also, some files will (and should) always be exactly the same in both branches. Some files will be very different.
Just out of curiosity, why wouldn't you lock the feature set of 1.0.x and contribute only bug fixes/security fixes to that branch, and develop new features under the 1.1.x branch?
That's not a /bad/ idea. Does anyone out there think that TMDA-cgi, as-is now is "good enough" (except bug fixes!) to be feature frozen? It can:
- Install TMDA for the first time for users who have not set it up themselves.
- View the pending list and release and/or whitelist emails there
- Generate and test tagged addresses
- View and change the contents of lists
- View and change the contents of filters
- View and change settings for TMDA, and the interface itself
I suppose these are the basics of what TMDA-cgi set out to do... all feature requests pending right now are enhancements to these ideas which make them easier to do, or extra goodies which may be useful to a handful of "power users".
Thanks, Mark - I used to think (~10 minutes ago) that TMDA-cgi wasn't ready for a feature freeze, but on second thought, it does what I would consider a "full range" of functionality for letting people interact with TMDA through a web interface.
Questions/comments/flames?
-- Jim Ramsay "Me fail English? That's unpossible!"
_________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
