Starting a new version of LuxCoreRender - 2.10

[howetuft]

New Version Proposal: "2.10"

Purpose:

• Technical version to upgrade dependencies and build system, according to the guidelines outlined in “Back on Track” discussion.
• No functional changes. (not manageable while modifying build system)
• Bug fixing allowed

Target Version Number: 2.10

Rationale:

• Major: In the absence of functional evolutions, the API should not change and we should keep the major version at 2.
• Minor: The last known minor version is 2.9a1.

Development Branch Name: for_2.10

Rationale:

• LuxCore development branches are named for_X.Y.

Fork Base: luxcorerender-v2.9alpha1

Rationale:

• Last known version of Lux

For your comments...

[CodeFHD]

My opinion:

• Agree on purpose secion
• Agree on new version number
• Accept branch name. Just for the sake of commenting on rationale: I would not see a need to adhere to an old convention since this only affects few developers (for whom this is no issue) and normal users will not notice this. (I have no own alternative suggestions so I don't actually care)
• Regarding "fork base": Seems ok. Again jsut for completeness without expecting issues: I assume the for_blender_4.2_wheels branch is already a direct continuation and already counts into this?

[howetuft]

Thank you very much for your answer!

Accept branch name. Just for the sake of commenting on rationale: I would not see a need to adhere to an old convention since this only affects few developers (for whom this is no issue) and normal users will not notice this. (I have no own alternative suggestions so I don't actually care)

Yes, the name is arbitrary and unimportant in itself, but it's just to write here that the story restarts in for_v2.10 and that this is now the main development branch, to avoid the proliferation of new “dev” branches at this stage, or at least make sure they track for_v2.10.

Regarding "fork base": Seems ok. Again jsut for completeness without expecting issues: I assume the for_blender_4.2_wheels branch is already a direct continuation and already counts into this?

Exact, and I should have mentioned it: the wheels used in for_blender_4.2_wheels are based on luxcorerender-v2.9alpha1(with a bunch of patches, however).

I'll fork the branch this week-end.

[CodeFHD]

Proposal:
Rename the BlendLuxCore branch "for_blender_4.2_wheels" to "for_v2.10" as well for consistency, as well as making it a little easier to type in the console.

[howetuft]

You're right, but shouldn't we rather fork for_v2.10 and keep for_blender_4.2_wheels as-is, as this is the current "stable" version?

[CodeFHD]

Forking is probably cleaner anyways so fine with me.

Regarding latest stable, I would suggest to make another 2.9a4 release with the imagepipeline fix just pushed, as well as the BLC_DEV_MODE work (which I am ready to push). Reasons are a) to have the working imagepipeline again and b) to include the update of not downloaduing the wheel everytime incl. yanked wheels.

(P.S.: After v2.10 is done I suggest also to clean out all the old branches, but that can wait.)

[howetuft]

I agree with all your points.

[CodeFHD]

Done.

On my side, building and installing the for_blender_4.2_wheels branch succeeded.
If you can confirm, you could do the 2.9a4 release as you see fit.

A new for_v2.10 branch has been created including a first commit to solve an open issue.

I would create a forum post for this, and the environment-variable-mechanisms, as outlined in my restart post there

[howetuft]

OK, thank you, I'll try it later!

[CodeFHD]

@howetuft I would suggest we can close this one as well, since the branches were created as discussed and have by now been merged?

[howetuft]

Yes, we can... and we must, as now we all want to open 2.11, don't we?