Remove delay comment in PR template because we've been merging PRs (#243)

* Remove delay comment in PR template because we've been merging PRs.

* Add readme.md note, and change "CI" to "automated testing" in checklist.

* Also remove statement from readme.md.
This commit is contained in:
Billy O'Neal 2019-10-31 18:39:31 -07:00 коммит произвёл GitHub
Родитель 1d094330aa
Коммит 389066634b
Не найден ключ, соответствующий данной подписи
Идентификатор ключа GPG: 4AEE18F83AFDEB23
2 изменённых файлов: 5 добавлений и 5 удалений

Просмотреть файл

@ -41,7 +41,7 @@ yet hardened it against untrusted changes.
conventions, Standard requirements, Microsoft-specific requirements, binary compatibility (ABI) requirements, and more.
We're eager to begin accepting features and fixes from the community, but in addition to setting up a CI system, we need
to write down all of the rules that are currently stored in our brains. (The ABI rules may be useful to other C++
libraries.) Until that's in place, pull request reviews will be delayed.
libraries.)
* Issues: **In progress.** We're going to use GitHub issues to track all of the things that we need to work on. This
includes C++20 features, [LWG issues][], conformance bugs, performance improvements, and other todos. There are

Просмотреть файл

@ -4,15 +4,15 @@
# Checklist
Be sure you've read README.md and understand the scope of this repo.
If you're unsure about a box, leave it unchecked. A maintainer will help you.
- [ ] I understand README.md. I also understand that acceptance of
community PRs will be delayed until the test and CI systems are online.
- [ ] Identifiers in product code changes are properly `_Ugly` as per
https://eel.is/c++draft/lex.name#3.1 or there are no product code changes.
- [ ] The STL builds successfully and all tests have passed (must be manually
verified by an STL maintainer before CI is online, leave this unchecked for
initial submission).
verified by an STL maintainer before automated testing is enabled on GitHub,
leave this unchecked for initial submission).
- [ ] These changes introduce no known ABI breaks (adding members, renaming
members, adding virtual functions, changing whether a type is an aggregate
or trivially copyable, etc.).