FPC, Lazarus combinations
|Lazarus Release||Recommended FPC version||Notes|
|1.6||2.6.4 or 3.0.0||last version for Win98/ME using 2.6.4|
Explanation of the different version numbers of Lazarus
The most important thing to know is that if the last number of the version is an even value, it's a stable/published release. For example version 1.4.2 is released, and will never change, ever.
But the developers are working on two ongoing versions, which change every day. Those versions have odd last numbers. There is the fixes branch using the version 1.4.3 and the development trunk using the version 1.5. The fixes branch only receives bug fixes and will eventually be released as 1.4.4. The development version 1.5 receives bug fixes and new features. These versions are maintained using SVN (Getting Lazarus), every patch gets a 'revision'-number.
For example, at the moment of writing this the current SVN/1.7 version has revision 50714. It's available via SVN. Every night some snapshots are built from the current revision.
How about fixed bugs, in which version is the fix included?
Take this bug as an example. The target is the version in which the developers aim to get this problem fixed. In this case this means that version 0.9.12 can't be released if this bug is not fixed. This way we also have a nice list of bugs that has to be solved before a version can be released. You can see this list in the bug-tracker, using the appropriate filter.
You can see that bug 1227 is solved in revision 8004. Thus all versions with a revision number higher then 8004 must contain this patch. The revision number of version 0.9.10 is 7919, thus this fix is not included in that version. But the fix will be in the first version that will be released; version 0.9.12. Of course it's also available in the unstable svn-versions (0.9.11).
Version numbers in graph form
Maybe this will help some users understand the version numbering a bit better.
o - trunk becomes version 1.5: development + experimental stuff, fixes branch 1.4 is created | |\ | \ | | | o - (branches\fixes_1_4) - feature freeze + release candidate, based on 1.3 | |\ | | o - (tags\release_1_4_RC1) | |\ | | o - (tags\release_1_4_2) | |\ | | o - (tags\release_1_4_4) | o - trunk becomes version 1.7: development + experimental stuff, fixes branch 1.6 is created | |\ | \ | | | o - (branches\fixes_1_6) - feature freeze + release candidate, based on 1.5 | |\ | | o - (tags\release_1_6_RC1) | |\ | | o - (tags\release_1_6) - this will happen in the future
Note that trunk gets a new version right after branching. So version 1.7 from trunk exists at the same time as version 1.6RC1 in branches\fixes_1_6.