I'd say lets always call 'trunk' just chdk. After all, it is the version on which the most people contribute, the version most people use - special names are good for branches and forks.
About the versioning.. As we're already at 0.5, why dont pursuit a versioning method like the linux kernel guys use.. odd numbers for unstable/development releases, even numbers for stable releases.. (0.5.x for dev, 0.6.x for a stable one, 0.7.x for a dev version again..)But honestly, i dont see the necessity for a distinction between stable & development releases.. In chdk its "either it works, or it does not". Things that doesnt work wont get commited to trunk anyway, and small things like the "sporadic raw" wont be noticed if there's only a little community of testers.
# @printf " %s-%s (%s, #%s): MEMISOSIZE used: 0x%s\n" \# $(PLATFORM) $(PLATFORMSUB) $(PLATFORMOS) $(PLATFORMID) \# `tail -c16 $(topdir)size.txt | head -c6` >> $(topdir)bin/caminfo.txt
Sounds good, i can host some stable releases on mighty-hoernsche.de .. maybe wrap them into a nice download page.. (And i probably should get another domain name)
Started by toinech General Discussion and Assistance
Started by PhyrePhoX « 1 2 3 » Feature Requests
Started by Stanislas « 1 2 » General Help and Assistance on using CHDK stable releases
Started by carl1864 General Chat
Started by ultimA General Discussion and Assistance