- When bugs are discovered during normal development, they should be
fixed in the next release.
I think we should say that they should "generally" be fixed for the
next release. We should always strive to have addressed all known bugs
for any given release. But we may run into situations where certain
low-priority (or low-impact) bugs may need to be addressed in a future
release, due to time/resource constraints.
- When bugs are discovered after a release candidate has been
tagged,
they should be investigated to determine their severity. Only
critical bugs
should hold up the release; all other bugs can go in the following
release.
Agreed.
- It's ok for a release to be missing certain features, as long as
those
features are tracked on the roadmap and prioritized according to the
consensus priority. The prioritization of JIRA tickets is always
open for
debate on the dev list, though it should be kept in mind that if a
developer
chooses to work on something of lower priority, that's his or her
prerogative and should not be discouraged.
Agreed.
