Warning: Can't synchronize with repository "(default)" (Unsupported version control system "svn": No module named svn). Look in the Trac log for more information.

Ticket #1741 (closed task: fixed)

Opened 11 years ago

Last modified 11 years ago

tgsetup.py should be moved ino the TurbuGears branch it installs in the repository

Reported by: Chris Arndt Owned by: Chris Arndt
Priority: normal Milestone: 1.1
Component: Installation Version: 1.0.4.4
Severity: normal Keywords: website, tgsetup
Cc:

Description

Currently tgsetup.py lives in source:website/download/tgsetup.py. Everytime a new TG version is released, the script is adapted and the old version overwritten.

We should move the script into the branch it installs instead, so it will be tagged with the rest of the release files. This will make it easier to check out the tgsetup.py script for given release.

Then we must either adapt the release procedures to copy the script to the right place in the download section on the website or use URL rewriting to point to the script in the tagged release in the repository directly.

Change History

comment:1 Changed 11 years ago by faide

  • Milestone changed from 1.1 to 1.1.1

comment:2 Changed 11 years ago by Chris Arndt

  • Owner changed from anonymous to Chris Arndt

comment:3 Changed 11 years ago by Chris Arndt

  • Status changed from new to assigned

comment:4 Changed 11 years ago by faide

  • Milestone changed from 1.6 to 1.5

comment:5 Changed 11 years ago by Chris Arndt

  • Status changed from assigned to closed
  • Resolution set to fixed
  • Milestone changed from 1.5 to 1.1

tgsetup.py was moved into the 1.0 branch in r5468 and to the 1.1 branch in r5466.

I set up a redirect for the  tgsetup.py download URL to point to the file in the SVN repository. This needs to be changed for every new release. I updated the  ReleaseHowto with instructions for this.

There is also a redirect for the  tgsetup-betaversion.py script, which points to the tgsetup.py file in the 1.1 branch.

For 1.1 this is an intermediate solution, since we want to use the tgsetupng.py script for 1.1 and going forward as soon as we have the necessary EggBasket infrastructure set up.

Note: See TracTickets for help on using tickets.