Dear All,
having discovered that we lack concensus... here goes with my idea.
I venture to suggest that every release team performs certain functions...
1. Harvesting Fixes
2. Removing Deprecated Stuff
3. Loading the latest and greatest packages
4. Producing some documentation for workspaces etc.
My plan is to take each potential activity as a sub-project, whose
results generate either a script on installer.pbwiki.com or a Sake/Task.
So to generate a release candidate for testing we run the script end to
end assembling all of the parts for example.
3.10 + MinorFixes + PackageUpgrades + Clean.
This produces a cantidate for 3.11, well at least the proposed content
for 3.11, we then look at how to deliver it using the new tools we are
developing.
Option 1. Run the script using using DS to record all of the changes
made to the image, then generate a cs from that which can be placed upon
the update stream.
Option 2. Save all packages from the prototype image to MC.
Generate 3.11 by taking 3.10 and loading in all the latest packages from
MC. (requires atomic loading)
Having done this...
3.12 becomes 3.11 + MinorFixes + PackageUpgrades + Clean
and we go around again every 6 months or so.
Keith
I wanted to make an "easy" way to make tests unloadable and loadable. At
present we have two conventions in the image, and I want to try and
simplify.
The first convention is to have categories suffixed "Tests", or "Testing"
e.g. System-Event Notification-Tests
The second is to have categories such as "KernelTests" or "NetworkTests".
I would like to standardize on the first more commonly use convention,
and make supporting tools available to everyone.
To this end I have updated PackageInfo so that packages called
Kernel.impl and Kernel.test will save the impementation and the tests
separately.
The following reorganization is suggested:
http://installer.pbwiki.com/CleanReorganize-Squeak3:10
Having made this reorganization tests can be removed using
Installer unload: '*.tests'.
comments requested.
Keith
p.s. the Clean Script is comming along nicely
http://installer.pbwiki.com/Clean-Squeak3%3A10
Klaus D. Witzel wrote:
> On Thu, 29 May 2008 18:01:53 +0200, Keith Hodges wrote:
>
>> Torsten Bergmann wrote:
>>> The latest Squeak3.10.1-7175-basic.zip image from
>>> http://ftp.squeak.org/current_stable/
>>> also left out the patch to make FFI usable in 3.10:
>>>
>>> http://bugs.squeak.org/view.php?id=6980
>>>
>>> Thx
>>> Torsten
>>>
>> I added the above patch to
>> http://installer.pbwiki.com/MinorFixesUnstable-Squeak3%3A10
>>
>> All of the listed patches can be loaded using
>>
>> Installer install: 'LatestUnstable'.
>>
>> We still need to establish a "gate" process for moving patches from
>> Unstable to Stable. Those patches listed on the Stable page would be
>> the ones that are loaded by: Installer install: 'Latest'. These are
>> considered to be the fixes that will be included in 3.11
>>
>> We could have a "vote for approval" approach, a "vote for
>> disapproval" approach or a "vote for suspicion" approach.
>
> This looks +1 to me; only one thing: can the release team (harvesting
> team?) perhaps offer a recommendation on that page, the default for
> what will happen after the two weeks ?
>
> /Klaus
As yet the "release team" as listed by matthew is fairly informal and so
I would not expect a formal response. I am attempting to move things
forward a little, and so will accept any recommendations anyone cares to
make.
Matthew and I hope/expect that 3.11 will be a derivative of this work,
but not everyone agrees with us
best regards
Keith
Klaus D. Witzel wrote:
> Cedrick, Nicolas,
>
> I will not be around from Wednesday on for two weeks. Have you seen
> Keith's message about
>
> - http://installer.pbwiki.com/MinorFixesUnstable-Squeak3%3A10
>
> where he sets a deadline of two weeks. If one of you could add a test
> before that (from the material discussed) then perhaps #6937 could go
> for 3.11?
>
> /Klaus
>
>> A NOTE has been added to this issue.
>> ======================================================================
>> http://bugs.squeak.org/view.php?id=6937
>> ======================================================================
I have added this fix to FixesMinorUnstable, we how have 44 fixes in the
candidate list
Keith