2 replies to this topic

[smiley]

I think that it's time for Winbuilder to use different versioning . What i mean is to make version numbers for the main program AND for the scripts to be like x.x.x and not xxx.

For example when someone has a script with version 005 and want to make some bug fix he has to change the version to 006 ( meaning that he has done changes ) or letting the same.With the new versioning he will change the 5.0.0 to 5.0.1 !

Another example: in the two last packages of winbuilder , Nuno needed to publish a new fixed package with the same version number.With the new versioning it can be 50.0.1 or 0.50.1 ( still don't which of theese it is)

But i have a problem: What version is Winbuilder?
It can be :
3.3.1 (The first number is Batcher->OpenBuilder->Winbuilder, the second means the third version after winbuilder released and the third means the fix) or 50.0.1 or 0.50.1

What do you think?

[Brito]

But i have a problem: What version is Winbuilder?
It can be :
3.3.1 (The first number is Batcher->OpenBuilder->Winbuilder, the second means the third version after winbuilder released and the third means the fix) or 50.0.1 or 0.50.1

Winbuilder is version 0.5.0 (build 050), I also agree with a versioning system and it's not to difficult to add the comma support. I just prefer to release the main application as builds instead of versions - since each has significant changes compared to the previous one released.

I think you'll like the next beta on this matter..

[pscEx]

I'm preparing to expand my 'Upload-Area-Tools' to change all scripts to new version.

Peter