I have never heard the term "integration build" before and I am not sure what the difference between the 1.4 release and the 1.5 integration build? Is the 1.5 integration build like a alpha, beta, or release canidate? Or is it a branch of the main project?
I have looked at it and the organization of classes is very different, so that everything I have written for 1.4 doesn't work with the 1.5 integration build.
Just wondering if it is something I need to keep an eye on and watch the changes if it is not a branch and is more of what the future release is going to be like.
Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The 1.5 Integration Builds are milestones where amalgamations of changes on the head branch (or trunk) from various people are fixed into a servicable release by ensuring the unit tests pass or have only known issues. That is, in the analogy of a software project being like a bicycle, it's like getting the wheels and pedals back on so somebody can ride it. There's no guarantees that the brakes or bell works, but you can usually get to the corner store.
The 1.4 and (now 1.41) release is the stable release, that thousands of people have put through the alpha, beta and candidate release checks to assure some level of capability. Changes to that release are minimal and are usually back ports from the trunk that are deemed worth implementing when the balance of risk to existing behaviour versus bug severity tips toward change.
Eventually the integration builds have fewer and fewer radical changes and begin to settle down into the alpha of the next version. Then the project enters bug fixing mode and beta or release candidates are built as needed until the version ships', and then the whole cycle starts again.
So, yes, you should monitor the trunk integration builds since that's the way it will be in the next version. At least that's how it works with HTML Parser, other projects may be radically different.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've never heard about "integration release", it's simply called alpha.
I missed half a day trying 1.5 without success (all examples doesn't work) simply because there is no note on website, which version should I use (there really should be noted which version is production stable - on main WWW page)
Now i know....
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have never heard the term "integration build" before and I am not sure what the difference between the 1.4 release and the 1.5 integration build? Is the 1.5 integration build like a alpha, beta, or release canidate? Or is it a branch of the main project?
I have looked at it and the organization of classes is very different, so that everything I have written for 1.4 doesn't work with the 1.5 integration build.
Just wondering if it is something I need to keep an eye on and watch the changes if it is not a branch and is more of what the future release is going to be like.
Thanks!
The 1.5 Integration Builds are milestones where amalgamations of changes on the head branch (or trunk) from various people are fixed into a servicable release by ensuring the unit tests pass or have only known issues. That is, in the analogy of a software project being like a bicycle, it's like getting the wheels and pedals back on so somebody can ride it. There's no guarantees that the brakes or bell works, but you can usually get to the corner store.
The 1.4 and (now 1.41) release is the stable release, that thousands of people have put through the alpha, beta and candidate release checks to assure some level of capability. Changes to that release are minimal and are usually back ports from the trunk that are deemed worth implementing when the balance of risk to existing behaviour versus bug severity tips toward change.
Eventually the integration builds have fewer and fewer radical changes and begin to settle down into the alpha of the next version. Then the project enters bug fixing mode and beta or release candidates are built as needed until the version ships', and then the whole cycle starts again.
So, yes, you should monitor the trunk integration builds since that's the way it will be in the next version. At least that's how it works with HTML Parser, other projects may be radically different.
I've never heard about "integration release", it's simply called alpha.
I missed half a day trying 1.5 without success (all examples doesn't work) simply because there is no note on website, which version should I use (there really should be noted which version is production stable - on main WWW page)
Now i know....