microsoft / microsoft/mimalloc

Question: state of 3.0 / 3.1 branches

Open
#1,170 11 comments 17 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
13.4k
Forks
1.2k
Avg merge
4d 45m
Merged PRs (30d)
13

Description

Background:
We are using mimalloc 2 for some time under Windows, and it works great, except for a problem with large memory allocations after version 2.1.7. This may have been by design, and is not the issue here - but the problem is gone in the dev3 branch, so we want to switch to version 3 ASAP.

Question:
There are the 3.0 and 3.1 branches, both are actively developed, and the release notes indicate that 3.1.5 is still beta, while there are no release notes for 3.0.10 (the last ones are for 3.0.3, which also stated it as beta). The question is: is the 3.0 branch the stable (or LTS) branch? What is it's state, it is still considered beta? What is the difference between the 3.0 and 3.1 releases, and which one is better suited for production?

Thanks!

(creating a question issue, as there are no discussions available)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the 3.0 and 3.1 branches, their release notes, and the dev3 branch referenced in the issue. The work is done when the branch stability, beta status, release differences, and production recommendation are clearly documented or answered.

Written by the indexing model from the issue text.

Assessment

Domain
release
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.