Releasing 1.1 - page 2 - General Discussion and Assistance - CHDK Forum
« previous next »
Pages: 1 [2]   Go Down

Releasing 1.1

  • 14 Replies
  • 5568 Views
*

Offline waterwingz

  • ******
  • 12138
    • Waterwingz
Re: Releasing 1.1
« Reply #10 on: 25 / July / 2012, 19:08:33 »
Advertisements
Quote from: reyalp on 25 / July / 2012, 17:21:47
The autobuild is now switched, so 1.1 is officially released.
Excellent ! To quote Shakespeare's Julius Caesar "Cry 'havoc ' and let slip the dogs of war !"

Quote
I'll update the wiki pages later, already overrun my lunch break ;)
I'll look for changes - the USB2.0 code is now mainstream for example.  And I think we still need to figure out how to differentiate the UI changes coming in 1.2 ? A new User Guides etc will be needed - would be nice if there was something like a standard  "1.2 compatible"  icon or something that could go at the top of each page or in sections that describe new features  - especially if it can become  a 1.3, 1.4 etc icon n the future...

Update :  I guess I can't put off an update to the wiki page for USB remote 2.0 any longer - the "draft" timing diagrams and block diagram really need to be fixed.
« Last Edit: 25 / July / 2012, 19:23:22 by waterwingz »
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline philmoz

  • *****
  • 3450
    • Photos
Re: Releasing 1.1
« Reply #11 on: 25 / July / 2012, 21:44:16 »
Quote from: reyalp on 25 / July / 2012, 17:21:47
I changed the name of the cfg file for the unstable build to CHDK12.CFG

Is this necessary - does the config file name have to match the build?

I would think the config filename only needs to change if there is a significant change to the file itself (e.g. the re-org that occurred in the previous version).

Phil.
Logged
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)
  g5x (1.00c, 1.01a, 1.01b)
  g7x2 (1.01a, 1.01b, 1.10b)
*

Offline reyalp

  • ******
  • 14080
Re: Releasing 1.1
« Reply #12 on: 25 / July / 2012, 21:56:43 »
Quote from: philmoz on 25 / July / 2012, 21:44:16
Quote from: reyalp on 25 / July / 2012, 17:21:47
I changed the name of the cfg file for the unstable build to CHDK12.CFG

Is this necessary - does the config file name have to match the build?

I would think the config filename only needs to change if there is a significant change to the file itself (e.g. the re-org that occurred in the previous version).

Phil.

Possibly not, but it is probably good to keep the unstable branch cfg separate from the stable one. We could do this by having a different name for dev I guess, and switching it back at release.

I would expect the UI stuff to benefit from cfg changes, but perhaps not.

I'm open to suggestions. Or changing it back if you think it's a bad idea. Personally, I don't see resetting the config each release as a big deal.
Logged
Don't forget what the H stands for.
*

Offline philmoz

  • *****
  • 3450
    • Photos
Re: Releasing 1.1
« Reply #13 on: 25 / July / 2012, 22:06:25 »
Quote from: reyalp on 25 / July / 2012, 21:56:43
Quote from: philmoz on 25 / July / 2012, 21:44:16
Quote from: reyalp on 25 / July / 2012, 17:21:47
I changed the name of the cfg file for the unstable build to CHDK12.CFG

Is this necessary - does the config file name have to match the build?

I would think the config filename only needs to change if there is a significant change to the file itself (e.g. the re-org that occurred in the previous version).

Phil.

Possibly not, but it is probably good to keep the unstable branch cfg separate from the stable one. We could do this by having a different name for dev I guess, and switching it back at release.

I would expect the UI stuff to benefit from cfg changes, but perhaps not.

I'm open to suggestions. Or changing it back if you think it's a bad idea. Personally, I don't see resetting the config each release as a big deal.

If the config files are compatible then people can try out the new version and switch back if they need to.
For me, it's annoying once you've set up the config the way you want it, to have to redo it.

Extending the config file with new items doesn't break backward compatibility; but you will lose the changes to the extra items if you go back to an old CHDK version and save the config. You could argue that this makes having a seperate config file for each version a better option.

Personally I'd prefer to keep the config file version the same unless there are major changes that would justify a name change.

Phil.
Logged
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)
  g5x (1.00c, 1.01a, 1.01b)
  g7x2 (1.01a, 1.01b, 1.10b)
*

Offline reyalp

  • ******
  • 14080
Re: Releasing 1.1
« Reply #14 on: 25 / July / 2012, 22:31:32 »
Fair enough. I've reverted the filename to CCHDK2.CFG
Logged
Don't forget what the H stands for.
Pages: 1 [2]   Go Up
« previous next »
 

Related Topics