quote:
Originally posted by Apatik
About the changelog filename, I agree we could/should make different changelogs for different builds, but then again we would get complains because there would be too many files to manage.
To answer the O.P., I have to ask : are you checking everyday for a new changelog/new build? What's the issue if you didn't get an email (yet, the mail was sent this morning) about a new changelog? Do you take note of what you've worked on? We may not be helping, and I know everyone has their own way to get the work done, but it seems to me you're kinda confusing yourself here.
The changes in the aboutbox were bumped to 681 in case some of the translators missed them in 677. If you already translated it, what's the big issue?
I'm not asking you to make new changelogs for every release. By all means keep adding new changes to the top of the current one. What you need to do, however, is change the filename to reflect the latest change.
No, I'm not checking every day for a new build. When the e-mail about release 677 came out, I downloaded the changelog and beta file at once, then translated it and handed it in on Wednesday (the deadline). However, just after turning in my 677 translation, another Danish translator informed me that he had just downloaded the change log and found that 681 was now the newest version. Of course I was annoyed about this when I had just handed in my 677, which was apparently already obsolete.
And as of today, the newest version in the changelog seems to be - once again - 677 (even after deleing my cache!). What happened to 681?
So no, I wouldn't attribute my confusion to incompetence on my part. I've been doing this since 2002 and never had a problem before.
Easy on the change logs...
/ 
