Plan "Off-We-Go" - Proposition for a Version v2.11.0-alpha #1046
Replies: 4 comments 4 replies
-
|
The Issue lists in both the LuxCore and BlendLuxCore repositories have been filtered and where possible updated over the course of the last year, so action items can be picked primarily from those lists. For BlendLuxCore, I had picked a bunch of Issues that I deemed possible to tackle in the near future and collected them in this project: I have a few assigned to myself already, and will revise again in the next days. I also propose that we open a second discussion dedicated to checklists again, like we did for v2.10 here: |
Beta Was this translation helpful? Give feedback.
-
Proposed scope for a
|
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Update: |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Proposition to release a new version v2.11.0
It seems to be time to consider a new version, which will allow us to consolidate the developments made so far in LuxCoreDeps, LuxCore and BlendLuxCore.
We should yet precisely determine the complete trajectory to 2.11.0 (alpha, beta, release candidates and so on), but at least we all agree to start with a
v2.11.0-alphain December 2025.The first purpose of this discussion is to define the scope of this alpha version and the tasks that remain to be completed in order to achieve this scope.
The second purpose is to describe the whole steps to v2.11.0, starting with v2.11.0-alpha.
Beta Was this translation helpful? Give feedback.
All reactions