Web-CVS acces to the repos

[neo]

Hello,

is it possible to have a web cvs acces to you repositories?

So it is possible to view the changes online and determine what happened in the past.

greetings
Andreas

[Daniel Halbe]

This is one of the things we are discussing at the moment.

Daniel

[neo]

This is one of the things we are discussing at the moment.

Daniel

And what about the build versions?

I'm testing nearly every day and it is still build number 6048 or did I miss somethin?
So it is a bit hard to explain bugs to a given build number because it does not change but the code does.

[Martin Heiland]

Uhm, thats a point for sure, lets investigate about this tomorrow

[Martin Heiland]

I talked about this with the server development team leader. The case that there is a build number in the current community edition itself is a bug, because you check out the source, the build number is set when building the package on your machine. For sure this is not usable for bug reports, please provide the checkout date instead of the build number when reporting bugs. At least until the build number problem has been fixed.

[neo]

Ok, thanks for the fast answer.

Another thing to mention is, what about the status of CVS?
At the moment it does not compile cleanly.

Could it be possible to remain the CVS in a stable state (or some sort of stable state)?

[Daniel Halbe]

Hmm, problem is that a realtime cvs is wanted by many code contributors. On the other side we loose stability with this because we can not guarantee you can build a full functional ox at time x.

Had a longer talk with Francisco from development team while travelling back from german Cebit, we arrived in office olpe ten minutes ago Perhaps best solution would be to update the CVS every week / two weeks and review the build results via tools like cruisecontrol before updating public cvs.

R&D has to take a descision - the above is only my opinion as non-developer

Daniel

[neo]

Hmm, problem is that a realtime cvs is wanted by many code contributors. On the other side we loose stability with this because we can not guarantee you can build a full functional ox at time x.

Had a longer talk with Francisco from development team while travelling back from german Cebit, we arrived in office olpe ten minutes ago Perhaps best solution would be to update the CVS every week / two weeks and review the build results via tools like cruisecontrol before updating public cvs.

Hmm, what about the idea to setup two CVS (one public and one for code contributors) or creating a branch with an increased buildnumber and a clean compile would help a bit. Of course the branches are out of scope because they are development snapshots.