release 1.0.0 soon? when? how? discuss. - page 3 - CHDK Releases - CHDK Forum
« previous next »
Pages: 1 2 [3] 4   Go Down

release 1.0.0 soon? when? how? discuss.

  • 36 Replies
  • 27248 Views
*

Offline waterwingz

  • ******
  • 12138
    • Waterwingz
Re: release 1.0.0 soon? when? how? discuss.
« Reply #20 on: 12 / December / 2011, 21:05:28 »
Advertisements
Quote from: thepanoguy on 12 / December / 2011, 21:01:33
Starting a new development and writing code from scratch would be a better proposition than breaking the existing code base.
I don't think we plan to go quite that far ....
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline fe50

  • ******
  • 3147
  • IXUS50 & 860, SX10 Star WARs-Star RAWs
    • fe50
Re: release 1.0.0 soon? when? how? discuss.
« Reply #21 on: 13 / December / 2011, 05:12:38 »
Logged
*

Offline outslider

  • *****
  • 762
Re: release 1.0.0 soon? when? how? discuss.
« Reply #22 on: 13 / December / 2011, 06:28:19 »
It's good to hear this idea, reyalp! I'm thinking about changes in color palettes stuff (whole idea ho it works) and having experimental branch I could not be afraid about breaking current stability.
Logged
if (2*b || !2*b) {
    cout<<question
}

Compile error: poor Yorick
*

Offline waterwingz

  • ******
  • 12138
    • Waterwingz
Re: release 1.0.0 soon? when? how? discuss.
« Reply #23 on: 13 / December / 2011, 07:17:38 »
Quote from: reyalp on 12 / December / 2011, 17:23:15
A proposal:
  • We declare the current trunk to be the "stable" version, and release it as 1.0 (or maybe 1.x since CHDKDE already took 1.0 ?)
  • A branch is created from the stable version, for ongoing bug fixes
  • The trunk becomes a development branch for 2.x
  • Work continues in the trunk
Is the definintion of 2 & 3 reversed ?  Don't you want to do bug fixes (only) in the trunk and new developments in branches ?

Regardless, any thoughts on how the branches get merged back into the trunk ?

Also, is there a "goal" for 2.0, 3.0, 4.0 etc ?  Maybe a six month rolling cycle with a code freeze one month before the update ? 
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline reyalp

  • ******
  • 14080
Re: release 1.0.0 soon? when? how? discuss.
« Reply #24 on: 13 / December / 2011, 16:28:46 »
Quote from: waterwingz on 13 / December / 2011, 07:17:38
Is the definintion of 2 & 3 reversed ?  Don't you want to do bug fixes (only) in the trunk and new developments in branches ?
No. Practically, I think the way I have it is simpler. You create a new branch for each stable release, rather than merging the development release back into the trunk when you release.
Quote
Regardless, any thoughts on how the branches get merged back into the trunk ?
They don't, that's why the trunk is always the development branch ;) I guess you are asking more about the development cycle though:
Quote
Also, is there a "goal" for 2.0, 3.0, 4.0 etc ?  Maybe a six month rolling cycle with a code freeze one month before the update ? 
Based on past experience that seems to be setting the bar a bit high with regards to our level of organization. That said, I think your outline is good. I would like to keep the development->release cycles relatively short: Put in a few major features, stabilize for a while, release, repeat.

One open question is where new ports go, but porting platform code in either direction should not be a huge deal.
Logged
Don't forget what the H stands for.
*

Offline waterwingz

  • ******
  • 12138
    • Waterwingz
Re: release 1.0.0 soon? when? how? discuss.
« Reply #25 on: 13 / December / 2011, 16:50:04 »
I think I see the distinction now.   

At some point you label what you think is a stable SVN version in the main trunk as 1.0  ( e.g. 1.0 = SVN version 1546) and then continue with the normal SVN update process ( e.g. 1547, 1548 ...) as new features are added / changed and bugs fixed.

If you apply a bug fix to the SVN version that is labelled 1.0 (e.g. 1546),  it becomes a branch and get labelled 1.1.  As long as you also apply the bug fix to the current version in the trunk (maybe 1578 by then),  you never need to merge the branch back in.

At some point down the road ( six months maybe ) when you again think the trunk is stable,  you label that version 2.0 ( e.g. 2.0=SVN version 1743) and start the process again.

Does that seem right ?




Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline philmoz

  • *****
  • 3450
    • Photos
Re: release 1.0.0 soon? when? how? discuss.
« Reply #26 on: 13 / December / 2011, 17:02:15 »
I don't think you would want to branch for every bug fix / improvement.

My view is that the stable (1.x) branch would still have bug fixes and improvements made (including new ports); but the version number and branch would stay the same.

Any bug fixes and improvements would also be done in the main trunk (if applicable).

At some point the trunk is deemed stable, another stable branch is created and the cycle continues.
You also need to decide if the 1.x branch then dies and is no longer updated.

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: release 1.0.0 soon? when? how? discuss.
« Reply #27 on: 13 / December / 2011, 22:13:06 »
Quote from: philmoz on 13 / December / 2011, 17:02:15
My view is that the stable (1.x) branch would still have bug fixes and improvements made (including new ports); but the version number and branch would stay the same.

Any bug fixes and improvements would also be done in the main trunk (if applicable).
Exactly what I had in mind. The basic idea is that the "stable" branch is feature frozen, and should be expected to be as functional as possible at any time. Script APIs, user interface etc shouldn't have any radical changes. The development branch may have features that are broken, or get reworked in incompatible ways over a longer period of time.
Quote
At some point the trunk is deemed stable, another stable branch is created and the cycle continues.
You also need to decide if the 1.x branch then dies and is no longer updated.
My feeling is that it dies.
Logged
Don't forget what the H stands for.
*

Offline waterwingz

  • ******
  • 12138
    • Waterwingz
Re: release 1.0.0 soon? when? how? discuss.
« Reply #28 on: 13 / December / 2011, 22:44:21 »
Oh crud - posted a parrallel conversation to this in the ELF thread.  Here's the diagram I used  - I think it reflects what everyone is saying here :
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline fudgey

  • *****
  • 1705
  • a570is
Re: release 1.0.0 soon? when? how? discuss.
« Reply #29 on: 18 / December / 2011, 08:51:15 »
Quote from: reyalp on 12 / December / 2011, 17:23:15
We've discussed this in the past, going back and forth without any real conclusion. I don't want to do that again, so unless someone comes up with convincing objections, I'm going to make this this happen in some form before integrating the above mentioned changes in the trunk.

No objections here! I completely agree that there are big, wonderful changes brewing up that each have the rather likely potential of breaking the trunk for some cameras...  :D
Logged
Pages: 1 2 [3] 4   Go Up
« previous next »
 

Related Topics