Baseline version?

> Date: Sun, 19 Jul 2015 23:01:22 +0000
> From: "H. Hirzel" <[hidden email]>
> To: Discussion of Cuis Smalltalk <[hidden email]>
> Subject: [Cuis] Baseline version?
> Message-ID:
>    <[hidden email]>
> Content-Type: text/plain; charset=UTF-8
>
>> On 7/19/15, Ken.Dickey <[hidden email]> wrote:
>> On Sun, 19 Jul 2015 11:20:19 -0300
> ....
>> I'd like to propose a simpler model based on the Smalltalk Way.
>>
>> We take any stable revision, call it a version, give it a Baseline Version
>> Number (could be just the development version number).
>
> I'd like to suggest to label just the current version as a "baseline".
>
> It would not need a long description, just a few keywords regarding
> major changes like the addition of the FileMan package with a
> reference to the description of it.
>
> The last one
> http://www.jvuletich.org/Cuis/CuisReleaseNotes.html
>
> had
>
> New in Cuis 4.2 (released July 25, 2013)
>
>    Packages now have dependencies
>
>    Package loading greatly enhanced
>
>    Moved non-essential stuff to optional packages. Cuis is now below
> 500 classes and 100kLOC. Reduction was about 25%
>
>    Many bugfixes, and minor enhancements and cleanup
>
>
> So this one would have
>
> New in Cuis 4.3 (released July 25, 2015)
>
>     Many bugfixes, and minor enhancements and cleanup
>
>     Addition of FileMan
>
>    .....................
>
>    .......................
>
>
>    .....................
>
>    .......................
>
>
>
> And then after testing various packages on it
> another baseline at the end of the year with a release document.
>
> New in Cuis 4.4 (released December 31, 2015)
>
>     Many bugfixes, and minor enhancements and cleanup
>
>    .....................
>
>    .....................
>
>    .......................
>
>
>    .....................
>
>    .......................
>
>    .....................
>
>    .......................
>
>
> More text as we will be more aware of the changes.
>
>
>
>> Each Baseline
>> Release has a release document which describes major changes since the
>> previous baseline.  This document is a light-weight description.
>>
>> Each baseline release starts a new fork.  The only changes to the particular
>> baseline release are bug fixes.
>>
>> Nice users test their packages and likewise fork a Package Release which
>> matches a Baseline Release.  This fork also only changes with bug fixes, and
>> only in synch with its particular baseline.  Baseline packages Feature the
>> baseline release.
>>
>> So we forge ahead as usual, once in a while we say "enough has changed that
>> we should re-baseline", do a new Baseline Release, test and release our
>> Package Releases, then again move on forward.
>>
>> Anyone can now pick any baseline release, require any associated packages,
>> and ship/demo without fear.
>>
>> Anyone with the time, energy, and interest can document baseline APIs to
>> whatever level they feel comfortable.
>>
>> Anyone can forge on ahead with the latest revision(s) with the usual "here
>> be dragons, but also gold".
>>
>> $0.02
>> -KenD
>>
>> _______________________________________________
>> Cuis mailing list
>> [hidden email]
>> http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org
>
>

> Craig Latta has a nice write up about his decent looking versioning system
> for Spoon: http://netjam.org/versions/
>
> Ken G. Brown
>
>> Date: Sun, 19 Jul 2015 23:01:22 +0000
>> From: "H. Hirzel" <[hidden email]>
>> To: Discussion of Cuis Smalltalk <[hidden email]>
>> Subject: [Cuis] Baseline version?
>> Message-ID:
>>    <[hidden email]>
>> Content-Type: text/plain; charset=UTF-8
>>
>>> On 7/19/15, Ken.Dickey <[hidden email]> wrote:
>>> On Sun, 19 Jul 2015 11:20:19 -0300
>> ....
>>> I'd like to propose a simpler model based on the Smalltalk Way.
>>>
>>> We take any stable revision, call it a version, give it a Baseline
>>> Version
>>> Number (could be just the development version number).
>>
>> I'd like to suggest to label just the current version as a "baseline".
>>
>> It would not need a long description, just a few keywords regarding
>> major changes like the addition of the FileMan package with a
>> reference to the description of it.
>>
>> The last one
>> http://www.jvuletich.org/Cuis/CuisReleaseNotes.html
>>
>> had
>>
>> New in Cuis 4.2 (released July 25, 2013)
>>
>>    Packages now have dependencies
>>
>>    Package loading greatly enhanced
>>
>>    Moved non-essential stuff to optional packages. Cuis is now below
>> 500 classes and 100kLOC. Reduction was about 25%
>>
>>    Many bugfixes, and minor enhancements and cleanup
>>
>>
>> So this one would have
>>
>> New in Cuis 4.3 (released July 25, 2015)
>>
>>     Many bugfixes, and minor enhancements and cleanup
>>
>>     Addition of FileMan
>>
>>    .....................
>>
>>    .......................
>>
>>
>>    .....................
>>
>>    .......................
>>
>>
>>
>> And then after testing various packages on it
>> another baseline at the end of the year with a release document.
>>
>> New in Cuis 4.4 (released December 31, 2015)
>>
>>     Many bugfixes, and minor enhancements and cleanup
>>
>>    .....................
>>
>>    .....................
>>
>>    .......................
>>
>>
>>    .....................
>>
>>    .......................
>>
>>    .....................
>>
>>    .......................
>>
>>
>> More text as we will be more aware of the changes.
>>
>>
>>
>>> Each Baseline
>>> Release has a release document which describes major changes since the
>>> previous baseline.  This document is a light-weight description.
>>>
>>> Each baseline release starts a new fork.  The only changes to the
>>> particular
>>> baseline release are bug fixes.
>>>
>>> Nice users test their packages and likewise fork a Package Release which
>>> matches a Baseline Release.  This fork also only changes with bug fixes,
>>> and
>>> only in synch with its particular baseline.  Baseline packages Feature
>>> the
>>> baseline release.
>>>
>>> So we forge ahead as usual, once in a while we say "enough has changed
>>> that
>>> we should re-baseline", do a new Baseline Release, test and release our
>>> Package Releases, then again move on forward.
>>>
>>> Anyone can now pick any baseline release, require any associated
>>> packages,
>>> and ship/demo without fear.
>>>
>>> Anyone with the time, energy, and interest can document baseline APIs to
>>> whatever level they feel comfortable.
>>>
>>> Anyone can forge on ahead with the latest revision(s) with the usual
>>> "here
>>> be dragons, but also gold".
>>>
>>> $0.02
>>> -KenD
>>>
>>> _______________________________________________
>>> Cuis mailing list
>>> [hidden email]
>>> http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org
>>
>>
>
> _______________________________________________
> Cuis mailing list
> [hidden email]
> http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org
>