Ticket #703 (closed enhancement: fixed)
find a way to keep "Recent News" up to date
| Reported by: | geofft | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | The Distant Future |
| Component: | website | Keywords: | |
| Cc: | Fixed in version: | ||
| Upstream bug: |
Description
Apparently, we recently upgraded W20-575 to Debathena on Jaunty and are planning to upgrade the other clusters soon....
Maybe someone should be assigned to spend 5 minutes at/after release-team (since that's the closest thing to a timer interrupt the project has) to determine if we need anything new in that section?
Alternatively, I hear we have plans about rethinking our development process and sending package update notification somewhere. Perhaps we can integrate "Determine if this is interesting enough to note on the website" into that workflow.
Change History
comment:2 Changed 14 years ago by jdreed
We could also setup a blog and use its RSS feed. Which frankly, might not be a terrible idea. The blog could be canonical (allowing us to edit announcements if we screw up), and mail to debathena-announce and Twitter posts could redirect people to the blog for the full details of announcements.
We could just link to Twitter and be done, on the theory that it's easer to keep Twitter up to date (which may not be true).