Box-Admins October 2022

box-admins@lists.squeakfoundation.org

3 participants
3 discussions

Re: [Box-Admins] [squeak-dev] Should I put my unofficial V3 versions of Squeak 5.2 and 5.3 on files.squeak.org?
by David T. Lewis 23 Dec '22

23 Dec '22

Moving this to box-admins for assistance. I have a couple of images that I would like to preserve for posterity on files.squeak.org. They can go in a new folder under "various_images" files.squeak.org/various_images/squeak_V3_images/ Can someone on box-admins help me make this happen? I do not have access to the server but I can put the files out on a google drive if that works. I zipped up the files and put them here: https://drive.google.com/file/d/1wUZa4IHEkaTqzgwR3K1Wcwa9ckb7iVo2/view?usp=… Thanks, Dave On Sat, Jul 25, 2020 at 10:35:22AM -0700, tim Rowledge wrote: > Hard to think of any reason *not* to have them available. > > > On 2020-07-25, at 10:04 AM, David T. Lewis <lewis(a)mail.msen.com> wrote: > > > > A couple of years ago, I put a copy of a Squeak 5.2 image in V3 object > > memory format on the squeakvm.org server, and I linked to it from the > > project page at http://www.squeaksource.com/TrunkUpdateStreamV3. That link > > has gone dead, and I think I recall someone noticing it a recently. > > > > I still have the files, should I put them somewhere on files.squeak.org? > > I was thinking of putting them under the "various_images" folder: > > > > files.squeak.org/various_images/squeak_V3_images/ > > > > I also have a V3 image that is up to date with the Squeak 5.3 release, > > so I could put that on line as well. > > > > These images will run under an up-to-date interpreter VM or a Cog VM. They > > may be of interest to people doing VM work, benchmarking, or as a reference > > to understand the image-side differences between Spur and V3. > > > > Dave > > > > > > > tim > -- > tim Rowledge; tim(a)rowledge.org; http://www.rowledge.org/tim > How was Thomas J. Watson buried? 9 edge down. > > >

3 6

Re: [Box-Admins] [squeak-dev] Request to manually move the following SqueakSource versions
by Chris Muller 09 Oct '22

09 Oct '22

Hi Christoph, > unfortunately, I have already uploaded Regex-Core-ct.78 which merges Regex-Core-ct.74, > i.e., references it as an ancestor. I only noticed afterward that this > version has an incorrect encoding. So we seem to have two options: > > > > 1. Move Regex-Core-ct.74 to the Trunk indeed and hope that it won't > make any further problems in the future. (You can still view it from the > image, just not from source.squeak.org.) > 2. Remove Regex-Core-ct.78 from the trunk (move it to treated) and > create a new merge commit that excludes Regex-Core-ct.74. But I don't know > how this will influence the update stream and the images of people who have > already installed the latest updates. > > Option 2. Make a new .74 as .79 with the correct encoding. Then make a .80 that merges it all together. We will get rid of .74 and .78. If you're worried about development images of an early alpha, then add a postScript to the .80 that fixes their MCWorkingCopy's ancestry (by removing .74 and .78). And, Christoph, _please_ understand the cost/benefit balance when cultivating our Monticello model. Remember what is stored where, and how, and accordingly *keep the commit notes as close to one sentence as possible*! Look at Marcel's commit notes as a guide. Please write your implementation notes and examples *in the code*, and NOT in the commit notes. .74 is a tome of text that would've forever lived in everyone's images, never to be read again after next week. And, please do NOT copy-and-paste the descriptions of the merged versions into the new .80! > I'm sorry for the trouble. I don't know what is the best option ... What > do you think? > Thank you so much for all the great work you do, and please forgive me for nit picking about lengthy commit notes. I really do think it's important, or I wouldn't. Best, Chris

3 2

Re: [Box-Admins] [squeak-dev] Request to manually move the following SqueakSource versions
by Chris Muller 07 Oct '22

07 Oct '22

May we not move 74 to trunk like that? Would you please remake a new version in the correct encoding (utf8, I presume)? Then, resend the full list of what you want where concisely (so I don't have to look at multiple emails) and I will take care of all of them at once. On Thu, Oct 6, 2022 at 8:27 AM Thiede, Christoph < Christoph.Thiede(a)student.hpi.uni-potsdam.de> wrote: > Hi all, dear SqueakSource admins, > > > the following inbox versions need to be moved from the inbox, but I cannot > do this myself because the details page in the web interface won't load > (presumably due to an encoding error): > > > please move to the treated inbox: Regex-Core-ct.68, Regex-Core-ct.71 > please move to the trunk: Regex-Core-ct.74 > > Could someone do this manually from the backend, please? I will take care > not to add any non-ascii characters to a Monticello version's description > again in the future ... > > > Best, > > Christoph > >

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Box-Admins October 2022