Re: monit 4.0 release todo list

[Martin Pala]

Jan-Henrik Haukeland wrote:

> TODO items:
> ...
>
> 4) Re-add the possibility to use a request in protocol tests
>   Responsible: Martin
I looked on it - i think the best will be to revert to Port_T usage in 
check function facade instead of Socket_T and refactor present socket 
code to utilize current Port_T structure for socket or socket object. It 
is true, that the only module which utilizes parameters is HTTP 
currently, but there are lot of protocol tests, which potentialy can 
support optional parameters too, for example:

- ldap modules can support seach filters, server controls
- http module can support returned page cheksumming
- pop3, smtp, imap, ldap, etc. can support autentization methods

Because these and other modules (including non-implemented 'future' 
tests) have sometimes very specific needs and they are not reusable for 
other modules, the best solution i think is to provide access to whole 
service's 'port' configuration (which is easily extensible) to testing 
modules => such solution is universal and won't involve refactoring in 
the future. In addition in this case it is more effective to handover 
just one pointer parameter, than handling of value parameters with 
static data (less memory).

What do you think?

> Release plan:
>
> - I suggest that we try to set a release date no later than August 1.
>
>  
I think it is too soon. We shall test every function and it's reaction 
to different environments and conditions, which will take lot of time. 
Before such complex tests can start, i think we must completely freeze 
the code and accept only bugfixes of detected bugs. Because the 
refactoring isn't finished completely and new functions  are to  be 
added,  i think we can have first beta (suitable for testing) at the end 
of upcomming week. I think it is possible to  prepare stable release 
candidate until beginning of september.

Martin