Re: RE: ANN: Barracuda 1.2.5 available

At 08:46 AM 8/27/2003 -0600, you wrote:
>Looks like the web pages had been updated under CVS but never refreshed on 
>the web site. This has now been taken care of, so http://barracudamvc.org 
>shows 1.2.5 as the current release.
>
>Also, I just noticed that the "News & Changes" document 
>(docs/changes.html) does not reflect the 1.2.5 release. Jake do you think 
>you could put some verbiage in there for the new release? If not I could 
>probably rummage through A_Changes_History and figure out what needs to be 
>said.

Looks updated to me.  Try doing a shift+refresh.  It is probably cached in 
your browser or maybe by your work's proxy server (if you use one).

BTW, can you update BarracudaDiscRack as well?  Where we were seeing 
exceptions before with the older XMLC beta release, it should work fine 
with the XMLC-2.2 release.

>Also, I just had a question on the version numbering scheme. The releases 
>I see are 1.0, 1.1, 1.1.1, 1.2.0, and now 1.2.5. I'm just wondering if 
>there is actually a system and why the jump from 1.2.0 to 1.2.5?

To be honest, it was somewhat arbitrary, but since it was the first release 
with XMLC-2.2 final and really represents a pretty stabilized Barracuda 
release, I figured that a more solid release number than 1.2.1 was 
appropriate.  I suppose we should vote on a release strategy.  The one 
thing we should keep in mind is that perception is paramount here.  If we 
continue to release everything under 1.2.x with minor increments to the 
numbers and never really get up to 2.0 or 3.0, Barracuda will always look 
immature.  A common perception is that software is never truly ready until 
it hits 3.0.  I'm not saying we should just start bumping up the numbers 
just to make things look good, but we also shouldn't merely do minor 
increments for major milestones either.

Anyone else have thoughts here?

Now, since I few things changed to correct a few issues with Barracuda 
1.2.5, the next release should probably be called 1.2.6 and come out within 
the next couple weeks.  It won't add much functionality like 1.2.0 or 1.2.5 
did, just fix a few bugs that we've found.

Jake

>Thanks!
>-shawn
>
>Roger C. Soares wrote:
>>BTW, the site is still poiting to Barracuda 1.2.0
>>Cheers,
>>Roger.
>>-- Garth Dahlstrom wrote:
>>
>>>Submitted it to Freshmeat, JSurfer, javable, serverside, and released
>>>files on SF (but could not create a news item).
>>>
>>>It's already shown up on Freshmeat...  Hopefully it will appear on the
>>>others tomorrow sometime.
>>>
>>>I'm not sure who to contact about getting us on the Jakarta elsewhere
>>>news at: http://jakarta.apache.org/site/elsewhere.html ... anyone know?
>>>
>>>Northern.CA ===--
>>>http://www.northern.ca Canada's Search Engine
>>>
>>>
>>>_______________________________________________
>>>Barracuda mailing list
>>>[email protected]
>>>http://barracudamvc.org/lists/listinfo/barracuda
>>>
>>_______________________________________________
>>Barracuda mailing list
>>[email protected]
>>http://barracudamvc.org/lists/listinfo/barracuda
>
>_______________________________________________
>Barracuda mailing list
>[email protected]
>http://barracudamvc.org/lists/listinfo/barracuda