small request :) Tweet

[cpember]

please bear with me on this one, heh

its not an engine feature, more of an organizational request

versioning....

is there a way to have Octane follow a normal versioning system?

for example,
1.0.0.0 would be version 1, THE major release.
1.0.2.46 would be the current beta version we have
just say you add another new feature like moblur, but it still follows under 1.xx, but it's more than a bugfix or utility build, then you could have
1.1.x.x, etc and so on... nice part of this is, you could end up with, in our current build's case:
1.0.2.945678 for a build if you like.. The point is, its always a number, and always up. You can add the beta to it if you like, but i'd assume unless its a full x or a x.x point release build that it IS beta.

anyways, just a request, makes for keeping archived builds organized locally easier to

cheers!



Im finding it difficult to quickly see if there's a new version of octane out because of the "1.0 beta 2.45 pre" and "1.0b beta 2.XX" style versioning that's going on atm.. When I increment a file version, there's never any text in the name at all.. if it's a new build, its a new version number, period

[abstrax]

please bear with me on this one, heh

its not an engine feature, more of an organizational request

versioning....

is there a way to have Octane follow a normal versioning system?

for example,
1.0.0.0 would be version 1, THE major release.
1.0.2.46 would be the current beta version we have
just say you add another new feature like moblur, but it still follows under 1.xx, but it's more than a bugfix or utility build, then you could have
1.1.x.x, etc and so on... nice part of this is, you could end up with, in our current build's case:
1.0.2.945678 for a build if you like.. The point is, its always a number, and always up. You can add the beta to it if you like, but i'd assume unless its a full x or a x.x point release build that it IS beta.

anyways, just a request, makes for keeping archived builds organized locally easier to

cheers!

Im finding it difficult to quickly see if there's a new version of octane out because of the "1.0 beta 2.45 pre" and "1.0b beta 2.XX" style versioning that's going on atm.. When I increment a file version, there's never any text in the name at all.. if it's a new build, its a new version number, period

I know The problem is, that we haven't released the final version yet, which means the current version number is actually something more like 0.8.something or 0.9.something . I guess, the scope of OctaneRender 1.0 final has changed tremendously from what was originally anticipated, hence the versioning confusion. I will pass your request on to Radiance. The next release would then be 1.0.2.50(beta) instead of 1.025 beta2.50..., which I personally prefer, too.

[mib2berlin]

Hi, i am also always struggle with the revision numbers.
Whats about 0.9250 and 0.935rc and then maybe 0.935 and so forth.
The "problems" start again if refractive reach 1.0, the you have to go to 2.0.250 or similar.
I hear the questions: "Have we pay now for the upgrade to Version 2?"

Cheers mib

[abstrax]

Hi, i am also always struggle with the revision numbers.
Whats about 0.9250 and 0.935rc and then maybe 0.935 and so forth.
The "problems" start again if refractive reach 1.0, the you have to go to 2.0.250 or similar.
I hear the questions: "Have we pay now for the upgrade to Version 2?"

Cheers mib

I reckon, after 1.0final has been released, we will then adapt to a proper versioning scheme. Like 1.1.something, 1.2.something. The jump to version 2.0 will then be an upgrade, you have to pay for.

Cheers,
Marcus

[cpember]

I know The problem is, that we haven't released the final version yet, which means the current version number is actually something more like 0.8.something or 0.9.something . I guess, the scope of OctaneRender 1.0 final has changed tremendously from what was originally anticipated, hence the versioning confusion. I will pass your request on to Radiance. The next release would then be 1.0.2.50(beta) instead of 1.025 beta2.50..., which I personally prefer, too.

hey I'd totally be down with a:

version 0.9.2.50 that leaves TONS of versions before 1.0.0.0

its just a sanity check for me heh

tks for reply tho

cp