Assigned
Status Update
No update yet.
Comments
be...@gmail.com
Hello,
Thank you for reaching out to us!
This issue seems to be outside of the scope of Issue Tracker. This Issue Tracker is a forum for end users to report bugs and request features on Google Cloud products. Please go through
I recommend you to
For now, I'm going to close this thread which will no longer be monitored. In case you want to report a new issue, please do not hesitate to create a new Issue Tracker describing your issue.
Thank you!
jo...@google.com
Sounds like a fine idea to me. It helps us out too, by letting us stage new appserver
binaries and get feedback from the community before deploying them everywhere. The
great insight in this feature request is the idea of letting individual apps opt-in
to run on staging servers. So yeah, sounds good to me. Accepted.
binaries and get feedback from the community before deploying them everywhere. The
great insight in this feature request is the idea of letting individual apps opt-in
to run on staging servers. So yeah, sounds good to me. Accepted.
Description
Among them are app-engine-patch, GAE Helper and others. Even if GAE team
intentionally try to avoid including libraries in the core AE project,
functionality these libraries deliver must be either reimplemented in each
end-project or be accumulated at some intermediate tier (app-engine-patch,
GAE Helper, Gaebar, etc.)
So, indirectly, these applications become a part of AE project. The
volunteers supporting them enlarge AE team, volunteers' efforts multiply AE
team efforts.
But from one GAE release to another intermediate tier breaks. It needs to
be fixed, tweaked or enhanced. In the meantime, intermediate application
and each one which depends on it is broken. This is not a pleasant experience.
May you consider some form of staging server, where intermediate
application could be tested PRIOR to AE service release? So if something
went wrong, developers would have a chance to fix before it would have an
impact on dependent applications? This staging could be as simple as
or as complete as subscription-based latest build of development server
deliver. This is not well-known successful practice, but probably you could
propose a better option?