Releasing 1.1

As discussed in the UI thread and IRC, we are considering making the current trunk (1.1) the stable branch soon.

For the community:
Is the current trunk stable enough to be the stable branch ? If anyone has outstanding issues that don't exist in the 1.0 branch, please speak up. If you haven't tried the trunk recently, now would be a good time to do so.

When we do this:
1) The autobuild for release-1_0 will be disabled, and no further changes will be made on the branch. The final autobuild should be archive somewhere (box.net like https://www.box.com/chdk#/chdk/1/215563400 perhaps ?)

2) The current trunk will be branched to release-1_1, and the "stable" autobuild will be switched to use this branch.

3) The trunk will become the 1.2 unstable branch, which will start with the UI changes phil has been working on.

Other considerations:

Wiki documentation - do we want to try to keep anything for 1.0 around ? I'd be tempted to at least copy http://chdk.wikia.com/wiki/CHDK_User_Manual to something like http://chdk.wikia.com/wiki/CHDK_User_Manual_1.0

Script documentation would be another candidate, but it is scattered enough that I'm not sure it's worth the effort.

Other than that, pages that reference 1.0 vs 1.1 will need to be updated.

I'd also like to run the code through a pretty printer. The ideal time for this would be just before the release, so both the "stable" and "unstable" branches are reformatted, and there is no need to back merge stuff to the previous stable branch.  I'm open to suggestions on how it should be reformatted, but I don't want to get into a long discussion of code format standards. I don't care much which standard, as long as the codebase is consistent. We've discussed this before, I'll try to dig up that thread(s).

edit:
http://chdk.setepontos.com/index.php?topic=2145.msg36658#msg36658

I'm very concerned about this and all the unintended side-effects and consequences these changes will bring.

So my only answer to that is - GO  !!!!

We are all here to enjoy the ride.   Thanks for bringing us along !

1) The autobuild for release-1_0 will be disabled, and no further changes will be made on the branch. The final autobuild should be archive somewhere (box.net like https://www.box.com/chdk#/chdk/1/215563400 perhaps ?)

Uploading #1982 to the box is in progress...

EDIT:
Done, #1982 is available from the "CHDK Package Backups" section.
Wikia is updated - http://chdk.wikia.com/wiki/Downloads#Conserved_Versions

Let us close the simple chdk version. The modular CHDK is the future.

Starts the version 1.2 as developer trunk.

edit: It would also be a good time to clean up the autobuild zip file, e.g. not working changelog.txt.

msl

My plan now is to make the release next weekend. In the mean time, we can say the trunk is in "release candidate" state. Users are encouraged to try it.

Done, #1982 is available from the "CHDK Package Backups" section.
Wikia is updated - http://chdk.wikia.com/wiki/Downloads#Conserved_Versions

Thanks

edit: It would also be a good time to clean up the autobuild zip file, e.g. not working changelog.txt.

Good reminder.

I'm inclined to go back to a manually maintained changelog that just mentions big, user visible changes. A link can be provided to the svn log for anyone who is interested.

My plan now is to make the release next weekend.

Any thoughts on how to manage the wiki at this point ?

Almost worth having a brand spanking new CHDK2 one that we move stuff over to as it gets updated .. the old one does not go away but slowly dies of link rot.

Since both philmoz and tsvstar have branches open for the UI stuff, I've to defer reformatting the code.

I've created the new stable branch https://tools.assembla.com/svn/chdk/branches/release-1_1

To avoid confusion (?) I'll hold off updating the wiki and version in the trunk until hacki has switched the autobuild over.

edit:
and by updating the wiki, I just mean the downloads and release strategy pages that refer to the different builds, not resolving the big documentation questions.

and by updating the wiki, I just mean the downloads and release strategy pages that refer to the different builds, not resolving the big documentation questions.

darn ....

Just a quick note to say that I've replaced ACID with a version which lets you choose either the 'stable' or 'trunk' versions. The s100 and g1x are only available in the trunk at present and some users had asked me to update Acid to find them.

OSX, Windows and Linux versions are available, but as yet I have not produced the German and Spanish versions.

My program which scans the 4 websites daily looking for new SDM. CHDK and CHDK-DE builds (and hence prompts me to update the Acid tables) has also been updated to scan the 'trunk' site as well as the 'stable' one.

The autobuild is now switched, so 1.1 is officially released.

CHDK stable is 1.1, available from http://mighty-hoernsche.de/

CHDK unstable is 1.2, available (once the next build completes) from http://mighty-hoernsche.de/trunk/

I changed the name of the cfg file for the unstable build to CHDK12.CFG

Guidelines
1.0
no further changes

1.1
Bug fixes
Simple / low risk changes to maintain compatibility with the trunk (e.g. cosmetic code rearrangement, script compatibility like the earlier param changes etc)
Other trivial / low risk enhancements may be accepted on a case by case basis.
New ports. Until the 1.2 has stabilized, new ports should go into both trees, unless major changes are required to non-platform code, in which case they should probably go in the trunk

trunk (1.2)
Everything else. The work in-progress UI stuff can be merged back into the trunk any time as far as I am concerned, this should be up to phil and tsvstar to decide.

I'll update the wiki pages later, already overrun my lunch break