Current revision: 5432M <---

[fodder]

I'm a bit puzzled about this. That should mean any and all things with lower numbers should be fixed, or at least the fixes are active.

And if it still bugged, then the fix doesn't work, right?

For testing islands at least, or is that the number for dwilight with bt lagging a bit? (and stable a lot)

[Indirik]

That revision number should be good for testing islands. That's both BT and Dwilight.

Stable islands are indeed farther behind. I don't think there's any easy way to determine the rev level of a stable island. All code revisions have a rev number, including new features. So if a new feature is not  moved to stable islands (like the the flagged messages), but a later bug fix *is* put on stable, then stable will be "missing" some revisions.

[Indirik]

Oh, also, the rev number given on the login page is not the associated bugtracker bug number. It is a code revision level that the devs will sometimes give in the comments to a bug report when they fix the issue. Shouldn't be too much confusion now, as the current code revision is up to 5434, but bugs are up to 6068. For a while the two numbers were pretty close, and people often confused the two.

[fodder]

dev comment:
"Fixed in revision 5421."  <--- but it's not... (and i'm talking about bt.)

[Anaris]

That revision number should be good for testing islands. That's both BT and Dwilight.

Stable islands are indeed farther behind. I don't think there's any easy way to determine the rev level of a stable island. All code revisions have a rev number, including new features. So if a new feature is not  moved to stable islands (like the the flagged messages), but a later bug fix *is* put on stable, then stable will be "missing" some revisions.

No, stable is on the same revision.  That was one of the important points about moving to a full testing/stable setup rather than a testing-copied-to-stable setup.

However, occasionally we devs fix a bug in testing and forget to copy that fix to stable.  If you notice something like this, just give a shout out (here or on the bugtracker) and we'll try and get to it quickly.

dev comment:
"Fixed in revision 5421."  <--- but it's not... (and i'm talking about bt.)

This was the one about duchy taxes not showing up in your regional tax display (RegionTaxes.php), right?

Well, the revision in question definitely fixed something there, though it looks like it might have gotten a bit mixed up.  I wasn't the one who fixed it, though, so I'll bring it up with the other devs.

[fodder]

ok.. i think i know what the problem is.... i'll go back to bug tracker

[Foundation]

dev comment:
"Fixed in revision 5421."  <--- but it's not... (and i'm talking about bt.)

The display bug was indeed fixed, what you are asking for though is a more fundamental bug that calculates the knights taxes wrong.

[fodder]

you could say there were really 3 related issues in the original report. the one fixed was not really the one i thought the most important and was mentioned as a btw, so to speak. i do have a habit of lumping many related issues into the same report.

mind you.. the amount actually paid isn't wrong... it's just on those 2 screens that it's mangled.

[Foundation]

Please separate then.