Hi Alexey.
I should have mentioned in my original email that I have been lead
developer on several projects. Yes, occaisonally some developers
do decide to use the Code Vault's Head Revision as their personal
sandboxes. Normally, I dealt with that behaviour immediately,
rather than waiting several months, just to avoid the kind of
hassle you guys seem to be going through.
One of the earlier statements you guys made earlier (I think I
quoted it, hope I did, anyways) was something along the lines of
"If a developer is going to experiment, they should split off a
branch, and merge back in when ready". A policy which should
always be strictly enforced.
Stability is always good. Drastic rollbacks are not good, are
much extra work, have a tendency to destabilize the code base,
and should be avoided whenever possible.
While the timing may be coincidental, the fact that it is commencing
during the rollouts of Release Candidates is, unfortunately, highly
suspicious. Especially after the fact that the dust has not yet
settled between a major blowout between JBoss Group LLC, and a number
of developers who have recently had their access revoked (in some cases
with cause, in some cases definately without a valid cause being given).
And as you may recall, the blowout included statements from various
JBoss Group LLC staff questioning the competence of some developers who
have a proven track record and have chosen to work for and/or with
another (and not necessarily competing) project(s).
And to paranoid project leads such as myself, this kind of activity
with this kind of timing makes me very nervous.
Basically, what is making me most nervous about this action was
that it is a major undertaking that is taking place during RC Rollouts,
directly affecting the version being rolled out, apparently without
any discussion among the general developer community. (Yes, this is
something I would expect not be discussed in the user community,
but I also lurk on the Developer list, and was unable to find a
discussion there or in the forums about this action).
Bottom line, I am now extremely nervous about the direction that the
JBoss Application Server is being taken, and how it is being managed.
Regards,
Steve
Alexey Loubyansky wrote:
Stephen Davidson wrote:
I hope that this rollback is not just to remove contributions from
developers that JBoss Group LLC is apparently pissed off at, as it
would indicate continued extreme childness on their part.
No, it is not. HEAD occurred to be messed up. Because, in many parts it
was used as a sandbox for researches. It's time to stabilize it. We
decided to rollback and port new code that worth it making another
iteration and, this time, doing it accurately.
Courtesy Copied to the Keel Meta-Framework group, as JBoss is
integrated as one of our modules, and we need to be aware of what
JBoss is doing, and where it is going.
We are making JBoss 4th generation more stable.
I am hoping we do not have to switch to another J2EE provider, but
the recent actions of the JBoss Group LLC have made me very, very
nervous.
Will then the other J2EE provider ask you how to manage their codebase?
Why pannic?
alex
--
Java/J2EE Developer/Integrator
Co-Chair, Dallas/FortWorth J2EE Sig
214-724-7741
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
