[Scummvm-devel] Re: [Scummvm-cvs-logs] CVS: scummvm/simon simon-md5.h,NONE,1.7.2.1

Travis Howell kirben at optusnet.com.au
Sat Aug 14 00:14:01 CEST 2004


Max Horn wrote:
> Am 14.08.2004 um 06:37 schrieb Travis Howell:
>
>> Update of /cvsroot/scummvm/scummvm/simon
>> In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv14407/simon
>>
>> Added Files:
>>       Tag: branch-0-6-0
>> simon-md5.h
>> Log Message:
>>
>> Back port Simon engine detection changes
>>
> Uhm,
>
> Kirben, for my taste those recent backports (HE, Windows platform,
> Simon MD5) are going a bit to far -- those are big feature backports,
> not just small isolated bug fixes, some with rather deep impact (Simon
> MD5 removes targets, for example). The main idea of having a 0.6.x
> branch is to be able to backport important bug fixes, and then be able
> to make a bug fix release, *if desired*.
> Neither of those "backports" qualifies in that category, though....
>
> If we end up backporting all our 0.7.x changes, there is no point in
> keeping a separate branch...
>
> In any case, I'd prefer to see a 0.7.0 release next over a 0.6.2
> release, so maybe this discussion is moot :-)

What HE changes ? I made no HE specific changes in the last series of 
commits.
The last series of commits to 0.6.0 branch were mainly to sync changes 
between save game versions on two branches. Since  a few bug fixes required 
save game to be increased in main branch and were worth back porting. Is 
always good to have save game version the same between release version and 
CVS when possible too.
The reason I back ported the Simon detection changes (Along with the 
required Windows platform), was for the Dreamcast port, where those 
particular games have auto detection issues. So they would be classed as a 
bug fix, although mainly specific to that port. 





More information about the Scummvm-devel mailing list