Well, yes, and no. The last official binary release from titer was 0.7.1. I believe that everyone, including myself, thought that this was a build from titers last svn revison which was 69. As previously discussed, HB 0.7.1 is now believed to have been a binary created from svn rev 63. Now, it gets a bit murkier, as there is another target app in HB, which is Instant HB (which you modified in svn rev 72) which has taken advantage of all of the changes post svn rev 63.johnallen wrote:I suggest that we not use the SVN revision when discussing release builds. Every time we check a change in, the revision is going to increment. With 4 or 5 of us commiting changes, this revision will increase fairly rapidly.
We should probably follow the release versions previously used in HB. Does anyone know the current convention for versioning releases?
Looks like the current is 0.7.1....next is 0.7.2?
So, the two targets (at least as far as the mac gui version goes) are not compatible from the same svn rev.
HB compiled from rev 64 plus has optical drive issues. IHB compiled from svn rev 63 isnt even called Instant Handbrake, it was Handbrake Express at that time and lacked several features found in the newer revs.
So, it is sort of a tale of two Handbrakes. Now, what I have done is backward ported HB to use the ScanController and Drive Detector from svn rev 63 but keep the newer code from svn rev 71 which rhester and company worked to hard to upgrade primarily in the x264 area for the new iPod format. I did this because using the above mentioned code for optical drive scanning caused HB to crash. So I ported backward to the last known working release that didnt crash.
Now as far as commiting changes, up to this point we have been working together to try to decide when we want to commit changes to keep the tree inline and make sure we are all working from the same slate. We are playing quite a game of catch up as we are finding out more and more where HB was when titer last left it.
So, in summary, I agree that we not use svn revison upon discussing release builds, but at the same time, it probably is important at least to those of us trying to sort this out, to realize which svn rev each release build comes from.
Yes, I believe that the next rev would be 0.7.2 at least as far as the past versioning convention has been to date.
One other thing to consider: we have binary release being distributed courtesy of MK2000 which has a fatal flaw in that as soon as you attempt drive detection, it crashes.
Although I dont want to publicly release anything too soon, it may be worth trying to release a build with the same new h.264 capabilities that doesnt crash.
These are just some of my thoughts. But, I am only one developer and am in no position to decree anything.