Subversion revision matching 0.6.1 SDK

[wally]

Can someone confirm if subversion revision 1798 is an exact (or the closest) match for the code used in the 0.6.1 SDK?
With repository URL
https://crayzedsgui.svn.sourceforge.net ... ags/v0-6-1

The 0.6.1 tag was created at revision 1780, but then there were a few changes in this "tag branch" after that so I wasn't sure.

Thanks

(edit: I'm asking because I used to use the SDK, but now I'm setting up an svn:externals reference to a specific code revision in my project)

[scriptkid]

Yes, i cannot promise an exact match, but it's surely the closest. Maintenance development on 0.6.1 happens in the v0-6 branch.

[CrazyEddie]

Just to add, generally speaking, the code in v0-6 should be pretty much rock-solid stable as far as comparisons with the 0.6.x releases go. Obviously occasionally we pull a few boners and the build or whatever might get broken for a day or two.

To put it another way, perhaps... The v0-6 branch is the stable code, where possible all bug fixes go in there first, and API and ABI compatibility should be maintained throughout the lifetime of that branch. The 'releases' - 0.6.0, 0.6.1 and 0.6.x, are basically snapshots of this stable codebase.

For my own devices, it is preferable to have people using the SVN stable branches instead of the releases; it's great to be able to get bug fixes to people within a week or so (or even a couple of days sometimes ). Obviously many people prefer the precompiled option though, and that's fine if you can stand the wait for the fixes

CE.

[wally]

Thanks for the info, both of you.

From the point of view of integrating 3rd party libraries into my projects, I prefer to know when I'm getting an update to those libraries. Even if they're only minor "maintenance" updates. It's not that I don't trust the library, it's more that I want to know when I should give related features in my app more of a test. I'm probably being paranoid.

That's why I'm referencing a specific revision (e.g. 1798) in my externals.

And yes in general I could reference a specific revision of the .../branches/v0-6 and get the same result as referencing a (different) specific revision of .../tags/v0-6-1
(though not in the case of v0.6.1, since a few changes were made to it after the copy from v0-6 branch).