diff options
| author | Matt Davis <nitzmahone@users.noreply.github.com> | 2018-05-22 01:14:53 +0200 |
|---|---|---|
| committer | Matt Clay <matt@mystile.com> | 2018-05-22 01:14:53 +0200 |
| commit | e4edb2842a8816a3eed596aea1c28aa769a31e9d (patch) | |
| tree | 6e1407782d7a1360345e078a4cee7808d365002a /hacking/ticket_stubs/thanks.md | |
| parent | Ios test fixes (#40503) (diff) | |
| download | ansible-e4edb2842a8816a3eed596aea1c28aa769a31e9d.tar.xz ansible-e4edb2842a8816a3eed596aea1c28aa769a31e9d.zip | |
2.6 changelog gen/version/root dir cleanup (#40421)
* patched in changelog gen stuff from stable-2.5
* Makefile updates
* release.py as single-source-of-truth
* Remove obsolete ansible-core-sitemap.xml file.
* Move ROADMAP.rst into README.rst.
* dynamic rpm changelog, zap old deb/rpm changelogs
* fix changelog in MANIFEST.in
* Remove obsolete hacking/update.sh script.
* Remove ref to deleted authors script.
* Remove ref to removed module-formatter script.
* Update headings to match script names.
* MANIFEST.in cleanup
* removed RELEASES.txt and versions.yml
* removed obsolete release generation playbook/bits (not used since 2.5)
* misc Makefile cleanup
* speculative changes to DEB versioning
* allow override of DEB_VERSION/DEB_RELEASE
Diffstat (limited to 'hacking/ticket_stubs/thanks.md')
| -rw-r--r-- | hacking/ticket_stubs/thanks.md | 21 |
1 files changed, 21 insertions, 0 deletions
diff --git a/hacking/ticket_stubs/thanks.md b/hacking/ticket_stubs/thanks.md new file mode 100644 index 0000000000..646571d568 --- /dev/null +++ b/hacking/ticket_stubs/thanks.md @@ -0,0 +1,21 @@ +Submission Received +=================== + +Hi! + +Thanks very much for your submission to Ansible. It sincerely means a lot to us. + +Just as a quick reminder of things, this is a really busy project. We have over 800 contributors and to manage the queue effectively +we assign things a priority between P1 (highest) and P5. + +We may also ask some questions and it may be a while before we can get to this, but we'd like to thank you very much for your time! +We'll work things in priority order, so just wanted you to be aware of the queue and know we haven't forgotten about you! + +We will definitely see your comments on this issue when reading this ticket, but may not be able to reply promptly. You may also wish to join one of our two mailing lists +which are very active: + + * https://groups.google.com/forum/#!forum/ansible-project - for user questions, tips, and tricks + * https://groups.google.com/forum/#!forum/ansible-devel - for strategy, future planning, and questions about writing code + +Thank you once again for this and your interest in Ansible! + |