<br><br><div class="gmail_quote">On Sat, Jun 6, 2009 at 5:16 PM, Bill Williamson <span dir="ltr"><<a href="mailto:bill@bbqninja.com">bill@bbqninja.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="gmail_quote">On Sun, Jun 7, 2009 at 4:25 AM, Michael T. Dean <span dir="ltr"><<a href="mailto:mtdean@thirdcontact.com" target="_blank">mtdean@thirdcontact.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
The official position is you must use the same SVN revision on all systems. If you use different ones and don't see any problems and you're happy, that's fine. If you use different ones and /do/ see problems, it's up to you to verify that the differing versions are not causing the issues /before/ reporting any bugs to Trac/wasting the developers' limited time (i.e. ask on -users list first, test with identical revisions, ...).<br>
<br>
Mike<div><div></div><div><br></div></div></blockquote><div><br>So, not attempting to start another "happy flame festival," but this completely contradicts what Robert said earlier. It's this sort of confusion (and I know why the main devs don't want to get involved, it never ends "nicely') that drives us users trying to generally "do the right thing" batty :)<br>
</div></div><br>
</blockquote><div><br>They're actually complementary pieces of information-- The policy is that schema and protocol changes won't happen in a stable branch (although rules can go out the window to fix critical bugs, and always include a clean upgrade path). The *troubleshooting* policy is that if something doesn't work with mismatched revisions, one would be asked to reproduce the problem with matched, unpatched revisions.<br>
<br>Any two boxes running the same stable release *should* be protocol and schema-compatible, it's just not tested with all possible revisions against one another. Thus, the standard troubleshooting approach would be to ask the user to remove all patches and match revisions, then attempt to reproduce the issue.<br>
<br>Robert <br></div></div><br>