|
1 | 1 | # Release Notes |
2 | 2 |
|
| 3 | +## v9.2 |
| 4 | + |
| 5 | +_September 2020:_ Version 9.2 |
| 6 | + |
| 7 | +### Spoke Project Status Update |
| 8 | + |
| 9 | +As we are getting closer to the 2020 election, MoveOn is 'code-freezing' changes on our production instance. |
| 10 | +We believe campaigns and Spoke hosters would be well-advised to do the same and aim for stability over this time. |
| 11 | +The only releases before November 3rd, 2020 will be for security updates. |
| 12 | + |
| 13 | +We will also continue to merge additions to documentation and integration test PRs directly into our `main` branch. |
| 14 | + |
| 15 | +That said, other hosters and developers are continuing to make bug fixes and add important features for their |
| 16 | +own texting programs. Normally, MoveOn's release process involves first gathering a release candidate, then |
| 17 | +running QA on the changes, and finally running it in production for a day or two to shake out any bugs missed |
| 18 | +during QA and review and to evaluate the release 'at scale'. Without this final step, we can't make a strong commitment |
| 19 | +to release readiness. |
| 20 | + |
| 21 | +However, we want to track these improvements, so we will be maintaining two 'experimental' PRs -- one more conservative |
| 22 | +with small changes and mostly bug fixes: [stage-main-postelection2020-stable](https://github.com/MoveOnOrg/Spoke/pull/1830). |
| 23 | +The other with larger changes but riskier to deploy before the election: [stage-main-postelection2020-unstable](https://github.com/MoveOnOrg/Spoke/pull/1831). If a hosting partner steps up to |
| 24 | +run one of these at any time and affirms its stability, we will mark that. Additionally, in the conservative PR, |
| 25 | +we will link to specific PRs that if you run into a particular bug in production you can cherry-pick that PR to fix that issue. |
| 26 | + |
| 27 | +After the election, I'm sure there will be a lot of changes and diverged branches from different organizations. |
| 28 | +We will be here to try to gather those changes, but we'd like to note that will be significant work and can't happen |
| 29 | +without those organizations also making an effort to separate their 'hacks' to make something work vs. changes that |
| 30 | +will be maintainable and support the long-term architecture and stability of Spoke for the community. We recommend |
| 31 | +whenever possible, opening a PR on specific small changes -- these are more likely to be mergeable after the election. |
| 32 | +If that's not possible due to time/development constraints, we ask that you at least open a 'organization dev' PR that |
| 33 | +just includes all your changes -- then post-election we can at least sort out the features and the community can |
| 34 | +have a place to see what was done. |
| 35 | + |
| 36 | +I'd like to take a moment to celebrate this amazing community -- so many progressive orgs and campaigns are using Spoke and |
| 37 | +contributing back to it -- along with a cadre of committed volunteer developers, designers and texters. Good luck |
| 38 | +with all your campaigns -- let's win! |
| 39 | + |
| 40 | +### New Features/Improvements |
| 41 | + |
| 42 | +- Throughout the admin on the People page, Message Review, and Campaign stats, there are little links to the texter's |
| 43 | + own Todos page view. This can be useful for admins to see what campaigns a texter is part of and debug any |
| 44 | + issues where seeing the texter view can help. |
| 45 | +- Experimental DB_READONLY_HOST variable which can connect to a replica/read-only instance for some specific queries. |
| 46 | + In the event of high database stress, setting this may help relieve IO on the 'writer' database instance. |
| 47 | + |
| 48 | +### Bug Fixes |
| 49 | + |
| 50 | +- Fixed a regression in 9.1 where /twilio-message-report Twilio validation would fail if TWILIO_MULTI_ORG=1 but |
| 51 | + TWILIO_MESSAGE_CALLBACK_URL was NOT set. We reverted that behavior, but recommend that you update your |
| 52 | + twilio config to `/twilio-message-report/<org id>` in this configuration and then set TWILIO_VALIDATION=1 |
| 53 | +- Fixed a but in 9.1 on the superadmin organizations page where creating an organization did not work. |
| 54 | +- Fixed two minor security issues to restrict post-login redirect and hide errors on the front-end by-default. |
| 55 | + If you want to re-enable errors on the front-end, set SHOW_SERVER_ERROR=1 |
| 56 | +- Fixed issue with Release Contacts texter sidebox where clicking "Done for the day" would not give feedback on |
| 57 | + the todos screen -- it now clears the 'send first messages' and 'replies' buttons where appropriate. |
| 58 | + |
| 59 | +### Appreciations |
| 60 | + |
| 61 | +Thanks to [jeffm2001](https://github.com/jeffm2001) and [schuyler1d](https://github/schuyler1d) |
| 62 | + |
3 | 63 | ## v9.1 |
4 | 64 |
|
5 | 65 | _September 2020:_ Version 9.1 |
6 | 66 |
|
| 67 | +* Regression notice: When TWILIO_MULTI_ORG=1 is set but TWILIO_MESSAGE_CALLBACK_URL is not, /twilio-message-report |
| 68 | + fails. There is a [fix](https://github.com/MoveOnOrg/Spoke/pull/1826) that is also available in 9.2 (above). |
| 69 | + |
7 | 70 | ### New Features/Improvements |
8 | 71 | - **New UI for adding organizations to your instance:** There is now a page only accessible for users with `is_superadmin` set for adding orgs in a Spoke instance. You can access this screen through the user menu under "superadmin tools." We've gated this feature to only users with that privilege to keep any roles you already have on your instances from suddenly gaining the ability to add orgs. You can only change a user's `is_superadmin` status with a direct DB query at this time. *The first user on new instances will be a superadmin by default now* |
9 | 72 | - **Past campaign contact loader:** Creates a contact loader that allows someone to select contacts from a past campaign and filter optionally for a particular question response (or no response) by entering a message review query into the contact loader. The contact loader has instructions inline. |
|
0 commit comments