Thanks Michael. Usually a 'release' is accompanied by the publishing of a new image in the appropriate place (in this case
I should think). Do you plan to do that?
If so then you will either need to pass it on to the website team for placement on the FTP site (since they own the contents of the FTP site except for certain directories), or if you desire I can add your ssh key back to the website team account and you can access that account directly and add it yourself.
This makes me think of a new plan for accounts on the server related to updating the FTP site and related. I wonder if I shouldn't simply setup a new account for each release team (for example release3.8, release3.9, release3.10, etc.). Then the relevant subdirectories (like 3.8/, 3.9alpha/, 3.9beta/, etc.) would be owned by the respective release team account and so they would not have to either bother the website team for uploading or have direct access to the website team's account for the purpose. Also the ownership of the updates/ directory could pass to the current release team. Or perhaps more appropriately, since more than one release team may need access to add bugfixes to the update stream, there could be a group that has write access to the update stream and all of the appropriate release team accounts could be members of said group. Thoughts?
Ken
On Thu, 2006-08-31 at 17:55 +0200, Michael Rueger wrote:
Hi all,
posted updates and the version advance for 3.8.1, available from any regular 3.8 image.
The release has basically been sitting there for way too long.
Besides a number of fixes the biggest change is the integration of Goran's FastSocketStream as the default SocketStream.
Thanks to everybody who contributed or pointed me to fixes for this release.
If there are fixes that you would like to see in this maintenance branch of Squeak please let me know.
(Hopefully) Enjoy :-)
Michael