Tobias Pape wrote
> On 25.06.2016, at 13:05, H. Hirzel <

> hannes.hirzel@

> > wrote:
> 
>> +1 Makes sense.
>> 
>> BTW, what does Rtm stand for?
>> And how will minor maintenance releases be marked, which happen from
>> time to time?
> 
> Should be an additional digit, right?
> 
> 4.5.1 or 5.1.2, for example.
> 
> Best regards
> 	-Tobias
> 
>> 
>> As Tobias writes
>> 
>>    SystemVersion current
>> 
>> 
>> does not return an 'alpha' suffix, this should be fixed.
>> 
>> 
>> --Hannes
>> 
>> On 6/22/16, marcel.taeumel <

> Marcel.Taeumel@

> > wrote:
>>> Tobias Pape wrote
>>>> On 22.06.2016, at 11:24, marcel.taeumel <
>>> 
>>>> Marcel.Taeumel@
>>> 
>>>> > wrote:
>>>> 
>>>>> Hi there,
>>>>> 
>>>>> we have a system version: "SystemVersion current". For trunk images,
>>>>> it
>>>>> used
>>>>> to say 'Squeak4.1alpha' or something like it. Right now, it doesn't
>>>>> even
>>>>> add
>>>>> the 'alpha' suffix.
>>>>> 
>>>>> Can we change that to 'SqueakTrunk'? What would break? Right now,
>>>>> SystemVersion works with a string rather than major/minor numbers. I
>>>>> assume
>>>>> that there is some code that parses that string. Metacello does that,
>>>>> for
>>>>> example.
>>>>> Any thoughts?
>>>> 
>>>> Yes.
>>>> 
>>>> SystemVersion current  should give the following
>>>> 
>>>> for 4.6		Squeak4.6
>>>> for 5.0		Squeak5.0
>>>> for trunk	Squeak5.1alpha	(or Squeak5.1trunk if it must be, but please
>>>> Squeak{stable+1}{dev-indicator})
>>>> 
>>>> Best
>>>> 	-Tobias
>>>> 
>>>> 
>>>>> 
>>>>> Best,
>>>>> Marcel
>>> 
>>> Okay, we good improve the version number in trunk images and treat them
>>> as
>>> (Git) tags.
>>> 
>>> ...
>>> Squeak5.1alpha
>>> Squeak5.1beta
>>> Squeak5.1rc1
>>> Squeak5.1rc2
>>> Squeak5.1rtm
>>> Squeak5.2alpha
>>> Squeak6.0alpha
>>> Squeak6.0beta
>>> ...
>>> 
>>> Even if we decide to not make a minor release but a major the tag can
>>> jump.
>>> So, any suffix after the version number indicates the trunk stream.
>>> 
>>> Alpha = Open to any code submittions
>>> Beta = Feature freeze, bug fixes only
>>> Rc1...n = Some bugs fixed, next try
>>> Rtm = Full code freeze, will be the one to release
>>> 
>>> Would this work?
>>> 
>>> Best,
>>> Marcel
>>> 
>>> 
>>> 
>>> --
>>> View this message in context:
>>> http://forum.world.st/Renaming-Squeak-s-system-version-from-Squeak-alpha-to-SqueakTrunk-tp4902398p4902424.html
>>> Sent from the Squeak - Dev mailing list archive at Nabble.com.

Would it make sense to keep track of the release build number and show the
current increment in a separate way? Releases are basically branches from
Trunk. E.g.:

source.squeak.org/trunk
source.squeak.org/squeak50

At release time, the code base is identical. Then, things might get
cherry-picked from trunk into the release branch (here "squeak50"). Then,
the summative build number would be confusing because "14023" in squeak50 is
not the same as it is in trunk.

What about doing it like GitHub branches and show "number of commits your
are behind the main branch"? It could displayed like this:

"Squeak 5.0 (Build 14000 +23/-324)"

This means that the current image is a release image, created from trunk
build 14000. There were 23 fixes in this branch since then and current Trunk
is already 324 builds ahead.

What do you think?

Best,
Marcel



--
View this message in context: http://forum.world.st/Renaming-Squeak-s-system-version-from-Squeak-alpha-to-SqueakTrunk-tp4902398p4903508.html
Sent from the Squeak - Dev mailing list archive at Nabble.com.