#1741: tgsetup.py should be moved ino the TurbuGears branch it installs in the
repository
------------------------------+---------------------------------------------
 Reporter:  Chris Arndt       |        Owner:  Chris Arndt
     Type:  task              |       Status:  closed     
 Priority:  normal            |    Milestone:  1.1        
Component:  Installation      |      Version:  1.0.4.4    
 Severity:  normal            |   Resolution:  fixed      
 Keywords:  website, tgsetup  |  
------------------------------+---------------------------------------------
Changes (by Chris Arndt):

  * status:  assigned => closed
  * resolution:  => fixed
  * milestone:  1.5 => 1.1

Comment:

 `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 [http://www.turbogears.org/download/tgsetup.py
 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
 [http://docs.turbogears.org/Contributing/ReleaseHowto ReleaseHowto] with
 instructions for this.

 There is also a redirect for the [http://www.turbogears.org/download
 /tgsetup-betaversion.py 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
 [source:/projects/tgsetupng tgsetupng.py] script for 1.1 and going forward
 as soon as we have
 the necessary !EggBasket infrastructure set up.

-- 
Ticket URL: <http://trac.turbogears.org/ticket/1741#comment:5>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "TurboGears Tickets" group.
This group is read-only. No posting by normal members allowed.
To unsubscribe from this group, send email to
[EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets?hl=en?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to