FENIX 7 SOFTWARE UPDATE 14.31 BATTERY DRAIN

I disagree. The problem is not that people write about problems but that there is a problem and that response is lacking. Same as in beta forums. Marking threads as closed is not how problems will be resolved, it will just make them look less problematic. Discussions in all those forums discovered important points regarding the problem and its occurence. 

7910838 said:

Garmin lacks quality control internally, especially on the software end

Obviously and unfortunately.

Not saying we don't make mistakes and I can't speak for all external moderators, but we typically don't lock threads without a reason and a link to the main thread on the topic. Often joining similar threads if possible. This latest round of issues regarding firmware and Garmin Connect changes has been especially difficult with forum members opening new threads, or opening threads in the wrong sub-forum, such as the beta forums for known production issues. Certainly, a learning experience. Can always get better.

Learn from beta forums and mistakes made in the past. Repeating same mistakes over and over again (as with this battery drain problem that was identified and reported long ago in beta and for previous software versions) is not learning. 

I'm referring to external (volunteer) moderators learning. We have little input regarding anything internal to Garmin, other than moderating the forums. Nonetheless, I welcome all constructive feedback. Thanks.

In that case I misunderstood. My comments are directed to Garmin software development since that is the key problem here.

I imagine it must be quite difficult sometimes to moderate forum without precise internal information. It seems that some Garmin staff on this forums shares the same problem (not having some important information at times)

Vizi said:

Marking threads as closed is not how problems will be resolved

Forum threads are closed with a link posted to the main thread to steer customers reporting the same software issue to the main thread that is being monitored and updated.

Vizi said:

It seems that some Garmin staff on this forums shares the same problem

On the official side vs. the greatly appreciated work of our volunteer moderators, I will update an active issue thread as the information is updated and changes. Along with providing an update when the issue within the thread has been resolved. What our volunteer moderators due within our forums is priceless.

In my own experiences, personally speaking regarding the information that we share, I do not see a difference in our policies compared to other large tech companies I have been with prior to Garmin.

I understand what was done. But you are closing all other threads and this one is already marked as resolved (and it is far from resolved).

Same fate happened to some other threads in the past and it did not help resolving them. That is why I expressed disagreement with such practice.  

Garmin - Chris said:

I do not see a difference in our policies compared to other large tech companies I have been with prior to Garmin

Of course you do not. But that is not the topic, not it is what I said. Serious battery drain bug in public software is a topic. You are free to implement any policies that will prevent bugs identified in beta stage go into public software version.