[qmailadmin-devel] Show stoppers to making a stable release

[Tom C. <to...@to...>]

Forgetting the fact that the current versions rely on development  
releases of vpopmail, I think we should discuss all outstanding issues  
that prevent us from calling QmailAdmin stable.

Ken has dropped the ball on the vpopmail 5.3.21 release, and it may  
soon end up on SourceForge as well.

https://sourceforge.net/tracker/ 
?func=detail&atid=200001&aid=761548&group_id=1

I'd like to see two more things get into QmailAdmin before it's  
declared stable:

1) A tool to go through all .qmail-user files in all domains and  
convert aliases to forwards (i.e., Maildir delivery to &us...@do...  
format).
2) (minor) A compile option to hide the MySQL options on add/modify  
mailing list.

Number 2 is not difficult at all, and can be accomplished with a new  
##t tag and a configure option.  I plan on adding it in the next few  
days.

Does anyone want to tackle number 1?  Do you think a Perl script is  
appropriate, or would it have to be a compiled C program?  I can  
probably whip up some Perl in a few hours to get the job done, but C  
could take 2-3 times as long.

Is there anything else that should go on this list?  Counting of  
forwards was broken in 1.0.24, but I already have a fix in 1.0.25.

Should we set up CVS on SourceForge?  If someone can give me simple  
directions, I'd be willing to push my current in-progress work up to  
CVS on a regular basis, and could accept patches posted to the  
repository as well.

I think that all of the other feature requests can wait for the next  
development cycle, which I plan on opening up as soon as QA is stable.   
I'm even willing to declare 1.0.25 (or maybe 1.0.26) stable and open up  
1.1 before vpopmail is stable.  We can continue to patch the 1.0 series  
with bugfixes, while adding new features and rewriting parts of 1.1.

--
Tom Collins
to...@to...
http://sniffter.com/ - info on the Sniffter hand-held Network Tester