Release candidate expiry

[skiwi]

After running this for rather too long (to give feedback) it has expired with no warning.

I'd really appreciate some sort of nagging warning, as our release process takes (considerable) time to have an app allow-listed and installed.

[Eve]

You managed to get the (beta and RC) allow-listed but can't get the release allow-listed? How does that work?

Sure, a nag could have happened. All that was important from our point of view was making sure people didn't go on using a pre-release and potentially causing themselves problems.

[skiwi]

You managed to get the (beta and RC) allow-listed but can't get the release allow-listed? How does that work?

Let's see: minimum one week for allow-listing (median = 2 weeks), then at least a day or two to actually get it installed.
Then RC works well, combine that with a couple of weeks leave (skiing in Japan since you ask), and bang, one dead EA RC.

[skiwi]

You managed to get the (beta and RC) allow-listed but can't get the release allow-listed? How does that work?

Sure, a nag could have happened. All that was important from our point of view was making sure people didn't go on using a pre-release and potentially causing themselves problems.

You know, I have reflected on this response, prompted by the third release of EA 12 since it went GA.
One of the reasons I held off moving from the RC was to wait for any initial quick 'bug fix' releases post GA, exactly because our process to get EA into a production environment is slow and expensive.

I have two comments
1) NO ONE from your service area has contacted me since I submitted a service request to see if anything could be done about extending the operation of the RC until I can get the GA through our hoops. (Kudos for the quick response on the forums, but...)
In my case not having a nag has caused more problems than from continuing to operate the RC.

2) this response was to shoot the messenger and the organisation within which EA is used.

More appropriate would have be something along the lines of, "thanks for the good idea, we are always ready to accept feedback from our users because we know how it contributes to improvements to our already successful product - we'll use it next time we have betas and RCs"

I'm worried that this is indicative of the viewpoint with which customer suggestions are seem.

[Eve]

You know, I have reflected on this response, prompted by the third release of EA 12 since it went GA.
One of the reasons I held off moving from the RC was to wait for any initial quick 'bug fix' releases post GA, exactly because our process to get EA into a production environment is slow and expensive.

If you were still happily using the RC, neither of the builds since release would have been important to you. You could, (and I would recommend you to) just pick a build and sit on it while we continue a nice fast release cycle. Go through your upgrade process when something is fixed that impacts you.

NO ONE from your service area has contacted me since I submitted a service request to see if anything could be done about extending the operation of the RC until I can get the GA through our hoops.

When did you send your request via email? I can see the request now, but I didn't see it at all yesterday. Unfortunately, will not be able to get the RC to load while your computer reports a date after March 1.

this response was to shoot the messenger and the organisation within which EA is used.

Not my intention. I may be more blunt than is helpful at times, but I merely wanted to express suprise and incredulity that somewhere that takes two weeks to authorize a new version of a product would authorize a pre-release at all.