-
Notifications
You must be signed in to change notification settings - Fork 212
Project Management Guidelines
Issues are triaged by being labeled with the "triaged" label.
The triage process will involve looking at unlabeled items and categorizing them.
- For Docs issues, we'll triage priority then
- For questions, we label question and assign the current forum on-call engineer.
- For bugs/improvements, we'll move the issue to the appropriate repo and it will be triaged there.
- There is a convenient issue mover tool here: https://github-issue-mover.appspot.com/
- For general feature requests, we may move the issue to the appropriate repo or it may stay in Azure-Functions with a "feature" label on it.
- Since no work actually happens out of this repo, if the work doesn't fit inside this repo, we'll need to split it up into pieces that do fit into the main repos or create a new repo to track that work.
- While this repo works fine for specs/high level planning, it doesn't do well for engineering design/etc. since it is part of our engineering processes.
We use a waffle board to manage the doc work: https://waffle.io/Azure/Azure-Functions?label=documentation
It's reviewed every week and new work is dispatched to the various writers/PMs.
The assigned engineer should follow up on the question as soon as they can.
Note: We triage this repo once or twice a week. If you need a question answered, it can be faster to use Stack Overflow as we have alerts on new SO questions, but not on GitHub (because we have to triage GitHub issues to figure out what it is about). You can find other Stack Overflow questions here: http://stackoverflow.com/questions/tagged/azure-functions
Note: there is no official SLA on answering questions in this forum. If you need support with a business SLA, please use the official Azure Support which has various options to meet your business needs.