Cool thanks. I've done that many times myself. Actually, it helps to use a release process that checks out a fresh copy of svn in a temporary directory and builds the release files from there, but you're undoubtedly aware of that.
-Adam On Sep 16, 11:50 am, "Marzia Niccolai" <[EMAIL PROTECTED]> wrote: > Hi Adam, > > My bad, I forgot to SVN add the new files, I'll do this shortly. > > -Marzia > > On Tue, Sep 16, 2008 at 11:45 AM, Adam Fisk <[EMAIL PROTECTED]> wrote: > > > Woops -- meant 1.1.3 -- sorry folks! More coffee... > > > On Sep 16, 11:44 am, Adam Fisk <[EMAIL PROTECTED]> wrote: > > > The new zipserve directory only appears to be in the zip/dmg/etc > > > downloads, but not in svn. This is problematic for running with a > > > local .google_appengine directory, for example, that's designed to > > > always use the most recent version. > > > > Just a head's up. Any way the new release could get committed to svn, > > > or is there some snag there? > > > > Thanks. > > > > -Adam --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
