Sign in Join
Wiki copytemporary

Revision 2 of 4, by Maxim on 5-25-2024. The page as it is now.

Lazarus 3.0 fixes branch

Note: This page is used internally by the Lazarus team.
The data in this page does not represent the full extent of what is included in the fixes branch/versions

 

For a list of what was merged to the Fixes branch please visit:

Open issues listed on the linked milestones are loosely targeted for the indicated version. Their final inclusion depends on the available man-power and/or contributions. Release may or may not be deferred for any non resolved issue.

 

 

This page contains the revisions to be merged from main branch to the Lazarus 3.0 fixes branch.

These are only fixes made after the branch was created. For other fixes made since the previous release (2.2) see Git and Lazarus 2.2 fixes branch.

Release notes can be found here.

Internal Merge requests for 3.6

Open Merge requests

Submitted by others / waiting for sign off by team member

Submitted by developer / committer and waiting for testing (do not commit yet)

Merge conflicts

Submitted by developer / committer, tested, waiting to be merged

Processed Merge requests

Fixes for 3.4 (merged)

Fixes for 3.2 (merged)

.

Fixes for 3.0 (merged)

Fixes for 3.0RC2 (merged)

Roadmap to 3.0

The release process will consist of the following steps.

This is the start of the stabilization process before a new Lazarus release.

This will be the first Release Candidate. We would like to urge all users to test this version. The testing period is scheduled to last 2 weeks.

The testing period is scheduled to last 2 weeks.

The testing period is scheduled to last 2 weeks.

Users can download the new stable version.

Tests

Tagging release

FPCDIR=/path/to/fpc/src/trunk PATH=/path/trunk/fpc/utils/fpcm/bin/x86_64-linux/:$PATH ./tools/updatemakefiles

git status

Other branches


From the Free Pascal wiki, page "Lazarus 3.0 fixes branch", as it stood on 2024-05-25 after a change by Maxim, 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.