-
-
Notifications
You must be signed in to change notification settings - Fork 810
[Issues Process] Assigned issues guidelines
Issues will be assigned to core members if they fit within that members expertise and if the issue is not a major feature.
The issue will then be expected to have a followup (as a comment on progress or lack thereof) or close within a reasonable time.
If that member does not feel that it fit's within their expertise or if they will not have the time to fix or reply they can unassign themselves and leave a comment saying that (and if possible why), but perhaps consider if it should be closed instead.
Assigned issues should not be left unresolved for long periods of time without updates. If the solution is still worked on please leave some kind of update (something like "still working on this" is enough), and if it's not please consider leaving a link to the branch (if work has started) and saying that work on it has stopped/stagnated so that someone else can continue on it.
The reason for this is that a assigned issue is a sign to other contributors that we are working on this so we can reduce duplicate work and people know who to ask if they want to collaborate/help out.
- Bolt Wiki Home
- Tuesday Dev meetings
- Curated list of articles and tutorials
- Bolt internationalisation (i18n)
- Bolt Style Guide
- Roadmap
- TODOs
- [Tests] Unit & Functional Split
- [Tests] Code Coverage
- Core Team
- Bug/feature Process
-
Release Process
- Branching
- Packaging release builds