Today I submitted some work in progress in our SVN. I don’t plan to release a binary for this version, because it is still work in progress. People are free to give it a try, but I recommend to not widely distribute this version of HBL.
Over the past months, we’ve taken the (bad) habit of making a huge release with each revision of the SVN. We entered a vicious circle to prevent other sites from “stealing our thunder”, and instead of “making a release with each revision”, the rule slowly became “wait until we’re ready for a release before submitting code”. This is not how SVN is supposed to work. This way of thinking has almost stopped our progress on HBL, and overall this was a bad thing. So we’re going to try very hard and change this, by using SVN “normally”: submit more often and release when we are confident.
I still expect that some people will compile and distribute versions of HBL R102, just to have the “latest and greatest”. Therefore I will try to be as clear as possible: a new revision in the SVN doesn’t necessarily mean an improvement. When we (the people actually developing the HBL, that is, currently, JJS and myself) are confident that a revision of HBL is worth releasing, you will hear it directly from us, either here or in the HBL forums, and we will do a release.
We DO accept bug reports for the latest SVN version, but only if the people who report bugs know what they are talking about.
HBL R102 is a work in progress to improve the internal stability of HBL, and to bring compatibility with Hot shots golf 2. We haven’t started using the data we gathered from the memdumps yet, so most likely, this version will NOT work for you if you have hotshots golf 2, just be patient. For hot shots golf1 or Patapon users, this revision changes absolutely NOTHING.
Of course people are free to compile and distribute R102, but if people ask you why the latest revision is not available on the official page, tell them it’s because the devs estimate that it’s not worth releasing. By the way, just so you know one of the major reasons behind this decision: before I do a release, I test HBL with all exploits on as many consoles as possible. This process usually takes several days. I don’t think anybody else who release binary versions of HBL does that.
Let me state this once again: from now on, a new revision in HBL’s svn will NOT necessarily mean a new release. When we feel ready for a new release, it will be announced here.