We have experienced a very poor performance of the svn log command on the new repository that had only a few revisions.

It took more than a minute(!) to get history that had only one revision - the initial import.

While blaming the server configuration and network security, we didn't find anything unusual that could affect the svn performance so much.

The reason was much simpler - initial import of the full project tree had more than 32,000 files, and it turned out to be too much for one revision.

Breaking the initial import into several commits solved the problem completely.

If you have a big project to import, instead of running

svn import myproject file:///opt/opencm/svnroot/trunk/myproject -m "Initial import"

write a short script to import smaller parts, like:

cd myproject

The next major version of Bugzilla was released on the 13th of April.

Bugzilla 3.6 has a lot of new features for Bugzilla users and administrators.

Here is the list of the most interesting New Features and Improvements:

- General Usability Improvements

The 'Parallel Development'  presentation we gave in our last TCE event.

'Maven 3.x will be the version Maven for the people', says Jason van Zyl, and it does look promising!

At the moment there is a 3.0.alpha.6 version released, I could't find any roadmap or dates for the planned main release yet.

I didn't have a chance to "play around" enough with this release to be able to say that all that promised is there :), but I've summarized some main issues from the Maven 3.x previews I found in several blogs/presentations/apache info pages:

* Backward compatibility

- Loads of Integration testing is done to ensure backwards compatibility

- Stricter validation of the POM is added

- Configured plugins should have their versions specified (a warning appears otherwise)

* Site/reporting is now completely extracted from the Maven core

'Maven 3.x will be the version Maven for the people', says Jason van Zyl, and it does look promising!

At the moment there is a 3.0.alpha.6 version released, and I could't find any roadmap or dates for the planned main release yet.

I didn't have a chance to "play around" enough with this release to be able to say that all that promised is there :), but I've summarized some main issues from the Maven 3.x previews I found in several blogs/presentations/apache info pages:

* Backward compatibility

- Loads of Integration testing is done to ensure backwards compatibility

- Stricter validation of the POM is added

- Configured plugins should have their versions specified (a warning appears otherwise)

* Site/reporting is now completely extracted from the Maven core

It was one of those tasks that you think "i'll finish with it in a couple of hours", but i found myself dealing with it for more than 2 days...

A customer asked me to help him with a pre-commit hook that will check the existence of the svn:needs-lock property and the commit message - very simple.
We have the message check in our pre-commit hook, and I found a few examples on the net for the svn:needs-lock property check, but all examples just didn't work!
At the end i used svn contrib check-mime-type.pl, and, although i couldn't find the real differences between my previous tries written as bash script or in perl and this one, it worked.

The final hook is attached.