Sign in Join
Wiki copytemporary

Lazarus Development Process: what changed

Revision 0 to 1. Removed lines have a minus sign; added lines have a plus sign.

Title: Lazarus Development Process

OldNewLine
1+## Who are developers
2+
3+You can find a recent list of Lazarus developers here: [[Developer pages]]\
4+You can find history of lazarus developers here: [[History]]
5+
6+## Setting the target of a bugfix
7+
8+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.
9+
10+Some criteria are:
11+
12+- 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.
13+- 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.
14+- 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.
15+
16+For more details on the various versions of Lazarus, see [[Version Numbering]]
17+
18+## What we are planning to do
19+
20+### TODOs
21+
22+1. [[Lazarus 1.8.0 release notes]]
23+2. [[Detailed Lazarus release template todo]]
24+
25+### Tasks
26+
27+1. [[IDE Development]]
28+
29+### Roadmaps
30+
31+1. [Current Roadmap](http://bugs.freepascal.org/roadmap_page.php?project_id=1) - Roadmap of current Lazarus version.
32+2. [[Roadmap]] - Current status of some parts of Lazarus (IDE, LCL and others)
33+3. [[Icon Editor Roadmap]] - Roadmap of Icon Editor Tool
34+4. [[LCL Documentation Roadmap]] - Roadmap of LCL Documentation
35+
36+## What we have done
37+
38+## What we will not do
39+
40+1. [[Lazarus known issues (things that will never be fixed)]]
41+
42+## Lazarus branches / version numbers
43+
44+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).
45+
46+ 0.9.30 0.9.30.2 0.9.30.4
47+ | | |
48+ fixes_0_9_30: -- T - 0.9.30.1 - T - 0.9.30.3 - T - 0.9.30.5 -- End of life
49+ /
50+ | 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
51+ | | more RCs | | | | | | |
52+ 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
53+ | /
54+ | / 1.2.0 1.2.2 1.2.4
55+ | / | | |
56+ fixes_1_2: | | ----- T - 1.2.1 --- T - 1.2.3----- T - 1.2.5 ---- End of life
57+ | | /
58+ | | |
59+ trunk: --- 0.9.29 --B-- 0.9.31 ------B- 1.1 -------------------------------------B------- 1.3 ------------ Developing for 1.4 or 2.0
60+
61+## See also
62+
63+- [[Roadmap]]
64+- [[Lazarus release engineering]]
65+- [[WebPageDevelopment|Lazarus website development]]
66+
67+---
68+*From the Free Pascal wiki, page "Lazarus Development Process", as it stood on 2020-08-22 after a change by Trev, out of the wiki's dump of 2024-05-26. Copyright stays with the author who wrote it, according to the old wiki's [[Licensing]] page. If you have concerns about this material, [message the admin](/wiki-contact).*

Back to history