Thank you for your help. I see the process of .po file updating is somewhat of an art form.
I will save your last message for reference in the future.
> Everything since the fork
> point has to be merged. I've forgotten exactly when
> that was. If Chris
> doesn't remember the exact revision number, we're
> going to have to do a lot
> of annoying homework. Did 1.7.2 come out after the fork?
> If so, everything
> in the 1.7.2 release note and everything in the 1.7.3
> release note I didn't
> finish writing, which might or might not include stuff I
> forgot to document
> at all.
Unfortunately, I don't remember exactly when we forked. I believe it was shortly before 1.7.2. I believe Emanuel had just joined us and made a new directory and a big commit to it without realizing we where trying a mechanized approach first. We all talked a bit, then Chris grabbed the (then current) trunk branch and we started at it.
Unfortunately, what he grabbed didn't coincide with any particular release nor did we note the revision in any particular way. I just "assumed" you folks were on top of it and maybe svn was logging this in some fashion that we could extract later. Is that the case?
What can I say, I don't know anything about this stuff since this is my first project of this nature.
So, that is what I know.
> We should have just shut down trunk/ for the duration, period.
In hind sight, that might have been nice. I believe you and I had this talk some months ago. We decided that we wanted to remain friendly to current users and developers.
The down side is that we just keep shutting folks down that want to overhaul RG. I think really we should just ask that folks only correct bugs that make it crash.
I think a 1.7.3 might be nice to roll out, but I still have some issues with some of the recent "half" completed changes to the event and volume rulers: Bar width, line of controller insertion, and multiple selection methods.
After some resolution on those items, I could see rolling out a 1.7.3 and then freezing the thing.
As far as porting things across. I think we should just do the best we can with what we know and as people complain about missing features in the port, we can go back and find them. I hope most of that will become apparent after we get the port up and running.
Well, those are my thoughts on things.