Oops. sorry, wrong mailing list. I meant to send this to the OpenESB - dev
mailing list. I apologize!
_____
From: Frank.Kieviet_at_Sun.COM [mailto:Frank.Kieviet_at_Sun.COM]
Sent: Thursday, March 26, 2009 11:08
To: dev_at_glassfish.dev.java.net
Subject: OpenESB community process for improving QA/SCM process
Folks, see the message below, especially "I'd like to hear about
improvements in process for GFESB as I'm in love with its potential, but,
like you, see too much community dependence on the nightly for bug fixes of
GA releases. Does GFESB have a community process for improving the QA/SCM
process?".
I'd like to start a discussion on how we can address these issues.
I'll start with a question: on many of the issues that were raised and you
subsequently fixed, what was the underlying cause of the issue being there?
Possible causes that I can think of: lack of clarity on requirements,
component was used in an unexpected way, lack of unit tests, lack of
integration tests, etc.
Please join the discussion with your thoughts.
Frank
_____
From: Frank.Kieviet_at_Sun.COM [mailto:Frank.Kieviet_at_Sun.COM]
Sent: Thursday, March 26, 2009 10:43
To: users_at_open-esb.dev.java.net
Subject: RE: Component Versioning
Hi Erik,
Thanks for your feedback. Often people add "we're working on it" and leave
it at that. I don't think that's enough, yet I don't have a clear cut
answer. What I'll do is try to start a discussion on the dev mailing list to
get ideas on how we can improve on this.
Frank
_____
From: erikslimanad_at_gmail.com [mailto:erikslimanad_at_gmail.com] On Behalf Of
Erik Sliman
Sent: Wednesday, March 25, 2009 20:59
To: users_at_open-esb.dev.java.net
Subject: Re: Component Versioning
When I was reading a comparison of ESBs on a forum, one point was that JBoss
does a better job of creating a complete GA of the ESB and all its
components. GFESB could benefit from a better integration tested release
cycle, patch process and upgrade path to ensure continuous compatibility of
components.
I've never used JBoss ESB, but used JBoos AS since version 2, back in 2002.
JBoss has a long history of rigid integration testing and a release cycle
compatible with the community development world.
I'd like to hear about improvements in process for GFESB as I'm in love with
its potential, but, like you, see too much community dependence on the
nightly for bug fixes of GA releases. Does GFESB have a community process
for improving the QA/SCM process?
On Wed, Mar 25, 2009 at 6:06 PM, Andrew McLaughlin <andrew_at_ponowaiwai.com>
wrote:
Is it just me, or is anyone else having difficulty with this? Here's what I
mean. I'm working with POJOSE, among others, and am having to experiment
with different versions of the jar and nbm files. However, since Sun's
server offers every nightly build as the same name, it's becoming
increasingly difficult to keep track. I've had to resort to unpacking each
jar that I get, finding the build date/time in the MANIFEST.MF file and then
renaming the jar to match.
But, beyond that, once I try to deploy to GF using the web interface, it
doesn't even tell me what version is deployed. In fact, there appears to be
a void of version numbering across the entire system. This can't go on for
long. How do the guys as Sun keep track of these things?
Andrew
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_open-esb.dev.java.net
For additional commands, e-mail: users-help_at_open-esb.dev.java.net