You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that shortly after the 2.13.2 extension update was approved for AMO, the native client extension in the Arch Linux repos was updated to 2.13.3, once again creating a mismatch between extension and native version.
Is it possible to not release the updated native client until the AMO release has been approved by Mozilla so as to avoid this disconnect? It seems like the release to Arch repos is much faster than Mozilla's AMO approval process.
The text was updated successfully, but these errors were encountered:
Same issue as #620
It seems that shortly after the 2.13.2 extension update was approved for AMO, the native client extension in the Arch Linux repos was updated to 2.13.3, once again creating a mismatch between extension and native version.
Is it possible to not release the updated native client until the AMO release has been approved by Mozilla so as to avoid this disconnect? It seems like the release to Arch repos is much faster than Mozilla's AMO approval process.
The text was updated successfully, but these errors were encountered: