Release Guidelines #460
Labels
admin
Administrative chores etc.
discussion
Feedback is requested on an ongoing basis
documentation
documentation change can be for code and/or markdown pages
Milestone
We've recently started building out this repository's Wiki in force, with ancillary "meta" documentation in addition to calendar/agendas/minutes for the Working Group calls. As the
ReleaseGuidelines.md
went through another major set of changes with0.4.1
, I'm wondering if maybe this document makes more sense as part of the Wiki than with the repository itself?On one hand, documents within the main repo need to follow the lengthy release/review process and so changes can be hard to come by, particularly quick ones. On the other hand, maybe certain meta-documentation like the ReleaseGuidelines.md should go through this process? I'm on the fence but leaning towards this document moving to the Wiki.
Curious of other's thoughts, both on where the document lives and the process itself.
The text was updated successfully, but these errors were encountered: