Re: [google-appengine] Google has fixed 30 of 707 bugs reported in the past 12 months

['Lorne Kligerman' via Google App Engine]

Hi Wilson,

There is definitely progress!  Take a look at one of our recent blog posts
.
While this is more focused on the flex environment, near the bottom you'll
find a form to signup for the alpha release of Java 8 on standard.

Cheers,
Lorne.

On Wed, Mar 1, 2017 at 11:21 AM, Wilson Kurniawan 
wrote:

> Hi Lorne,
>
> Are there further updates on Java 8 support for GAE Standard Environment?
>
> Cheers,
> WK
>
>
> On Friday, 18 November 2016 02:42:06 UTC+8, Lorne Kligerman wrote:
>>
>> Hi there folks,
>>
>> Apologies for the delayed response.  We definitely hear you in that our
>> existing public issue tracker has not been kept up to date as best as we’d
>> like.  That being said, a few comments on the original post here.
>>
>> As mentioned, many issues have been closed as duplicate, invalid, etc.
>> I’ve scanned through a bunch of these issues and they all involve a member
>> of the Cloud Support team working with the user who posted the issue.  The
>> final comment in these issues include a description of why the issue was
>> being closed with the specific status.  As well, a lot of the issues logged
>> are unique problems with customer applications and not necessarily issues
>> with the platform.
>>
>> Our Cloud Support team has been doing a great job at triaging the issues
>> as they come in.  A lot of these issues have been later overlooked as we
>> are missing a connection between our internal and external system.
>>
>> There are plans underway to migrate the public issue tracker to a new
>> system.  In preparation we will soon be doing a bankruptcy of sorts, on
>> issues that are quite old and have not been modified in some time.  We’ll
>> post full details to this group in advance.  Once the new system is in
>> place we will do our best to keep the issues in good shape.
>>
>> Regarding the App Engine standard environment, there is no deprecation
>> coming.  We are excited about the updates to the App Engine flexible
>> environment that were just announced
>> ,
>> which will run alongside the standard environment.  We are committed to
>> both environments, with both providing unique advantages.  We are also
>> excited about upcoming enhancements to the standard environment that will
>> start to show up early in 2017, beginning with the Java 8 runtime.
>>
>> Cheers,
>>
>> Lorne.
>>
>>
>> On Friday, November 4, 2016 at 12:52:18 PM UTC-7, Mark Cummins wrote:
>>>
>>> I also am beginning to fear a "GAE deprecation email". Could anyone at
>>> Google give any reassurance on this? Is GAE standard going to be abandoned
>>> in favour of managed VMs (which are actually very different)?
>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Google App Engine" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/google-appengine/EFLhIU9GqjU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-appengine.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/google-appengine/22ef70ee-4e45-4d6f-ab60-
> 4cfef14f805c%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CA%2Bzk0p%2B3cnc44fL7gw1GwsL5Gz_NTYtL-t3Zx%2BqUFQ6VCbQjMw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Google has fixed 30 of 707 bugs reported in the past 12 months

[Wilson Kurniawan]

Hi Lorne,

Are there further updates on Java 8 support for GAE Standard Environment?

Cheers,
WK

On Friday, 18 November 2016 02:42:06 UTC+8, Lorne Kligerman wrote:
>
> Hi there folks,
>
> Apologies for the delayed response.  We definitely hear you in that our 
> existing public issue tracker has not been kept up to date as best as we’d 
> like.  That being said, a few comments on the original post here.
>
> As mentioned, many issues have been closed as duplicate, invalid, etc. 
>  I’ve scanned through a bunch of these issues and they all involve a member 
> of the Cloud Support team working with the user who posted the issue.  The 
> final comment in these issues include a description of why the issue was 
> being closed with the specific status.  As well, a lot of the issues logged 
> are unique problems with customer applications and not necessarily issues 
> with the platform.
>
> Our Cloud Support team has been doing a great job at triaging the issues 
> as they come in.  A lot of these issues have been later overlooked as we 
> are missing a connection between our internal and external system.
>
> There are plans underway to migrate the public issue tracker to a new 
> system.  In preparation we will soon be doing a bankruptcy of sorts, on 
> issues that are quite old and have not been modified in some time.  We’ll 
> post full details to this group in advance.  Once the new system is in 
> place we will do our best to keep the issues in good shape.
>
> Regarding the App Engine standard environment, there is no deprecation 
> coming.  We are excited about the updates to the App Engine flexible 
> environment that were just announced 
> , 
> which will run alongside the standard environment.  We are committed to 
> both environments, with both providing unique advantages.  We are also 
> excited about upcoming enhancements to the standard environment that will 
> start to show up early in 2017, beginning with the Java 8 runtime.
>
> Cheers,
>
> Lorne.
>
>
> On Friday, November 4, 2016 at 12:52:18 PM UTC-7, Mark Cummins wrote:
>>
>> I also am beginning to fear a "GAE deprecation email". Could anyone at 
>> Google give any reassurance on this? Is GAE standard going to be abandoned 
>> in favour of managed VMs (which are actually very different)?
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/22ef70ee-4e45-4d6f-ab60-4cfef14f805c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Google has fixed 30 of 707 bugs reported in the past 12 months

[Nick]

You would have received an announcement that cloud logging is moving to 
stackdriver. This introduces two pricing tiers, premium and basic. Everyone got 
a free trial of premium.

The pricing and limits are different than previously, and effectively kick in 
on the 5th of December.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/0cff9a57-c406-4d55-bbe8-607ca44e6fb2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Google has fixed 30 of 707 bugs reported in the past 12 months

[PK]

Well, technically there is no price increase, there is just a degradation of 
the logs service for apps that generate more than 5G of logs in 30 days. 
However, if one wants to maintain the same quality of service one can pay more. 
The increase, if any, varies based on how many log statements the app generates.

I looked at our main app and based on how many logs we generate every month and 
how much we pay for the service, I calculated that for us, maintaining the 30 
day window of logs would cost 30% more of what we pay now for AppEngine 
Standard. 

Like I said the increase will vary for each application, you need to look at 
your numbers. I hope this clarifies and I am sorry for any confusion.

> On Nov 26, 2016, at 1:24 PM, Renaud Tarnec  wrote:
> 
> @PK: Hi, could you please explain a bit more in detail what is the "30% price 
> hike coming on Dec 5? Working exclusively in the Standard environment, I've 
> the 
> feeling I've missed an announcement.
> 
> Thanks!
> 
> On Friday, November 25, 2016 at 8:42:14 PM UTC+1, PK wrote:
> Channels are not exotic, we have been using them heavily and is a  headache 
> for us to migrate. 
> 
> This attitude of some GAE users to only care about the features they use and 
> call the other features exotic and in the cutting block is not helpful. Keep 
> in mind that what goes around comes around and the feature you depend on will 
> be next. If you do not use a feature that gets deprecated at least stay 
> silent and thankful. After all, for many GCP users with IaaS mentality the 
> whole GAE is exotic...
> 
> If this is how GCP does business maybe they should post a Dashboard of each 
> feature and how many customers use it so we know what to stay away from..
> 
> --PK
> 
> PS btw I have been spending the thanksgiving holiday figuring out how to 
> migrate to a different log system and avoid/minimize the 30% price hike 
> coming on Dec 5. A lot of fun and good progress but I have customer features 
> to work on and would have preferred to be working on those instead. I picked 
> GAE so that I do not spend my resources doing platform work and here I am day 
> in/day out spending time rewriting and retesting things that were working. 
> 
> On Nov 25, 2016, at 7:59 AM, Kaan Soral  
> wrote:
> 
>> I agree, and I suspected you were talking about "Prospective Search", it 
>> always seemed too specific, however, "Channels" were truly unique and 
>> useful, if it was a scalable service, I would definitely use it - and I'm 
>> saddened by it's passing (I use polling heavily on one project, and have a 
>> nodejs/websocket system in another, if "Channels" bloomed, it would enrich 
>> the experience significantly)
>> 
>> As my .02 for the original post, I somehow gave up on support long ago, but 
>> it's not entirely bad either, as it is, appengine is very mature, and even 
>> if it received 0 updates for years, it would still be useful - but - indeed, 
>> receiving swift and practical technical support would've been great - this 
>> was my recent technical challenge: 
>> https://groups.google.com/forum/#!topic/google-appengine/A2_fr2L0fAY 
>>  - 
>> It's a bizarre one, when contention for one entity occurs, it's like the 
>> transaction is proceeding with a corrupt ndb system, and causing an 
>> exception that halts the execution, Instead of creating a public issue 
>> tracker issue, I ended up re-structuring my architecture so contention is 
>> less likely, it seemed like the easier option, I really didn't have the 
>> energy to go through the issue tracker process
>> 
>> On Friday, November 25, 2016 at 5:03:00 PM UTC+2, Mark Cummins wrote:
>> @Kaan Soral. Yes, we also heavily use the images service, it's invaluable 
>> and we love it. We were also using mail, although it really wasn't a big 
>> problem to move to an external service. (Though incoming is indeed more of 
>> an issue) By exotic, I mean things like Prospective Search and  
>> XMPP/Channels. I don't think too many people were really affected by those 
>> deprecations.
>> 
>> On Friday, 25 November 2016 13:38:16 UTC, Kaan Soral wrote:
>> It is what I meant, apologies if I was confusing
>> 
>> On Friday, November 25, 2016 at 3:36:14 PM UTC+2, George Bittmann wrote:
>> Where is the mail deprecation? Post a link if it's happening please. I 
>> thought they were only no longer approving requests to expand beyond the 100 
>> daily limit. Is that what you mean?
>> 
>> 
>> On Thursday, November 24, 2016 at 8:06:33 AM UTC-5, Kaan Soral wrote:
>> Hi
>> 
>> Thanks a lot for the reply again
>> 
>> For images, https://cloud.google.com/appengine/docs/python/images/ 
>>  - the 1600 resize 
>> limit started to age a bit, I'm using the images service heavily on 
>> https://geobird.com  - and considering the recent 4K, 
>> 5K resolutions, 

Re: [google-appengine] Google has fixed 30 of 707 bugs reported in the past 12 months

[Renaud Tarnec]

@PK: Hi, could you please explain a bit more in detail what is the "30% 
price hike coming on Dec 5? Working exclusively in the Standard 
environment, I've the 
feeling I've missed an announcement.

Thanks!

On Friday, November 25, 2016 at 8:42:14 PM UTC+1, PK wrote:
>
> Channels are not exotic, we have been using them heavily and is a 
>  headache for us to migrate. 
>
> This attitude of some GAE users to only care about the features they use 
> and call the other features exotic and in the cutting block is not helpful. 
> Keep in mind that what goes around comes around and the feature you depend 
> on will be next. If you do not use a feature that gets deprecated at least 
> stay silent and thankful. After all, for many GCP users with IaaS mentality 
> the whole GAE is exotic...
>
> If this is how GCP does business maybe they should post a Dashboard of 
> each feature and how many customers use it so we know what to stay away 
> from..
>
> --PK
>
> PS btw I have been spending the thanksgiving holiday figuring out how to 
> migrate to a different log system and avoid/minimize the 30% price hike 
> coming on Dec 5. A lot of fun and good progress but I have customer 
> features to work on and would have preferred to be working on those 
> instead. I picked GAE so that I do not spend my resources doing platform 
> work and here I am day in/day out spending time rewriting and retesting 
> things that were working. 
>
> On Nov 25, 2016, at 7:59 AM, Kaan Soral  
> wrote:
>
> I agree, and I suspected you were talking about "Prospective Search", it 
> always seemed too specific, however, "Channels" were truly unique and 
> useful, if it was a scalable service, I would definitely use it - and I'm 
> saddened by it's passing (I use polling heavily on one project, and have a 
> nodejs/websocket system in another, if "Channels" bloomed, it would enrich 
> the experience significantly)
>
> As my .02 for the original post, I somehow gave up on support long ago, 
> but it's not entirely bad either, as it is, appengine is very mature, and 
> even if it received 0 updates for years, it would still be useful - but - 
> indeed, receiving swift and practical technical support would've been great 
> - this was my recent technical challenge: 
> https://groups.google.com/forum/#!topic/google-appengine/A2_fr2L0fAY - 
> It's a bizarre one, when contention for one entity occurs, it's like the 
> transaction is proceeding with a corrupt ndb system, and causing an 
> exception that halts the execution, Instead of creating a public issue 
> tracker issue, I ended up re-structuring my architecture so contention is 
> less likely, it seemed like the easier option, I really didn't have the 
> energy to go through the issue tracker process
>
> On Friday, November 25, 2016 at 5:03:00 PM UTC+2, Mark Cummins wrote:
>>
>> @Kaan Soral. Yes, we also heavily use the images service, it's invaluable 
>> and we love it. We were also using mail, although it really wasn't a big 
>> problem to move to an external service. (Though incoming is indeed more of 
>> an issue) By exotic, I mean things like Prospective Search and 
>>  XMPP/Channels. I don't think too many people were really affected by those 
>> deprecations.
>>
>> On Friday, 25 November 2016 13:38:16 UTC, Kaan Soral wrote:
>>>
>>> It is what I meant, apologies if I was confusing
>>>
>>> On Friday, November 25, 2016 at 3:36:14 PM UTC+2, George Bittmann wrote:

 Where is the mail deprecation? Post a link if it's happening please. I 
 thought they were only no longer approving requests to expand beyond the 
 100 daily limit. Is that what you mean?


 On Thursday, November 24, 2016 at 8:06:33 AM UTC-5, Kaan Soral wrote:
>
> Hi
>
> Thanks a lot for the reply again
>
> For images, https://cloud.google.com/appengine/docs/python/images/ - 
> the 1600 resize limit started to age a bit, I'm using the images service 
> heavily on https://geobird.com - and considering the recent 4K, 5K 
> resolutions, even bumping the limit to 2400 would improve dynamics a lot, 
> considering it would at least cover 1080p (Current solution is to just 
> serve images with "=s0" - considering most devices have retina 
> resolutions 
> now, most images started becoming "=s0" - and a significant bandwidth is 
> wasted for clients)
>
> If we analyse the case for the images service, it provides dynamic 
> resizing at instant availability, It's an invaluable service, I love 
> appengine because it provides building blocks like these - Instead of 
> depreciating such services, it would be lovely to see new ones, for 
> example, a "videos" service, even though I'm using Zencoder for video 
> processing, if we compare it to the ease of using the images service, 
> it's 
> a heavy burden
>
> @Mark Cummins, I don't know what service you are calling exotic and 
> less-used, It 

Re: [google-appengine] Google has fixed 30 of 707 bugs reported in the past 12 months

[Thomas Baldauf]

Same here! Flex Env would have been great without the need to rewrite all the 
parts of our app that depend on GAE SDK APIs. I'm just wondering if they're 
going to deprecate it also in Standard Edition so everybody has to use the 
Google Cloud Client libraries in the future ...

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/83507f89-d79a-43a9-b7a6-1a6f62e642e1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Google has fixed 30 of 707 bugs reported in the past 12 months

[Stefano Ciccarelli]

PK you said a big truth, we used flexible environment very much, but now
that Google deprecated the compact runtimes we have to return to standard
environment.

Il giorno ven 25 nov 2016 alle 20:41 PK  ha scritto:

> Channels are not exotic, we have been using them heavily and is a
>  headache for us to migrate.
>
> This attitude of some GAE users to only care about the features they use
> and call the other features exotic and in the cutting block is not helpful.
> Keep in mind that what goes around comes around and the feature you depend
> on will be next. If you do not use a feature that gets deprecated at least
> stay silent and thankful. After all, for many GCP users with IaaS mentality
> the whole GAE is exotic...
>
> If this is how GCP does business maybe they should post a Dashboard of
> each feature and how many customers use it so we know what to stay away
> from..
>
> --PK
>
> PS btw I have been spending the thanksgiving holiday figuring out how to
> migrate to a different log system and avoid/minimize the 30% price hike
> coming on Dec 5. A lot of fun and good progress but I have customer
> features to work on and would have preferred to be working on those
> instead. I picked GAE so that I do not spend my resources doing platform
> work and here I am day in/day out spending time rewriting and retesting
> things that were working.
>
> On Nov 25, 2016, at 7:59 AM, Kaan Soral  wrote:
>
> I agree, and I suspected you were talking about "Prospective Search", it
> always seemed too specific, however, "Channels" were truly unique and
> useful, if it was a scalable service, I would definitely use it - and I'm
> saddened by it's passing (I use polling heavily on one project, and have a
> nodejs/websocket system in another, if "Channels" bloomed, it would enrich
> the experience significantly)
>
> As my .02 for the original post, I somehow gave up on support long ago,
> but it's not entirely bad either, as it is, appengine is very mature, and
> even if it received 0 updates for years, it would still be useful - but -
> indeed, receiving swift and practical technical support would've been great
> - this was my recent technical challenge:
> https://groups.google.com/forum/#!topic/google-appengine/A2_fr2L0fAY -
> It's a bizarre one, when contention for one entity occurs, it's like the
> transaction is proceeding with a corrupt ndb system, and causing an
> exception that halts the execution, Instead of creating a public issue
> tracker issue, I ended up re-structuring my architecture so contention is
> less likely, it seemed like the easier option, I really didn't have the
> energy to go through the issue tracker process
>
> On Friday, November 25, 2016 at 5:03:00 PM UTC+2, Mark Cummins wrote:
>
> @Kaan Soral. Yes, we also heavily use the images service, it's invaluable
> and we love it. We were also using mail, although it really wasn't a big
> problem to move to an external service. (Though incoming is indeed more of
> an issue) By exotic, I mean things like Prospective Search and
>  XMPP/Channels. I don't think too many people were really affected by those
> deprecations.
>
> On Friday, 25 November 2016 13:38:16 UTC, Kaan Soral wrote:
>
> It is what I meant, apologies if I was confusing
>
> On Friday, November 25, 2016 at 3:36:14 PM UTC+2, George Bittmann wrote:
>
> Where is the mail deprecation? Post a link if it's happening please. I
> thought they were only no longer approving requests to expand beyond the
> 100 daily limit. Is that what you mean?
>
>
> On Thursday, November 24, 2016 at 8:06:33 AM UTC-5, Kaan Soral wrote:
>
> Hi
>
> Thanks a lot for the reply again
>
> For images, https://cloud.google.com/appengine/docs/python/images/ - the
> 1600 resize limit started to age a bit, I'm using the images service
> heavily on https://geobird.com - and considering the recent 4K, 5K
> resolutions, even bumping the limit to 2400 would improve dynamics a lot,
> considering it would at least cover 1080p (Current solution is to just
> serve images with "=s0" - considering most devices have retina resolutions
> now, most images started becoming "=s0" - and a significant bandwidth is
> wasted for clients)
>
> If we analyse the case for the images service, it provides dynamic
> resizing at instant availability, It's an invaluable service, I love
> appengine because it provides building blocks like these - Instead of
> depreciating such services, it would be lovely to see new ones, for
> example, a "videos" service, even though I'm using Zencoder for video
> processing, if we compare it to the ease of using the images service, it's
> a heavy burden
>
> @Mark Cummins, I don't know what service you are calling exotic and
> less-used, It would be great if you could provide concrete examples,
> interacting with other app engine users, you would be amazed how each
> component is utilised and valued
> If we analyse the case for mail, I personally was using it to send mails,
> so, 

Re: [google-appengine] Google has fixed 30 of 707 bugs reported in the past 12 months

[PK]

Channels are not exotic, we have been using them heavily and is a  headache for 
us to migrate. 

This attitude of some GAE users to only care about the features they use and 
call the other features exotic and in the cutting block is not helpful. Keep in 
mind that what goes around comes around and the feature you depend on will be 
next. If you do not use a feature that gets deprecated at least stay silent and 
thankful. After all, for many GCP users with IaaS mentality the whole GAE is 
exotic...

If this is how GCP does business maybe they should post a Dashboard of each 
feature and how many customers use it so we know what to stay away from..

--PK

PS btw I have been spending the thanksgiving holiday figuring out how to 
migrate to a different log system and avoid/minimize the 30% price hike coming 
on Dec 5. A lot of fun and good progress but I have customer features to work 
on and would have preferred to be working on those instead. I picked GAE so 
that I do not spend my resources doing platform work and here I am day in/day 
out spending time rewriting and retesting things that were working. 

> On Nov 25, 2016, at 7:59 AM, Kaan Soral  wrote:
> 
> I agree, and I suspected you were talking about "Prospective Search", it 
> always seemed too specific, however, "Channels" were truly unique and useful, 
> if it was a scalable service, I would definitely use it - and I'm saddened by 
> it's passing (I use polling heavily on one project, and have a 
> nodejs/websocket system in another, if "Channels" bloomed, it would enrich 
> the experience significantly)
> 
> As my .02 for the original post, I somehow gave up on support long ago, but 
> it's not entirely bad either, as it is, appengine is very mature, and even if 
> it received 0 updates for years, it would still be useful - but - indeed, 
> receiving swift and practical technical support would've been great - this 
> was my recent technical challenge: 
> https://groups.google.com/forum/#!topic/google-appengine/A2_fr2L0fAY - It's a 
> bizarre one, when contention for one entity occurs, it's like the transaction 
> is proceeding with a corrupt ndb system, and causing an exception that halts 
> the execution, Instead of creating a public issue tracker issue, I ended up 
> re-structuring my architecture so contention is less likely, it seemed like 
> the easier option, I really didn't have the energy to go through the issue 
> tracker process
> 
>> On Friday, November 25, 2016 at 5:03:00 PM UTC+2, Mark Cummins wrote:
>> @Kaan Soral. Yes, we also heavily use the images service, it's invaluable 
>> and we love it. We were also using mail, although it really wasn't a big 
>> problem to move to an external service. (Though incoming is indeed more of 
>> an issue) By exotic, I mean things like Prospective Search and  
>> XMPP/Channels. I don't think too many people were really affected by those 
>> deprecations.
>> 
>>> On Friday, 25 November 2016 13:38:16 UTC, Kaan Soral wrote:
>>> It is what I meant, apologies if I was confusing
>>> 
 On Friday, November 25, 2016 at 3:36:14 PM UTC+2, George Bittmann wrote:
 Where is the mail deprecation? Post a link if it's happening please. I 
 thought they were only no longer approving requests to expand beyond the 
 100 daily limit. Is that what you mean?
 
 
> On Thursday, November 24, 2016 at 8:06:33 AM UTC-5, Kaan Soral wrote:
> Hi
> 
> Thanks a lot for the reply again
> 
> For images, https://cloud.google.com/appengine/docs/python/images/ - the 
> 1600 resize limit started to age a bit, I'm using the images service 
> heavily on https://geobird.com - and considering the recent 4K, 5K 
> resolutions, even bumping the limit to 2400 would improve dynamics a lot, 
> considering it would at least cover 1080p (Current solution is to just 
> serve images with "=s0" - considering most devices have retina 
> resolutions now, most images started becoming "=s0" - and a significant 
> bandwidth is wasted for clients)
> 
> If we analyse the case for the images service, it provides dynamic 
> resizing at instant availability, It's an invaluable service, I love 
> appengine because it provides building blocks like these - Instead of 
> depreciating such services, it would be lovely to see new ones, for 
> example, a "videos" service, even though I'm using Zencoder for video 
> processing, if we compare it to the ease of using the images service, 
> it's a heavy burden
> 
> @Mark Cummins, I don't know what service you are calling exotic and 
> less-used, It would be great if you could provide concrete examples, 
> interacting with other app engine users, you would be amazed how each 
> component is utilised and valued
> If we analyse the case for mail, I personally was using it to send mails, 
> so, while the deprecation was an extreme nuisance, it wasn't the end of 
> 

Re: [google-appengine] Google has fixed 30 of 707 bugs reported in the past 12 months

[Kaan Soral]

I agree, and I suspected you were talking about "Prospective Search", it 
always seemed too specific, however, "Channels" were truly unique and 
useful, if it was a scalable service, I would definitely use it - and I'm 
saddened by it's passing (I use polling heavily on one project, and have a 
nodejs/websocket system in another, if "Channels" bloomed, it would enrich 
the experience significantly)

As my .02 for the original post, I somehow gave up on support long ago, but 
it's not entirely bad either, as it is, appengine is very mature, and even 
if it received 0 updates for years, it would still be useful - but - 
indeed, receiving swift and practical technical support would've been great 
- this was my recent technical 
challenge: https://groups.google.com/forum/#!topic/google-appengine/A2_fr2L0fAY 
- It's a bizarre one, when contention for one entity occurs, it's like the 
transaction is proceeding with a corrupt ndb system, and causing an 
exception that halts the execution, Instead of creating a public issue 
tracker issue, I ended up re-structuring my architecture so contention is 
less likely, it seemed like the easier option, I really didn't have the 
energy to go through the issue tracker process

On Friday, November 25, 2016 at 5:03:00 PM UTC+2, Mark Cummins wrote:
>
> @Kaan Soral. Yes, we also heavily use the images service, it's invaluable 
> and we love it. We were also using mail, although it really wasn't a big 
> problem to move to an external service. (Though incoming is indeed more of 
> an issue) By exotic, I mean things like Prospective Search and 
>  XMPP/Channels. I don't think too many people were really affected by those 
> deprecations.
>
> On Friday, 25 November 2016 13:38:16 UTC, Kaan Soral wrote:
>>
>> It is what I meant, apologies if I was confusing
>>
>> On Friday, November 25, 2016 at 3:36:14 PM UTC+2, George Bittmann wrote:
>>>
>>> Where is the mail deprecation? Post a link if it's happening please. I 
>>> thought they were only no longer approving requests to expand beyond the 
>>> 100 daily limit. Is that what you mean?
>>>
>>>
>>> On Thursday, November 24, 2016 at 8:06:33 AM UTC-5, Kaan Soral wrote:

 Hi

 Thanks a lot for the reply again

 For images, https://cloud.google.com/appengine/docs/python/images/ - 
 the 1600 resize limit started to age a bit, I'm using the images service 
 heavily on https://geobird.com - and considering the recent 4K, 5K 
 resolutions, even bumping the limit to 2400 would improve dynamics a lot, 
 considering it would at least cover 1080p (Current solution is to just 
 serve images with "=s0" - considering most devices have retina resolutions 
 now, most images started becoming "=s0" - and a significant bandwidth is 
 wasted for clients)

 If we analyse the case for the images service, it provides dynamic 
 resizing at instant availability, It's an invaluable service, I love 
 appengine because it provides building blocks like these - Instead of 
 depreciating such services, it would be lovely to see new ones, for 
 example, a "videos" service, even though I'm using Zencoder for video 
 processing, if we compare it to the ease of using the images service, it's 
 a heavy burden

 @Mark Cummins, I don't know what service you are calling exotic and 
 less-used, It would be great if you could provide concrete examples, 
 interacting with other app engine users, you would be amazed how each 
 component is utilised and valued
 If we analyse the case for mail, I personally was using it to send 
 mails, so, while the deprecation was an extreme nuisance, it wasn't the 
 end 
 of the world, yet, communicating with others, I saw that some were using 
 apps as turnkey solutions, or, they were deploying singular apps for their 
 clients, so having a practical mail solution was crucial to them, some 
 were 
 handling incoming email, while things were simple from the outgoing email 
 perspective, for an app that handled both incoming/outgoing email, the 
 deprecation was much more worrying

 On Wednesday, November 23, 2016 at 3:28:07 AM UTC+2, Lorne Kligerman 
 wrote:
>
> Heard loud and clear on action speaking louder than words.  We have a 
> lot brewing and are excited to show it off when ready.
>
> There have been some deprecation announcements lately.  The objective 
> here is to bring App Engine in line with the rest of GCP.  This is a 
> challenging effort because of how long App Engine pre-dates the rest of 
> the 
> system.  That being said, we do have our users best interests at heart 
> and 
> we believe the future state will be a good one.  Significant improvements 
> have been made to the App Engine Admin API, which officially went GA 
> 

Re: [google-appengine] Google has fixed 30 of 707 bugs reported in the past 12 months

[Mark Cummins]

@Kaan Soral. Yes, we also heavily use the images service, it's invaluable 
and we love it. We were also using mail, although it really wasn't a big 
problem to move to an external service. (Though incoming is indeed more of 
an issue) By exotic, I mean things like Prospective Search and 
 XMPP/Channels. I don't think too many people were really affected by those 
deprecations.

On Friday, 25 November 2016 13:38:16 UTC, Kaan Soral wrote:
>
> It is what I meant, apologies if I was confusing
>
> On Friday, November 25, 2016 at 3:36:14 PM UTC+2, George Bittmann wrote:
>>
>> Where is the mail deprecation? Post a link if it's happening please. I 
>> thought they were only no longer approving requests to expand beyond the 
>> 100 daily limit. Is that what you mean?
>>
>>
>> On Thursday, November 24, 2016 at 8:06:33 AM UTC-5, Kaan Soral wrote:
>>>
>>> Hi
>>>
>>> Thanks a lot for the reply again
>>>
>>> For images, https://cloud.google.com/appengine/docs/python/images/ - 
>>> the 1600 resize limit started to age a bit, I'm using the images service 
>>> heavily on https://geobird.com - and considering the recent 4K, 5K 
>>> resolutions, even bumping the limit to 2400 would improve dynamics a lot, 
>>> considering it would at least cover 1080p (Current solution is to just 
>>> serve images with "=s0" - considering most devices have retina resolutions 
>>> now, most images started becoming "=s0" - and a significant bandwidth is 
>>> wasted for clients)
>>>
>>> If we analyse the case for the images service, it provides dynamic 
>>> resizing at instant availability, It's an invaluable service, I love 
>>> appengine because it provides building blocks like these - Instead of 
>>> depreciating such services, it would be lovely to see new ones, for 
>>> example, a "videos" service, even though I'm using Zencoder for video 
>>> processing, if we compare it to the ease of using the images service, it's 
>>> a heavy burden
>>>
>>> @Mark Cummins, I don't know what service you are calling exotic and 
>>> less-used, It would be great if you could provide concrete examples, 
>>> interacting with other app engine users, you would be amazed how each 
>>> component is utilised and valued
>>> If we analyse the case for mail, I personally was using it to send 
>>> mails, so, while the deprecation was an extreme nuisance, it wasn't the end 
>>> of the world, yet, communicating with others, I saw that some were using 
>>> apps as turnkey solutions, or, they were deploying singular apps for their 
>>> clients, so having a practical mail solution was crucial to them, some were 
>>> handling incoming email, while things were simple from the outgoing email 
>>> perspective, for an app that handled both incoming/outgoing email, the 
>>> deprecation was much more worrying
>>>
>>> On Wednesday, November 23, 2016 at 3:28:07 AM UTC+2, Lorne Kligerman 
>>> wrote:

 Heard loud and clear on action speaking louder than words.  We have a 
 lot brewing and are excited to show it off when ready.

 There have been some deprecation announcements lately.  The objective 
 here is to bring App Engine in line with the rest of GCP.  This is a 
 challenging effort because of how long App Engine pre-dates the rest of 
 the 
 system.  That being said, we do have our users best interests at heart and 
 we believe the future state will be a good one.  Significant improvements 
 have been made to the App Engine Admin API, which officially went GA 
 
  
 a couple months ago.

 Regarding mail, we are currently gathering requirements for a GCP wide 
 solution.  For images, could you give more detail on exactly which limit 
 you're running up against and the scenario?


 On Tue, Nov 22, 2016 at 2:45 PM, 'Alex (Cloud Platform Support)' via 
 Google App Engine  wrote:

> Hi Kaan,
>
> On a side note, it is possible to receive regular emails from the 
> Google Cloud Platform by following these steps:
>
>1. Access the Cloud Platform Console
>
>2. Click the “3 vertical dots” on the top-right section of the menu
>
>3. Navigate to preferences->Updates & Offers
>
>4. Set email to “On” for Feature announcements
>
> By doing this, you will receive emails about the latest feature 
> announcements on the Cloud Platform.
>
> Cheers,
>
> Alex
>
> -- 
> You received this message because you are subscribed to a topic in the 
> Google Groups "Google App Engine" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/google-appengine/EFLhIU9GqjU/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an email to 
> google-appengi...@googlegroups.com.
> To post to this 

Re: [google-appengine] Google has fixed 30 of 707 bugs reported in the past 12 months

[Kaan Soral]

It is what I meant, apologies if I was confusing

On Friday, November 25, 2016 at 3:36:14 PM UTC+2, George Bittmann wrote:
>
> Where is the mail deprecation? Post a link if it's happening please. I 
> thought they were only no longer approving requests to expand beyond the 
> 100 daily limit. Is that what you mean?
>
>
> On Thursday, November 24, 2016 at 8:06:33 AM UTC-5, Kaan Soral wrote:
>>
>> Hi
>>
>> Thanks a lot for the reply again
>>
>> For images, https://cloud.google.com/appengine/docs/python/images/ - the 
>> 1600 resize limit started to age a bit, I'm using the images service 
>> heavily on https://geobird.com - and considering the recent 4K, 5K 
>> resolutions, even bumping the limit to 2400 would improve dynamics a lot, 
>> considering it would at least cover 1080p (Current solution is to just 
>> serve images with "=s0" - considering most devices have retina resolutions 
>> now, most images started becoming "=s0" - and a significant bandwidth is 
>> wasted for clients)
>>
>> If we analyse the case for the images service, it provides dynamic 
>> resizing at instant availability, It's an invaluable service, I love 
>> appengine because it provides building blocks like these - Instead of 
>> depreciating such services, it would be lovely to see new ones, for 
>> example, a "videos" service, even though I'm using Zencoder for video 
>> processing, if we compare it to the ease of using the images service, it's 
>> a heavy burden
>>
>> @Mark Cummins, I don't know what service you are calling exotic and 
>> less-used, It would be great if you could provide concrete examples, 
>> interacting with other app engine users, you would be amazed how each 
>> component is utilised and valued
>> If we analyse the case for mail, I personally was using it to send mails, 
>> so, while the deprecation was an extreme nuisance, it wasn't the end of the 
>> world, yet, communicating with others, I saw that some were using apps as 
>> turnkey solutions, or, they were deploying singular apps for their clients, 
>> so having a practical mail solution was crucial to them, some were handling 
>> incoming email, while things were simple from the outgoing email 
>> perspective, for an app that handled both incoming/outgoing email, the 
>> deprecation was much more worrying
>>
>> On Wednesday, November 23, 2016 at 3:28:07 AM UTC+2, Lorne Kligerman 
>> wrote:
>>>
>>> Heard loud and clear on action speaking louder than words.  We have a 
>>> lot brewing and are excited to show it off when ready.
>>>
>>> There have been some deprecation announcements lately.  The objective 
>>> here is to bring App Engine in line with the rest of GCP.  This is a 
>>> challenging effort because of how long App Engine pre-dates the rest of the 
>>> system.  That being said, we do have our users best interests at heart and 
>>> we believe the future state will be a good one.  Significant improvements 
>>> have been made to the App Engine Admin API, which officially went GA 
>>> 
>>>  
>>> a couple months ago.
>>>
>>> Regarding mail, we are currently gathering requirements for a GCP wide 
>>> solution.  For images, could you give more detail on exactly which limit 
>>> you're running up against and the scenario?
>>>
>>>
>>> On Tue, Nov 22, 2016 at 2:45 PM, 'Alex (Cloud Platform Support)' via 
>>> Google App Engine  wrote:
>>>
 Hi Kaan,

 On a side note, it is possible to receive regular emails from the 
 Google Cloud Platform by following these steps:

1. Access the Cloud Platform Console

2. Click the “3 vertical dots” on the top-right section of the menu

3. Navigate to preferences->Updates & Offers

4. Set email to “On” for Feature announcements

 By doing this, you will receive emails about the latest feature 
 announcements on the Cloud Platform.

 Cheers,

 Alex

 -- 
 You received this message because you are subscribed to a topic in the 
 Google Groups "Google App Engine" group.
 To unsubscribe from this topic, visit 
 https://groups.google.com/d/topic/google-appengine/EFLhIU9GqjU/unsubscribe
 .
 To unsubscribe from this group and all its topics, send an email to 
 google-appengi...@googlegroups.com.
 To post to this group, send email to google-a...@googlegroups.com.
 Visit this group at https://groups.google.com/group/google-appengine.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/google-appengine/c37962f7-c400-44d9-9ab8-dfd3edc7ec1f%40googlegroups.com
  
 
 .

 For more options, visit https://groups.google.com/d/optout.

>>>
>>>

-- 
You received this 

Re: [google-appengine] Google has fixed 30 of 707 bugs reported in the past 12 months

[George Bittmann]

Where is the mail deprecation? Post a link if it's happening please. I 
thought they were only no longer approving requests to expand beyond the 
100 daily limit. Is that what you mean?


On Thursday, November 24, 2016 at 8:06:33 AM UTC-5, Kaan Soral wrote:
>
> Hi
>
> Thanks a lot for the reply again
>
> For images, https://cloud.google.com/appengine/docs/python/images/ - the 
> 1600 resize limit started to age a bit, I'm using the images service 
> heavily on https://geobird.com - and considering the recent 4K, 5K 
> resolutions, even bumping the limit to 2400 would improve dynamics a lot, 
> considering it would at least cover 1080p (Current solution is to just 
> serve images with "=s0" - considering most devices have retina resolutions 
> now, most images started becoming "=s0" - and a significant bandwidth is 
> wasted for clients)
>
> If we analyse the case for the images service, it provides dynamic 
> resizing at instant availability, It's an invaluable service, I love 
> appengine because it provides building blocks like these - Instead of 
> depreciating such services, it would be lovely to see new ones, for 
> example, a "videos" service, even though I'm using Zencoder for video 
> processing, if we compare it to the ease of using the images service, it's 
> a heavy burden
>
> @Mark Cummins, I don't know what service you are calling exotic and 
> less-used, It would be great if you could provide concrete examples, 
> interacting with other app engine users, you would be amazed how each 
> component is utilised and valued
> If we analyse the case for mail, I personally was using it to send mails, 
> so, while the deprecation was an extreme nuisance, it wasn't the end of the 
> world, yet, communicating with others, I saw that some were using apps as 
> turnkey solutions, or, they were deploying singular apps for their clients, 
> so having a practical mail solution was crucial to them, some were handling 
> incoming email, while things were simple from the outgoing email 
> perspective, for an app that handled both incoming/outgoing email, the 
> deprecation was much more worrying
>
> On Wednesday, November 23, 2016 at 3:28:07 AM UTC+2, Lorne Kligerman wrote:
>>
>> Heard loud and clear on action speaking louder than words.  We have a lot 
>> brewing and are excited to show it off when ready.
>>
>> There have been some deprecation announcements lately.  The objective 
>> here is to bring App Engine in line with the rest of GCP.  This is a 
>> challenging effort because of how long App Engine pre-dates the rest of the 
>> system.  That being said, we do have our users best interests at heart and 
>> we believe the future state will be a good one.  Significant improvements 
>> have been made to the App Engine Admin API, which officially went GA 
>> 
>>  
>> a couple months ago.
>>
>> Regarding mail, we are currently gathering requirements for a GCP wide 
>> solution.  For images, could you give more detail on exactly which limit 
>> you're running up against and the scenario?
>>
>>
>> On Tue, Nov 22, 2016 at 2:45 PM, 'Alex (Cloud Platform Support)' via 
>> Google App Engine  wrote:
>>
>>> Hi Kaan,
>>>
>>> On a side note, it is possible to receive regular emails from the Google 
>>> Cloud Platform by following these steps:
>>>
>>>1. Access the Cloud Platform Console
>>>
>>>2. Click the “3 vertical dots” on the top-right section of the menu
>>>
>>>3. Navigate to preferences->Updates & Offers
>>>
>>>4. Set email to “On” for Feature announcements
>>>
>>> By doing this, you will receive emails about the latest feature 
>>> announcements on the Cloud Platform.
>>>
>>> Cheers,
>>>
>>> Alex
>>>
>>> -- 
>>> You received this message because you are subscribed to a topic in the 
>>> Google Groups "Google App Engine" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/google-appengine/EFLhIU9GqjU/unsubscribe
>>> .
>>> To unsubscribe from this group and all its topics, send an email to 
>>> google-appengi...@googlegroups.com.
>>> To post to this group, send email to google-a...@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/google-appengine.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/google-appengine/c37962f7-c400-44d9-9ab8-dfd3edc7ec1f%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, 

Re: [google-appengine] Google has fixed 30 of 707 bugs reported in the past 12 months

[Kaan Soral]

Hi

Thanks a lot for the reply again

For images, https://cloud.google.com/appengine/docs/python/images/ - the 
1600 resize limit started to age a bit, I'm using the images service 
heavily on https://geobird.com - and considering the recent 4K, 5K 
resolutions, even bumping the limit to 2400 would improve dynamics a lot, 
considering it would at least cover 1080p (Current solution is to just 
serve images with "=s0" - considering most devices have retina resolutions 
now, most images started becoming "=s0" - and a significant bandwidth is 
wasted for clients)

If we analyse the case for the images service, it provides dynamic resizing 
at instant availability, It's an invaluable service, I love appengine 
because it provides building blocks like these - Instead of depreciating 
such services, it would be lovely to see new ones, for example, a "videos" 
service, even though I'm using Zencoder for video processing, if we compare 
it to the ease of using the images service, it's a heavy burden

@Mark Cummins, I don't know what service you are calling exotic and 
less-used, It would be great if you could provide concrete examples, 
interacting with other app engine users, you would be amazed how each 
component is utilised and valued
If we analyse the case for mail, I personally was using it to send mails, 
so, while the deprecation was an extreme nuisance, it wasn't the end of the 
world, yet, communicating with others, I saw that some were using apps as 
turnkey solutions, or, they were deploying singular apps for their clients, 
so having a practical mail solution was crucial to them, some were handling 
incoming email, while things were simple from the outgoing email 
perspective, for an app that handled both incoming/outgoing email, the 
deprecation was much more worrying

On Wednesday, November 23, 2016 at 3:28:07 AM UTC+2, Lorne Kligerman wrote:
>
> Heard loud and clear on action speaking louder than words.  We have a lot 
> brewing and are excited to show it off when ready.
>
> There have been some deprecation announcements lately.  The objective here 
> is to bring App Engine in line with the rest of GCP.  This is a challenging 
> effort because of how long App Engine pre-dates the rest of the system.  
> That being said, we do have our users best interests at heart and we 
> believe the future state will be a good one.  Significant improvements have 
> been made to the App Engine Admin API, which officially went GA 
> 
>  
> a couple months ago.
>
> Regarding mail, we are currently gathering requirements for a GCP wide 
> solution.  For images, could you give more detail on exactly which limit 
> you're running up against and the scenario?
>
>
> On Tue, Nov 22, 2016 at 2:45 PM, 'Alex (Cloud Platform Support)' via 
> Google App Engine  wrote:
>
>> Hi Kaan,
>>
>> On a side note, it is possible to receive regular emails from the Google 
>> Cloud Platform by following these steps:
>>
>>1. Access the Cloud Platform Console
>>
>>2. Click the “3 vertical dots” on the top-right section of the menu
>>
>>3. Navigate to preferences->Updates & Offers
>>
>>4. Set email to “On” for Feature announcements
>>
>> By doing this, you will receive emails about the latest feature 
>> announcements on the Cloud Platform.
>>
>> Cheers,
>>
>> Alex
>>
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "Google App Engine" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/google-appengine/EFLhIU9GqjU/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to 
>> google-appengi...@googlegroups.com .
>> To post to this group, send email to google-a...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/google-appengine.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-appengine/c37962f7-c400-44d9-9ab8-dfd3edc7ec1f%40googlegroups.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/3988b0b9-29c0-475b-8d08-97ba44af3d1a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Google has fixed 30 of 707 bugs reported in the past 12 months

[Mark Cummins]

Thank you for this update, very reassuring and makes me very happy! 
Personally I'm not too worried about some of the more exotic and less-used 
services being deprecated, so long as their are reasonable migration paths 
and the overall platform remains available.


On Wednesday, 23 November 2016 01:28:07 UTC, Lorne Kligerman wrote:
>
> Heard loud and clear on action speaking louder than words.  We have a lot 
> brewing and are excited to show it off when ready.
>
> There have been some deprecation announcements lately.  The objective here 
> is to bring App Engine in line with the rest of GCP.  This is a challenging 
> effort because of how long App Engine pre-dates the rest of the system.  
> That being said, we do have our users best interests at heart and we 
> believe the future state will be a good one.  Significant improvements have 
> been made to the App Engine Admin API, which officially went GA 
> 
>  
> a couple months ago.
>
> Regarding mail, we are currently gathering requirements for a GCP wide 
> solution.  For images, could you give more detail on exactly which limit 
> you're running up against and the scenario?
>
>
> On Tue, Nov 22, 2016 at 2:45 PM, 'Alex (Cloud Platform Support)' via 
> Google App Engine  wrote:
>
>> Hi Kaan,
>>
>> On a side note, it is possible to receive regular emails from the Google 
>> Cloud Platform by following these steps:
>>
>>1. Access the Cloud Platform Console
>>
>>2. Click the “3 vertical dots” on the top-right section of the menu
>>
>>3. Navigate to preferences->Updates & Offers
>>
>>4. Set email to “On” for Feature announcements
>>
>> By doing this, you will receive emails about the latest feature 
>> announcements on the Cloud Platform.
>>
>> Cheers,
>>
>> Alex
>>
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "Google App Engine" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/google-appengine/EFLhIU9GqjU/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to 
>> google-appengi...@googlegroups.com .
>> To post to this group, send email to google-a...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/google-appengine.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-appengine/c37962f7-c400-44d9-9ab8-dfd3edc7ec1f%40googlegroups.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/20f24616-c354-4703-ac21-5cfa45c563bf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Google has fixed 30 of 707 bugs reported in the past 12 months

['Lorne Kligerman' via Google App Engine]

Heard loud and clear on action speaking louder than words.  We have a lot
brewing and are excited to show it off when ready.

There have been some deprecation announcements lately.  The objective here
is to bring App Engine in line with the rest of GCP.  This is a challenging
effort because of how long App Engine pre-dates the rest of the system.
That being said, we do have our users best interests at heart and we
believe the future state will be a good one.  Significant improvements have
been made to the App Engine Admin API, which officially went GA

a couple months ago.

Regarding mail, we are currently gathering requirements for a GCP wide
solution.  For images, could you give more detail on exactly which limit
you're running up against and the scenario?


On Tue, Nov 22, 2016 at 2:45 PM, 'Alex (Cloud Platform Support)' via Google
App Engine  wrote:

> Hi Kaan,
>
> On a side note, it is possible to receive regular emails from the Google
> Cloud Platform by following these steps:
>
>1. Access the Cloud Platform Console
>
>2. Click the “3 vertical dots” on the top-right section of the menu
>
>3. Navigate to preferences->Updates & Offers
>
>4. Set email to “On” for Feature announcements
>
> By doing this, you will receive emails about the latest feature
> announcements on the Cloud Platform.
>
> Cheers,
>
> Alex
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Google App Engine" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/google-appengine/EFLhIU9GqjU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-appengine.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/google-appengine/c37962f7-c400-44d9-9ab8-
> dfd3edc7ec1f%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CA%2Bzk0pJZ4A1Er1Gmor4oowAk3_bqCDJbusrwC_YLv8n85nwvLg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Google has fixed 30 of 707 bugs reported in the past 12 months

['Alex (Cloud Platform Support)' via Google App Engine]

Hi Kaan,

On a side note, it is possible to receive regular emails from the Google 
Cloud Platform by following these steps:

   1. Access the Cloud Platform Console

   2. Click the “3 vertical dots” on the top-right section of the menu

   3. Navigate to preferences->Updates & Offers

   4. Set email to “On” for Feature announcements

By doing this, you will receive emails about the latest feature 
announcements on the Cloud Platform.

Cheers,

Alex

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/c37962f7-c400-44d9-9ab8-dfd3edc7ec1f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Google has fixed 30 of 707 bugs reported in the past 12 months

[Kaan Soral]

Thanks for the reply, it was good to see

As a small feedback, in essence and core, we all embraced appengine as it 
was a unified solution, each and every service amplifies the experience, so 
instead of deprecating these valuable services, please add to them instead

Two very basic examples are "images" and "mail", we've lost "mail", and 
with the resolution increases in recent years, the limits of "images" 
started being actual limits

As another constructive suggestion, it would be nice to receive regular 
emails from Google Cloud, maybe we could opt-in to gae specifically, and 
receive updates of everything new, fixed and improved

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/3fc12628-be55-46c2-9f98-78b8c38256b2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Google has fixed 30 of 707 bugs reported in the past 12 months

[George Bittmann]

Thanks for the reply. A lot of us who have been seeking support and/or 
signs of life are going to be happy to hear this.



On Thursday, November 17, 2016 at 1:42:06 PM UTC-5, Lorne Kligerman wrote:
>
> Hi there folks,
>
> Apologies for the delayed response.  We definitely hear you in that our 
> existing public issue tracker has not been kept up to date as best as we’d 
> like.  That being said, a few comments on the original post here.
>
> As mentioned, many issues have been closed as duplicate, invalid, etc. 
>  I’ve scanned through a bunch of these issues and they all involve a member 
> of the Cloud Support team working with the user who posted the issue.  The 
> final comment in these issues include a description of why the issue was 
> being closed with the specific status.  As well, a lot of the issues logged 
> are unique problems with customer applications and not necessarily issues 
> with the platform.
>
> Our Cloud Support team has been doing a great job at triaging the issues 
> as they come in.  A lot of these issues have been later overlooked as we 
> are missing a connection between our internal and external system.
>
> There are plans underway to migrate the public issue tracker to a new 
> system.  In preparation we will soon be doing a bankruptcy of sorts, on 
> issues that are quite old and have not been modified in some time.  We’ll 
> post full details to this group in advance.  Once the new system is in 
> place we will do our best to keep the issues in good shape.
>
> Regarding the App Engine standard environment, there is no deprecation 
> coming.  We are excited about the updates to the App Engine flexible 
> environment that were just announced 
> , 
> which will run alongside the standard environment.  We are committed to 
> both environments, with both providing unique advantages.  We are also 
> excited about upcoming enhancements to the standard environment that will 
> start to show up early in 2017, beginning with the Java 8 runtime.
>
> Cheers,
>
> Lorne.
>
>
> On Friday, November 4, 2016 at 12:52:18 PM UTC-7, Mark Cummins wrote:
>>
>> I also am beginning to fear a "GAE deprecation email". Could anyone at 
>> Google give any reassurance on this? Is GAE standard going to be abandoned 
>> in favour of managed VMs (which are actually very different)?
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/8a63ffb4-bb62-4d75-9626-40f597daa895%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Google has fixed 30 of 707 bugs reported in the past 12 months

[PK]

Hi Lorne,

thanks for your reassuring message. Many of us love GAE Standard and our 
customers depend on it so we are glad to hear this update. 

Having said that, actions speak louder than words: Most of the recent 
announcements on GAE Standard have been about deprecations, new releases come 
out rarely and I do not remember when an API was improved or a new API was last 
announced. At the same time, you have cut the prices on GCE, a newer GCP 
offering at least twice since its introduction but never for GAE.

Then again, GAE has been very stable, we had no downtime this year because of 
GAE issues and this is also very much appreciated. We will be following the 
developments closely.

Best,
PK


> On Nov 17, 2016, at 10:42 AM, 'Lorne Kligerman' via Google App Engine 
>  wrote:
> 
> Hi there folks,
> 
> Apologies for the delayed response.  We definitely hear you in that our 
> existing public issue tracker has not been kept up to date as best as we’d 
> like.  That being said, a few comments on the original post here.
> 
> As mentioned, many issues have been closed as duplicate, invalid, etc.  I’ve 
> scanned through a bunch of these issues and they all involve a member of the 
> Cloud Support team working with the user who posted the issue.  The final 
> comment in these issues include a description of why the issue was being 
> closed with the specific status.  As well, a lot of the issues logged are 
> unique problems with customer applications and not necessarily issues with 
> the platform.
> 
> Our Cloud Support team has been doing a great job at triaging the issues as 
> they come in.  A lot of these issues have been later overlooked as we are 
> missing a connection between our internal and external system.
> 
> There are plans underway to migrate the public issue tracker to a new system. 
>  In preparation we will soon be doing a bankruptcy of sorts, on issues that 
> are quite old and have not been modified in some time.  We’ll post full 
> details to this group in advance.  Once the new system is in place we will do 
> our best to keep the issues in good shape.
> 
> Regarding the App Engine standard environment, there is no deprecation 
> coming.  We are excited about the updates to the App Engine flexible 
> environment that were just announced 
> , which 
> will run alongside the standard environment.  We are committed to both 
> environments, with both providing unique advantages.  We are also excited 
> about upcoming enhancements to the standard environment that will start to 
> show up early in 2017, beginning with the Java 8 runtime.
> 
> Cheers,
> Lorne.
> 
> 
> On Friday, November 4, 2016 at 12:52:18 PM UTC-7, Mark Cummins wrote:
> I also am beginning to fear a "GAE deprecation email". Could anyone at Google 
> give any reassurance on this? Is GAE standard going to be abandoned in favour 
> of managed VMs (which are actually very different)?
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to google-appengine+unsubscr...@googlegroups.com 
> .
> To post to this group, send email to google-appengine@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/google-appengine 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-appengine/c67b1086-5b4f-481b-81bf-49af56bb154a%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/8C8306B2-32A5-4DED-86AC-12426A0A75A4%40gae123.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Google has fixed 30 of 707 bugs reported in the past 12 months

['Lorne Kligerman' via Google App Engine]

Hi there folks,

Apologies for the delayed response.  We definitely hear you in that our 
existing public issue tracker has not been kept up to date as best as we’d 
like.  That being said, a few comments on the original post here.

As mentioned, many issues have been closed as duplicate, invalid, etc. 
 I’ve scanned through a bunch of these issues and they all involve a member 
of the Cloud Support team working with the user who posted the issue.  The 
final comment in these issues include a description of why the issue was 
being closed with the specific status.  As well, a lot of the issues logged 
are unique problems with customer applications and not necessarily issues 
with the platform.

Our Cloud Support team has been doing a great job at triaging the issues as 
they come in.  A lot of these issues have been later overlooked as we are 
missing a connection between our internal and external system.

There are plans underway to migrate the public issue tracker to a new 
system.  In preparation we will soon be doing a bankruptcy of sorts, on 
issues that are quite old and have not been modified in some time.  We’ll 
post full details to this group in advance.  Once the new system is in 
place we will do our best to keep the issues in good shape.

Regarding the App Engine standard environment, there is no deprecation 
coming.  We are excited about the updates to the App Engine flexible 
environment that were just announced 
, which 
will run alongside the standard environment.  We are committed to both 
environments, with both providing unique advantages.  We are also excited 
about upcoming enhancements to the standard environment that will start to 
show up early in 2017, beginning with the Java 8 runtime.

Cheers,

Lorne.


On Friday, November 4, 2016 at 12:52:18 PM UTC-7, Mark Cummins wrote:
>
> I also am beginning to fear a "GAE deprecation email". Could anyone at 
> Google give any reassurance on this? Is GAE standard going to be abandoned 
> in favour of managed VMs (which are actually very different)?

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/c67b1086-5b4f-481b-81bf-49af56bb154a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Google has fixed 30 of 707 bugs reported in the past 12 months

[Mark Cummins]

I also am beginning to fear a "GAE deprecation email". Could anyone at Google 
give any reassurance on this? Is GAE standard going to be abandoned in favour 
of managed VMs (which are actually very different)?

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/968b8341-6968-4494-be2d-f8750b9a826a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Google has fixed 30 of 707 bugs reported in the past 12 months

[PK]

I remember the days I cared about these metrics. Now I take this lack of 
progress as granted and work around the issues. Franky, I am happy every day 
that I have not received the dreaded  GAE deprecation e-mail. Unless of course 
they have already started deprecating GAE the long way: one service at a time. 

Of course the sad thing is that this path is a self fulfilling prophecy, 
because the developers will not feel comfortable to start other projects or to 
recommend GAE to others. So eventually they will look at the number of the 
issues and the number of the remaining customers and they will say: "Our goal 
is to continue to do a better job of delivering reliable, performant, and full 
featured services. This means deprecating those APIs that have little to zero 
usage on our system to free up resources for newer, better performing products.”

It is sad because I am so happy with GAE otherwise, but because of the 
uncertainty I just cannot see myself starting other projects or recommending it 
to others.

PK

> On Nov 2, 2016, at 8:04 PM, pdknsk  wrote:
> 
> https://code.google.com/p/googleappengine/issues/list?can=1=opened-after%3Atoday-365=-id
> 
> ^ All 707 (public) bugs reported in the past 12 months.
> 
> https://code.google.com/p/googleappengine/issues/list?can=2=opened-after%3Atoday-365=-id
> 
> ^ 322 are still open.
> 
> https://code.google.com/p/googleappengine/issues/list?can=1=opened-after%3Atoday-365+closed-after%3Atoday-365+-status%3Afixed=-id
> 
> ^ 355 were closed for reasons other than Fixed (Invalid, Duplicate and the 
> like).
> 
> https://code.google.com/p/googleappengine/issues/list?can=1=opened-after%3Atoday-365+status%3Afixed=-id
> 
> ^ 30 were fixed.
> 
> 14 are Go bugs, which are fixed by the Go team.
> 4 are SDK bugs, which are usually fixed by the gcloud team.
> 1 was closed as fixed, but isn't.
> 1 is a typo.
> 
> That makes 10 bugs fixed by the App Engine "Engineering Team".
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to google-appengine+unsubscr...@googlegroups.com 
> .
> To post to this group, send email to google-appengine@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/google-appengine 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-appengine/bef808ae-a4b0-487b-9e5b-2181e613b5cb%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/AD9FD6B8-D48E-4AA3-9DE8-5E102B9AAEE4%40gae123.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Google has fixed 30 of 707 bugs reported in the past 12 months

[Vinuth Madinur]

Wow. So much love for App Engine.


On Thu, Nov 3, 2016 at 8:34 AM, pdknsk  wrote:

> https://code.google.com/p/googleappengine/issues/list?
> can=1=opened-after%3Atoday-365=-id
>
> ^ All 707 (public) bugs reported in the past 12 months.
>
> https://code.google.com/p/googleappengine/issues/list?
> can=2=opened-after%3Atoday-365=-id
>
> ^ 322 are still open.
>
> https://code.google.com/p/googleappengine/issues/list?
> can=1=opened-after%3Atoday-365+closed-after%3Atoday-365+-
> status%3Afixed=-id
>
> ^ 355 were closed for reasons other than Fixed (Invalid, Duplicate and the
> like).
>
> https://code.google.com/p/googleappengine/issues/list?
> can=1=opened-after%3Atoday-365+status%3Afixed=-id
>
> ^ 30 were fixed.
>
> 14 are Go bugs, which are fixed by the Go team.
> 4 are SDK bugs, which are usually fixed by the gcloud team.
> 1 was closed as fixed, but isn't.
> 1 is a typo.
>
> That makes 10 bugs fixed by the App Engine "Engineering Team".
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-appengine.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/google-appengine/bef808ae-a4b0-487b-9e5b-
> 2181e613b5cb%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAEKebvJTSGXeH1Kv%3D4AAZ-jUdimOC%2BuPJH-nXNwCzzvo-uqHfw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.