Why don't you use the internal version number as a deployment version string? Maybe you have to use a different separator character instead of the '.' Maybe 'b1_2_0' would show up full in the console.
Maybe you can let the version control tool fill in the "deployment version number" with a field code to equal the "internal version number" in the app.yaml file. And then only upload code that is freshly checked out from the repository and marked with the internal version number. 2010/6/18 Jeff Schwartz <[email protected]>: > Hi Nick, > > Thanks for your quick response. As the current version number only applies > to deployment there is no way to actually view the app's internal version > number in the console. For example, my app at i-emote.appspot.com is still > in beta. It's internal version number is b1.2.0. There is no way to see that > in the console. The console only shows its deployment version number which > is 1. > > What I am requesting is to allow for the app's internal version number to be > included in the console. It would have no relevance to the deployment number > and it would be meta data that would identify its internal version number to > the developer. It would be uploaded along with the app itself. It could be a > parameter in the app's configuration file and the Eclipse plugin could allow > for its data entry. > > I believe that being able to include and see the internal version number in > the console would be a great benefit for all developers, especially if more > than 1 is working on the same application. > > I hope I have been able to provide clarification to my original request. > > Sincerely, > Jeff -- 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.
