Difference between revisions of "Lazarus Development Process"
m |
|||
Line 69: | Line 69: | ||
* [[Roadmap]] | * [[Roadmap]] | ||
− | |||
− | |||
− | |||
− | |||
− |
Revision as of 14:40, 5 March 2017
│
English (en) │
français (fr) │
русский (ru) │
Who are developers
You can find a recent list of Lazarus developers here: Developer pages
You can find history of lazarus developers here: History
Setting the target of a bugfix
When new bugs are entered, we try to give them a target in which version the bug will be fixed. If a bug is set to post 1.2, that means the developers think this bug is not important enough to block a 1.0.x release. Of course you can make sure these post 1.2 issues are fixed in the 1.0.x release by providing patches for these issues.
Some criteria are:
- Only gtk2, qt and win32 widget sets are stable in 1.0.x. Bugs for other widget set (carbon) are set to post 1.2.
- Until 1.0 there will be a feature freeze. New features and components generally get a post 1.2 target. Bugs affecting stability have a higher priority than bugs fixing the implementation of a property.
- Some components are not stable enough and should be disabled for 1.0.x. If they are disabled, then fixing them before 1.2 will not be necessary.
For more details on the various versions of Lazarus, see Version Numbering
What we are planning to do
TODOs
Tasks
Roadmaps
- Current Roadmap - Roadmap of current Lazarus version.
- Roadmap - Current status of some parts of Lazarus (IDE, LCL and others)
- Icon Editor Roadmap - Roadmap of Icon Editor Tool
- LCL Documentation Roadmap - Roadmap of LCL Documentation
What we have done
- Lazarus 1.6.0 release notes
- Lazarus 1.4.0 release notes
- Lazarus 1.2.0 release notes
- Lazarus 1.0 release notes
- Lazarus 0.9.30 release notes
- Lazarus 0.9.28.2 release notes
- Lazarus 0.9.28 release notes
- Lazarus 0.9.26 release notes
- Lazarus 0.9.24 release notes
What we will not do
Lazarus branches / version numbers
This ASCII art schema shows what the Lazarus developers have chosen as branching policy for the Lazarus 1.0 release. It also illustrates the way current development works. Time goes from left to right; the different branches are shown vertically. B indicates a branch point, T a tag (release).
0.9.30 0.9.30.2 0.9.30.4 | | | fixes_0_9_30: -- T - 0.9.30.1 - T - 0.9.30.3 - T - 0.9.30.5 -- End of life / | 0.99.0(1.0.RC1) 1.0.0 1.0.2 1.0.4 1.0.6 1.0.8 1.0.10 1.0.12 | | more RCs | | | | | | | fixes_1_0: | ------T - 0.99.1 -< .. >-- T - 1.0.1 -- T -- 1.0.3 -- T -- 1.0.5 -- T -- 1.0.7 -- T -- 1.0.9 -- T -- 1.0.11 -- T -- End of life | / | / 1.2.0 1.2.2 1.2.4 | / | | | fixes_1_2: | | ----- T - 1.2.1 --- T - 1.2.3----- T - 1.2.5 ---- End of life | | / | | | trunk: --- 0.9.29 --B-- 0.9.31 ------B- 1.1 -------------------------------------B------- 1.3 ------------ Developing for 1.4 or 2.0