thanks greg. DEV_NOTES.txt still contains a *lot* more than just the release process, including baseline dependencies, gpg-specific stuff, packaging quirks for different operating systems, requirements for building docs.
DEV_NOTES.txt (how to release, pre-reqs, packaging, code stats, etc) is completely different content than devnotes.md (stuff you should know if you want to write weewx code), so the file naming is unfortunate. agree that TODO and ROADMAP should be consolidated. issues really track the TODO items. tom tends to move on those at a much faster pace than i am able, so i sometimes go to do weewx stuff only to find the TODO items or issues are gone/closed. i am inclined to keep developer notes (DEV_NOTES.txt content) separate from the docs, but that is just my old-skool notion that i should be able to read everything i need to build/develop without having to install a toolchain to build the docs i am supposed to read. m -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/weewx-development/A02F629C-520C-4420-B9DF-3C766613F276%40gmail.com.
