[jcifs] 0.7.0 release schedule

Michael B. Allen miallen at eskimo.com
Sat Nov 23 06:33:20 EST 2002

And next week someone will say "well ... keep in mind this is only beta
code." No. The jcifs-0.7.0b9 package and all 0.7s that came before it
are BETA. This means that it has not been tested thoroughly. I do not
recommend that beta code be used in production applications. Regardless of
what version of jCIFS you are using, beta or otherwise, you should test
the functionality you will be using thoroughly, possibly with regression
tests using JUnit or similar, and report any issues to the jcifs mailing
list. In this way you will have the confidence to move forward in your
application and you will have the test results to show your managers
that the package has passed your "certification" process. If after doing
this you are still not confortable with the b flag, you can expand your
tests and help bring the jCIFS package out of beta. I cannot make any
predictions about when and under what rules packages are released due
to the dynamic nature of software development. Release schedules are
pacifiers for managers and we don't have those here.

On Fri, 22 Nov 2002 08:21:42 -0500
Matthew Tippett <matthew.tippett at sympatico.ca> wrote:

> This comes down to more of an education issue.
> Find out what there concerns about beta software.  Most likely  their 
> primary concerns would be the lack of support and the tag beta is 
> associated with untested code.  This is true with tradition proprietary 
> code, but...
> 	o Michael does more than a valiant effort of support.  Turnaround time 
> within days.
> 	o Michael is stubbornly waiting until there are no known bugs before he 
> *NAMES* it 0.7.0.  This is a good thing becuase of integrity, but the 
> contrast to proprietary systems is more of a 'we will go ahead with 
> these known bugs'.
> Be careful about painting all applications with the same brush.  Version 
> names are purely a tag that represents the business' view of what state 
> the application is.  Michael could just as easily name it JCIFS-20021120 
> without the beta tag and that would make no difference to the quality of 
> the usability of the code.
> Most proprietary code ships with bugs, Michael is holding back shipping 
> (or naming) 0.7.0 until he has no *KNOWN* bugs.
> Matt 'Has gone through naming games too many times' Tippett
> ivo.vdmaagdenberg at pandora.be wrote:
> > hi, 
> > 
> > i am employing the jcifs-0.7.0b8 to do NTLM-authentication of users on our
> > domaincontroller from within a j2ee container (tomcat 4.0.4). i works,
> > which is great altogether! 
> > 
> > but, since the jcifs 0.7.0 package is in beta i looked on the jcifs
> > website to find out when the release date could be for 0.7.0.: not found.
> > 
> > the point is that my boss, sysadmins and me too don't really like to
> > employ beta version software in a production environment.
> > 
> -- 
> Matthew Tippett - matthew.tippett at sympatico.ca - (416) 435-4118
> Technology Forum - http://www.technology-forum.org/
> Commercial Open Source - http://www.commercialos.org/

A  program should be written to model the concepts of the task it
performs rather than the physical world or a process because this
maximizes  the  potential  for it to be applied to tasks that are
conceptually  similar and, more important, to tasks that have not
yet been conceived. 

More information about the jcifs mailing list