Skip to content
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

Release Notes & Critical Safety Updates #2366

Open
Naterater opened this issue Dec 26, 2019 · 2 comments
Open

Release Notes & Critical Safety Updates #2366

Naterater opened this issue Dec 26, 2019 · 2 comments

Comments

@Naterater
Copy link
Contributor

Naterater commented Dec 26, 2019

https://ardupilot.org/plane/docs/project-news.html, having the link to the github page with the release notes is an excellent start for a uniform location for the release notes. To take this to the final step, I think a few options could be considered.

  1. Create or rename the "project-news" html to be "releases" or "release-notes" so that the page title and URL match and there is no confusion. Maybe even redirect to a simpler URL like ardupilot.org/plane/releases
  2. Advertise this page on the ardupilot.org homepage or somewhere higher in the left-hand menu/tree instead of at the bottom in the appendix section.
  3. Auto-generate the text and bullet points on the actual wiki page to avoid redirecting to the github format (that most non-code users are generally uncomfortable with). This doesn't need to be physically copying and pasting the same information; leave the github page as the original source and the wiki page should reference it. This is done with the full parameter list, so I'm assuming it can be done with this page as well. It should only need to be updated once daily.
  4. Add button(s) to subscribe to mailing list(s) that will inform them of new stable, beta, or critical safety releases of firmware by email. I think people have been asking for this as the social media and forum posts can be buried quickly in just a few days' time. If we wanted to go a step further, we could maintain a little database of users and what autopilots they want updates for. For example, if a critical safety bug was found on the Cube Orange, why does the everyone need to be spammed about the update? This could really help the communication between the developers and the end users. Just subscribe to the hardware you want updates for.
@Naterater Naterater changed the title Release Notes Wiki Page Release Notes & Critical Safety Updates Dec 26, 2019
@stephendade
Copy link
Contributor

As an update to this, @auturgy and myself are working on a method to manage/release safety bulletins. We gave an initial talk about at at the 2020 Developer's Conference: https://www.youtube.com/watch?v=w6dwC9udmjE&list=PLC8WVaJJhN4xGtB7TDT5OQTeOIkhzTrcA&index=2

@Hwurzburg
Copy link
Contributor

User notification is now active....can we close this now?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants