- Dripal區分問題等級的方式。
- Critical (#) - 嚴重的
-
- Bug (#) - 臭蟲
- Critical bugs include those that: 嚴重的問題包含以下範圍.
- Render the system unusable and have no workaround. 系統無法使用,而且找不到解決方法
- Cause loss/corruption of stored data. (Lost user input, e.g. a failed form submission, is not the same thing as data loss and in most cases is major). 儲存資料遺失或損壞. (如果客戶在送出資料過程導致資料遺失,要歸類為主要的等級)
- Expose security vulnerabilities. 暴露資訊安全漏洞.
- Cause tests to fail in HEAD on the automated testing platform, since this blocks all other work. 在自動測試平台的一開始就發生問題,而導致所有的其它測試工作被封鎖.
- Cause race conditions, database deadlocks etc. for which even code with 100% automated test coverage may be affected. 即使自動測試含蓋率已經是100%, 還是發生導致競跑條件, 資料庫鎖死的問題.
Impact of critical issues on releases
發行時有嚴重問題的影響. Major versions of Drupal core (like 7.0 or 8.0) won't be released until all critical issues are fixed. Drupal核心(7.0或8.0)不會發行, 除非所有嚴重的問題被解決.
For point releases of Drupal core (like 7.1 or 8.0.1), outstanding critical bugs will not necessarily hold up a core release. If there are 20 critical issues when 8.0.2 is released, and five of those are fixed, then it may make sense to release 8.0.3 with the other 15 critical issues open - or there may be a security release that has to go out anyway. 對於Drupal核心(如7.1或8.0.1), 很顯著的嚴重問題不需要去阻擋核心的發行. 假如在8.0.2發行時有20個嚴重的問題, 然後有5個在之後被解決了. 那就有一個很好的理由去發行8.0.3 - 即使還有15個嚴重的問題未解決 - 或者要有一個安全性的發行.
- In contributed projects, it is up to each maintainer how they handle the critical status. 在開源專案上, 維護人員可自行決定嚴重問題該如何去處理.
- Major (#)
- The major priority is used for issues that are not critical, but that do have significant impact or are important by community consensus. 當問題不是嚴重但有重大的影響或社群一致認為是重要的, 會將它標示為主要優先權。
These issues are prioritized in the current development release and backported to stable releases where applicable. 這些問題的優先順序
Major issues do not block point releases.
- Bug (#)
- Bugs that have significant repercussions but do not render the whole system unusable (or have a known workaround) are marked major.
Examples of major bugs:
- A non-fatal PHP error, or a PHP error triggered under rare circumstances or affecting only a small percentage of all users.
- Test failures in secondary environments (for Drupal 7 and 8 core).
- A bug that causes user input to be lost, but does not delete or corrupt existing data.
- Feature Request
- Examples of major features:
- providing a better UX for creating, editing & managing draft revisions.
- Bug (#)
- Bugs that affect one piece of functionality and are self-contained are normal priority. They do not impact the overall functionality of the software.
Examples of normal bugs:
- the category filter not working on the database log screen.
- Feature Request (#)
- Examples of normal feature requests:
- adding a "Create content type" link to the content listing page.
- Bug
- Examples of minor bugs:
- An incorrect class reference only in a comment.
Choosing the right priority
Each project's maintainer might have specific guidelines for that project. In the end, it is up to maintainer discretion to decide issue priorities.Feature requests are very rarely "critical". They should usually be "normal".
Support requests should never be marked "critical" or "major". (It remains possible in the UI though to handle contrib special cases.) If you believe you have run into a bug and it is preventing your site from working at all, post it as a bug report; however, be prepared for others to re-categorize it as appropriate. A higher issue priority is unlikely to give you better support; it is better to describe your issue thoroughly (with clear steps to reproduce it) to help people understand what is wrong.
沒有留言:
張貼留言