Re: FW: JBoss 3.2 RC4

On Tue, 2003-03-25 at 11:55, Pitkanen, Nicola wrote:
> Hi Kev,
> 
> As you will be able to tell from the emails I have been firing Ari below, I have been trying to get his thoughts on upgrading to JBoss 3.2 RC4.  I have quite a few questions: 
> 1 - can you briefly elaborate on what you mean by the fact that there are less issues in BELTS with the new version of JBOSS, and therefore, what are the real benefits of upgrading now.  

My instance (which is RC4 based) doesn't throw exceptions on shutdown.
The current belts does throws an exception at shutdown that although not
harmfull is a little disconcerting. There are significant fixes to the
CMP engines handling of CMR attributes in RC4 over beta 3. Plus 100s of
other bug fixes in jboss between beta 3 (the version belts 1.0 is based
on) and rc4. I've been consistently running the latest version of 3.2
(from cvs) and have had no issues.

> 2. what do you think the risks of upgrading now are ie. has this version been used substantially enough for us to feel confident that we won't be the first to find nasty things wrong with it?

I'm confident that it's more stable than the current version.

> 3 - what will be involved in the states/territories upgrading and is this likely to be something they can do on their own? (as we have only promised to do the initial implementation for them, not ongoing support, so they would need to manage getting this done)

As there is no "upgrader" for belts (there's a new use case). I'm not
suggesting that the current 1.0 release be moved to 3.2 but that the 1.1
development keep track with 3.2 releases with the aim that 1.1 will be
released using 3.2 final.

Once we have finalised the use cases for 1.1 then we can look at the
impact of the as yet to be written upgrader use case.

> 4 - what happens if they don't upgrade? would they be able to run the next version of BELTS if we build it/test it using JBOSS 3.2 RC4

The belts package incorporates the jboss server. So many 1.1 version of
belts would use the specified server.

> --> if that all sounds promising, then we will need to get it installed on our test servers here so that we can also do some testing.

The development servers would be the first to move. This could be done
very quickly (as we would just redefine the version of jboss the system
builds with).

-k.

> Cheers,
> Nicky
> 
> 
> 
> 
> -----Original Message-----
> From: Stathopoulos, Ari 
> Sent: Tuesday, 25 March 2003 10:48 AM
> To: Pitkanen, Nicola
> Subject: RE: [Belts-developer] JBoss 3.2 RC4
> 
> 
> It's a good idea provided all the criteria mentioned below have been satisfied, and you're happy that there are no adverse affects on the application's operation....
> 
> It also helps that we're going to release another version of BELTS with extra functionality.  If we were only upgrading for the sake of JBOSS I would not advise it since it will the Sectors and systems that must take ownership of it.....
> 
> Since we are releasing a genuine build with extra functionality, then it's worth the upgrade and some documentation for the sectors and outlining the benefits and reasons.
> 
> Cheers & Good Luck
> Ari
> 
> 
> 
> 
> 
> -----Original Message-----
> From: Pitkanen, Nicola 
> Sent: Monday, 24 March 2003 05:28
> To: Stathopoulos, Ari
> Subject: RE: [Belts-developer] JBoss 3.2 RC4
> 
> 
> 
> Thanks Ari. Does that mean that you think we should upgrade the project to this version as soon as possible.  Any reasons why you think we shouldn't / can't? Also, I presume we should do some of our own testing too?
> 
> Cheers,
> Nicky
> 
> -----Original Message-----
> From: Stathopoulos, Ari 
> Sent: Monday, 24 March 2003 10:14 AM
> To: Pitkanen, Nicola
> Subject: RE: [Belts-developer] JBoss 3.2 RC4
> 
> 
> Just Standard Practice to test it for an adequate period prior to putting it out there.
> 
> Kev has stated that he has been using it, and if that means across all areas of the business funationality that may be affected and internally so that no adverse impact is expected on operational integrity than that's fine...
> 
> Cheers
> A.
> 
> 
> -----Original Message-----
> From: Pitkanen, Nicola 
> Sent: Monday, 24 March 2003 09:56
> To: Stathopoulos, Ari
> Subject: FW: [Belts-developer] JBoss 3.2 RC4
> 
> 
> Ari,
> 
> What are your thoughts on this? What impact would it have on already implemented BELTS systems?
> 
> Cheers,
> Nicky  
> 
> -----Original Message-----
> From: Kevin O'Neill [mailto:[email protected]]
> Sent: Sunday, 23 March 2003 12:30 PM
> To: BELTS - Developers
> Subject: [Belts-developer] JBoss 3.2 RC4
> 
> 
> JBoss 3.2 RC4 has hit the streets. I've been running BELTS with the 3.2
> CVS version and with no issues (in fact less issues than are currently
> encountered with the 3.2b3 version BELTS 1.0.0 is currently using).
> 
> I feel the project should be upgraded to this version as soon as
> possible, any reasons why we shouldn't can't?
> 
> -k.
-- 
If you don't test then your code is only a collection of bugs which 
apparently behave like a working program. 

Website: http://www.rocketred.com.au/blogs/kevin/



-------------------------------------------------------
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en