Re: [OJB-developers] cvs use

[Thomas M. <tho...@ho...>]

Hi all,

> Matt Goodall wrote:
> 
> Hi,
> 
> <disclaimer>
> I'm basing the following observations on the fact that the sourceforge
> cvs repository is still at version 0.5.200 (from release-notes.txt).
> </disclaimer>
> 

You are right: no CVS updates since 0.5.200!
To explain my point of you I have to go into OJB history a bit:
A year ago 4 or 5 people intented to work on several OJB tasks in
parallel.
We decided to use the SourceForge CVS repository.

I learned several lessons from this experiment:
- people check in code that does not compile
- people check in code that does compile but does not work
- people check in code that uses some external jars, but don't check in
these libraries
  and don't fix the build scripts accordingly
- CVS seems to have problems with CR/LF if Linux and Windows user are
using same
  files (maybe we did something wrong but we did not get it running
properly
- to get releases out I had to too a tough integration job.

At some point in time I decided that this does not work.
Now I'm maintaining the OJB source and people send in stuff they want to
contribute.
I'm deciding if and how to integrate those contributions. <no democracy
here/>
Of course I try to include everything that helps to improve OJB!
till build 200 I checked in the releases (but no intermediary snapshots)
into CVS.

But then I recognised that this is of no use as it just reflects the
latest public release.
So I decided to stop this as it took 2-3 hours for each release!
  
> There seem to be some *really* important changes going into the code
> at the moment. I would like to keep track of these changes but patches
> sent via the mailing list seem to disappear until the next release. Is
> there any chance that a publically accessible cvs repository could be
> kept up to date?
> 
> I know maintaining a version control system takes time (not much
> though) but I'm sure many people would appreciate the effort and I
> suspect it may be better for the project in the long run.
> 

I'm developing OJB on a offline laptop. Checking in intermediary
snapshots would take me too much time.

I don't think that having a source code repository is a quality
assurance in itself.
If you (as a OJB user) check out code from CVS you don't have any
guarantee that you get the stuff compiled, that it works, that the code
is covered by testcases, etc.

If you decide to wait on a new OJB release (coming in 2 - 4 week
rhythms) you can be sure that:
everything compiles, is tested etc. 

I'm not against Version control systems. I would really appreciate if
someone volunteers to do the code integration and release management job
based on a CVS repository. 

This would safe me so much time that I would even agree to check in my
source code twice a day :-)

I'm currently working on a new release (integrating all of Jakob's
interesting contributions).
I hope to get it finished this weekend.

cheers,

Thomas