New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revise Stable Updates activation instructions re legacy shop removal #2599
Comments
The following is the proposed new version of our activation dialog. Comments welcome. The above referenced #2539 has a screen grab of our 'interim' variant. |
@FroggyFlox & @Hooverdan96 given we have our initial Open Collective integration at Appman I'd like to get this proposed change into both master and testing before our 4.6.1-0 Stable and 5.0.0-0 testing releases. |
@phillxnet, looks good to me! |
…ockstor#2599 Modify our "Activate Stable updates" dialog instructions in accordance with our removal of the now legacy/redundant shop that has now been replaced by Appman's initial integration with our newly established Open Collective.
…ctivation_instructions_re_legacy_shop_removal Revise Stable Updates activation re legacy shop removal #2599
…ockstor#2599 Modify our "Activate Stable updates" dialog instructions in accordance with our removal of the now legacy/redundant shop that has now been replaced by Appman's initial integration with our newly established Open Collective. (cherry picked from commit ae3f342)
We have now dropped our legacy 'shop' that was maintain (at 100% discount) solely due to it's involvement in activation code issuance: see: https://forum.rockstor.com/t/appman-rockstor-com-maintenance-open-collective-integration/8867
It is proposed that we now update our Web-UI embedded instructions, as a follow-up to the prior transition changes introduced in the following pull request:
#2539
That accommodated our initial Open Collective arrangements.
We no longer require any reference to our now legacy/defunct 'shop', give we now have preliminary Appman to Open Collective integration: serving the vast majority of our prior use cases.
The pull request associated with this issue should remain as small/focused as possible give it's relevance to not only our Release Candidate/Stable master branch, but also our pending release new testing branch/updates. It should also be squashed to a single commit to assist with the cherry picking process.
The text was updated successfully, but these errors were encountered: