Repository navigation
Resume updates. #1275
Description
The content of the salsa3 branch has already been merged in, but because there were no updates during the holiday, it has made no progress. It currently cannot reach its previous usability, and its performance is even worse. However, I still choose to merge it into the main branch. If you use the main branch for daily use, please switch to V0.25.1 to stay stable until the next version is released.
- Restore usability — Bring the project back to its previously usable state so that existing functionality works as expected again.
- Fix performance issues — Investigate and resolve the performance regressions introduced by the salsa3 merge.
- Resolve the large backlog of issues — Triage and address the accumulated open issues, prioritizing those that block usability and performance.
Activity
xuhuanzy commentedon Oct 8, 2026
主要有哪些错误？
ligurio commentedon Oct 8, 2026
We are integrating the analyzer and the documentation generator into Tarantool (see tarantool/tarantool#13020) and have encountered numerous shortcomings and bugs that hinder the use of these tools. As I got it right a code freeze is currently in effect (see for an example #1252 (comment)), it would be great to hear about the plans for merging changes from contributors.
Developing our platform-specific analyzer based on emmyLua-analyzer also requires integrating a few small patches; when will it be possible to do that? See a previous discussion at #1253 (comment)
Does it even make sense to make a roadmap for the project? This will make the development process more transparent and predictable.
CppCXY commentedon Oct 8, 2026
There's no plan. Once the conflicts are resolved, it can be merged right away, but the current main branch isn't in a suitable, usable state, because I broke everything from before and need to start from scratch.
lewis6991 commentedon Oct 8, 2026
Does this mean I can start raising PR's again?
CppCXY commentedon Oct 9, 2026
Yes, you can start now.