THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
General project stuff:
- Gradle; Status update (Erick if I'm there, I have some commitments so the schedule is important).
- Short form: "we're ready to pull Ant out as soon as './gradlew eclipse' is in place. Volunteers?
- I encourage people to be using Gradle for everything and reporting problems while we still have ant to fall back on.
- Mark's beasting script is ant-based.
- I took a quick look and I think it can be changed to use Gradle, but haven't tried it. One possibility: assume I want to run 600 tests in 10 parallel sessions. Perhaps spawn 10 gradle tasks, each running 60 reps? This takes advantage of the work that Dawid did by adding iters (LUCENE-9465)
- Mike McCandless has his "stupid beasting" script ({{while(true) "./gradlew -p lucene test"}}
- Watch out, Gradle has a bug that can leave temporary files lying around that you have to manually clean up in some cases, see LUCENE-9468
- CI & Test status
- What are the "best practices" in an environment when CI is often failing?
- Developer Docs
- asciidoc: /dev-docs, /lucene/dev-docs, /solr/dev-docs. (Jan)
- Not sure what "belongs" in cwiki vs dev-docs
- Code reviews (David)
- We are doing more code reviews! Much appreciated.
- Communication channels: JIRA vs dev-list vs Slack vs IRC
...