A temporary redirect sounds good to me. You'll probably want to update the image when 4.6 gets released, but you won't be able to do that from an empty repository (nor from a repo filled with the packages of the 4.6 releease). Once all the images are updated (I expect only a few of them by that time), we can create the repository for 4.6 and remove the redirect.
Levente
On Mon, 20 Apr 2015, Chris Muller wrote:
Hi Tobias, only admin has access to create new projects at source.squeak.org, but I am not an admin. I have no issues if you want to redirect squeak46 to trunk temporarily. I'm also okay if we would like to go ahead and get our squeak46 repository created.
Levente is the box-admins team leader, I'm cc'ing that list in case he has any input.
On Mon, Apr 20, 2015 at 4:47 AM, Pape, Tobias Tobias.Pape@hpi.de wrote:
Hi Chris
I got a question for you as the release manager. Within the next days, I have to prepare a Squeak distribution for our local lecture work. I want to base the whole thing on the upcoming 4.6 but for reasons, I cannot wait to prepare the image. My idea is to start with Trunk as of today, but fix the update url of the resulting image to that of 4.6, probably
http://source.squeak.org/squeak46. This repo does not exist yet. Would it be possible to a) make a temporary redirect http://source.squeak.org/squeak46 -> http://source.squeak.org/trunk until 4.6 is there (preferred, I could do that on the nginx site) or b) make an yet empty http://source.squeak.org/squeak46 ?
Best -Tobias
-- Tobias Pape Research School on Service-Oriented Systems Engineering Software Architecture Group | http://www.hpi.uni-potsdam.de/swa/
Hasso-Plattner-Institut für Softwaresystemtechnik GmbH | Universität Potsdam Prof.-Dr.-Helmert-Str. 2-3, D-14482 Potsdam, Germany Amtsgericht Potsdam, HRB 12184 | Geschäftsführung: Prof. Dr. Christoph Meinel