Mark: I notice in several of your posts you say this or that is on your to do list.
Do you make your to do list available anywhere?
Your locked post (with the topic name CumulusMX - Future development) might be where people would look. Alternatively, people might expect viewtopic.php?f=40&t=17889 to be updated since you took over development.
Welcome to the Cumulus Support forum.
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Cumulus MX V4 beta test release 4.0.0 (build 4019) - 03 April 2024
Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Cumulus MX V4 beta test release 4.0.0 (build 4019) - 03 April 2024
Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
CumulusMX - TO DO List
- mcrossley
- Posts: 12756
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Re: CumulusMX - TO DO List
Currently it is within a tool I use for logging and tracking them. I only recently started using this tool which is really a bug tracker (MantisBT).
I've added my immediate ToDo list to it, and am slowly going back through requests and suggestions and added them if appropriate/doable.
I add bug reports that need fixing to it as well. If I can be disciplined enough to use it rigorously then it should also track what goes into each release.
[MantisBT is PHP based and uses a backend database, so it may be possible to host it somewhere eventually. I think I'd keep it read-only, things can get messy very quickly if everyone could contribute to it, particularly as it isn't really set-up for feature requests.]
I've added my immediate ToDo list to it, and am slowly going back through requests and suggestions and added them if appropriate/doable.
I add bug reports that need fixing to it as well. If I can be disciplined enough to use it rigorously then it should also track what goes into each release.
[MantisBT is PHP based and uses a backend database, so it may be possible to host it somewhere eventually. I think I'd keep it read-only, things can get messy very quickly if everyone could contribute to it, particularly as it isn't really set-up for feature requests.]