Mozilla Add-On store received last release over 3 years ago

[FlorianFranzen]

• I'm submitting a ...

  • Bug report
  • Feature request
  • Support request
  • Other

• What is the current behavior and expected behavior?

  • Latest version to be published to the store according to release notes: v0.44.1

  • Latest version on Mozilla Add-On store: v0.41.1

[ltfschoen]

This is really bad. Now I know why most of the features like not being able to filter what accounts to connect to a dApp isn't available. I will use the development version in future.

[wirednkod]

cc @TarikGul

[TarikGul]

As to why there hasn't been a store release in the past this comment can shed some light #1283 (comment).

We do intend on releasing once we get the credentials for the store - that being said I would like to make sure the above is also in line with the release.

[Tbaut]

I think pushing a release when the credentials are available is sensible though. Waiting to add more potential features with their potential related issues will only push back the release date for no good reason IMHO. The mentioned missing features aren't available in the current version in any case.

Releasing often, with baby steps, and act upon feedback, is I think the safest. There are ppl today that have been annoyed for many years for features that do exist in master. What we are about to do with giant steps is actually dangerous in terms of support issues and user feedback. Would the release process take hours.. Why not, but it's not the case.

[FlorianFranzen]

Congratulations, Mozilla now official tracks the latest update with 3 years.

[TarikGul]

@FlorianFranzen We are finalizing our plans to get these released in the next month (we have no choice but to get it resolved this month) - depending on if we get the credentials it will either a) be released under the same extension or b) we will create a new extension - along with migrations and export/import guides.

Congratulations, Mozilla now official tracks the latest update with 3 years.

I understand your sentiment, but let's keep things professional and constructive.

[FlorianFranzen]

I understand your sentiment, but let's keep things professional and constructive.

I really doubt you do as some people might consider not updating the official wallet for the only popular and privacy preserving browser unprofessional by itself.

And this is only the peak of Parity's inability to have proper version and release management. You are creating an endless amount of unnecessary work for hundred of developers and are completely unapologetic about it.

Not to mention that I have been asking for this issue to get the proper attention for longer then you can imagine, even when the old maintainer was still around. Now we reached the point where the with the latest runtime update you will no longer be able to sign anything in Firefox.

And if you do not take my word for it, just go through the issue tracker and see how many of the issues here all relate to the fact that the extension is outdated. This is a major issue for thousand of users!

Lastly, talking about professionalism: If Parity does not have access to the Mozilla account, who does? Was this just a supply channel attack waiting to happen? Why has the readme not been updated? Why are there not at least pre-build firefox extensions under releases?

EDIT: @TarikGul Please do not take this personal, I know how deep the miss-management at Parity went and that you are probably the least responsible for it. But polkadot.js has always been a train crash waiting to happen and this could have all been easily avoided.

[bkchr]

@FlorianFranzen maybe you could come over more nicely than this. You for sure know the history of the project and it was never a real parity project. We don't need to go into details here.

Nevertheless, I can tell you that there will be an update to the extension in the next two weeks.