db-ojb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert S. Sfeir" <rob...@codepuccino.com>
Subject Re: [OJB 1.1] Status?
Date Thu, 17 Feb 2005 22:13:15 GMT
Hash: SHA1

if you look at the speed at which Spring releases that is a great 
speed, it is about 1-2 months.  As far as people on 0.9 and rcs, you 
can't help those people, and they will not move as fast as we want them 
to anyway.  The point is to also get attention of activity on the 
project even if it is only a matter of perception.  If the changes are 
minimal and we have 10 bug fixes it is worth it to people to know that 
if they start using OJB and find a bug, something will get fixed and 
they will get a release within 1-2 months time if they want.  yes they 
can go get the build and fix from the repository, build it themselves, 
and be happy elves, but there is also a wider group who will not touch 
a fix until there is a tagged release.  That's the group I think we 
should cater to.  The first group, for what ever reason, is stuck in a 
version which they can't get out of.  Nothing you can do except ensure 
a certain level of backward compatibility.

Even if we adopted a 2-3 months cycle, we're not hitting that now 
because there are lots of things everyone gets excited about and wants 
to put in.  Perhaps a list at the beginning of a cycle with what folks 
want to commit to, that the group approves or recommends to move to 
another iteration would make things flow better, with the understanding 
that folks stick to their plan and not deviate.

Dunno...  I am working through the code right now and cleaning a few 
things up.  I haven't been in here for a while.  The changes I am 
making are non invasive.

Version: GnuPG v1.2.4 (Darwin)


To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org

View raw message