HowToWriteAnIssue

Kay-Uwe Janssen edited this page Apr 13, 2017 · 3 revisions

Please note GitHub issue tracker is not a user support forum, we discuss development here. If you have questions about just using AA, please go to our mailing list or stackoverflow.

Bug reports should be...

...Clear

Bug reports should have:

  • Precise, descriptive summaries.
  • Informative, concise descriptions.
  • A neutral tone, avoiding complaints or conjecture.

...Reproducible

Bug reports should contain:

  • The simplest steps to reproduce the issue, or...
  • A failing test fixture for the bug.

...Specific

Only publish one bug per report accompanied by:

  • A detailed description of the issue focusing on the facts.
  • Expected and actual results.
  • Versions of software, platform and operating system used.
  • Crash data, including stack traces, log files, screenshots and other relevant information.

...Unique

Please search for duplicates before reporting a bug and ensure summaries include relevant keywords to make it easier for others to find duplicates.

Feature requests should contain...

  • Description of the feature
  • List and usages of the new annotation(s)
  • Examples of the generated code

14/10/2018 The 4.5.1 release is out !

Using AndroidAnnotations

Questions?

Enjoying AndroidAnnotations

Improving AndroidAnnotations

Extending AndroidAnnotations

Clone this wiki locally
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.