Maybe this will help some users understand the version numbering a bit better. Of course it's also available in the unstable svn-versions (0.9.11). But the fix will be in the first version that will be released version 0.9.12. The revision number of version 0.9.10 is 7919, thus this fix is not included in that version. Thus all versions with a revision number higher then 8004 must contain this patch. You can see that bug 1227 is solved in revision 8004. You can see this list in the bug-tracker, using the appropriate filter. This way we also have a nice list of bugs that has to be solved before a version can be released. In this case this means that version 0.9.12 can't be released if this bug is not fixed. The target is the version in which the developers aim to get this problem fixed. How about fixed bugs, in which version is the fix included? Every night some snapshots are built from the current revision. These versions are maintained using SVN ( Getting Lazarus), every patch gets a 'revision'-number.įor example, at the moment of writing this the current SVN/1.7 version has revision 50714. The development version 1.5 receives bug fixes and new features. The fixes branch only receives bug fixes and will eventually be released as 1.4.4. There is the fixes branch using the version 1.4.3 and the development trunk using the version 1.5. For example version 1.4.2 is released, and will never change, ever.īut the developers are working on two ongoing versions, which change every day. 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. Last version for Win98/ME using fpc 2.6.4Įxplanation of the different version numbers of Lazarus FPC, Lazarus combinations Lazarus Release
0 Comments
Leave a Reply. |