Over the last several months I have encountered several problems with 
Oracle (8.1.7/9.2)/TopLink 9.0.3/JBoss 3.0.4 configuration.  When I have posted
to the forums, most of the time I am told to move to 3.2 of JBoss.  But 3.2 is 
Beta or a Release Candidate and is not listed on the JBoss downloade page. 
My management is interpreting the releases on the JBoss Download page 
as the production or recommended release. Are they interpreting this correctly? 
If not, then how do we determine what the current stable production release of 
JBoss is?    On sourceforge.net I find 3.0.4, 3.0.5, 3.0.6 and 3.2.  In a typical 
software product you have a major Releases and minor releases, even for open source
products. For example 3.0 and
3.2 would be major releases and 3.0.4,3.0.5, 3.0.6 are minor releases to fix bugs.  If 
these 
are minor releases that fix bugs and 3.0 is the current production release, my 
expectation
would be that as 3.0.5, 3.0.6, etc are released the jboss downloads page would be 
updated to reflect that for example 3.0.6 is the latest production release and what 
bugs 
are rolled into this release.  But I do not see this outlined anywhere.  Further more 
there are 
cases where I see a bug and I see that it is stated that it is fixed, but I cannot 
find the fix 
anywhere or I download a patch and compare the patch say against my 3.0.4 src and 
find that there is no difference and in fact it does not appear to be fixed.  How are 
people 
handling these situation?  I will accept that I may be lost and would appreciate 
someone 
putting me on the right Track.  At a minimum I do not want to move to something like 
3.2 if 
it is not considered a stable production release.  
 
Comments/Help please. 
 
Thanks 
 
Mike H. Sr. 
����^�����)�{(��[�8b�A�zE���&z� y�!y�ޞm���)��r����A��.���j)b�   
b��A��.����l���q���z�m��?�X���(��~��zw��X�����b��?��,��

Reply via email to