DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
Date
Notification thread
https://lists.apache.org/thread/6fyfbjp9tj4zk9gmjmz2rsq4s54xhmd4
Meeting Link
https://meet.google.com/mzq-iwcc-xvw
Attendees
- Jason Gerlowski (Organizer)
- Andrey Ukhanov
- Bruno Roustant
- Carlos Ugarte
- David Smiley
- Eric Pugh
- Houston Putnam
- Jan Høydahl
- Jude Muriithi
- Ken LaPorte
- Luke Kot-Zaniewski
- Matthew Biscocho
- Mikhail Khludnev
- Nazerke S
- Pierre Salagnac
- Sanjay Dutt
- Yuntong Qu
Discussion Topics
- (David) Solr 10 on the horizon
- Roadmap
- Jira issues (major changes, breaking changes, deprecations)
- List of Jira issues will continue to expand until there is consensus to start Solr 10 build
- (Jason) Solr Operator Community Discussion (5m)
- Where does the discussion take place? (user questions, issues, discussions)
- Right now it seems to mostly happen on Github issues
- Established practice
- Makes it easily searchable
- Other Apache projects have switched mailing lists to forums. Should we do that to users mailing list?
- (Eric) C/C Long Range Planning?
- Scheduled for November in North America
- C/C will alternative between North America and EU every year
- We would love to have more Solr presence and dedicated Solr track
- (Nazerke) Solr Social Media Presence
- Solr channel on LinkedIn
- There is currently a private channel
- Can it be made public?
- Post announcements, releases, and blog posts
- OpenSearch channel
- Next steps
- Contact admins of current private group
- We can create a group with disclaimer that it's run by users of Solr, not PMC. All project decisions must be made on the dev mailing list
- Add a step to release process to share on LinkedIn group in addition to the blog post
(Jason) Solr 9.8 Release Vote Reminder
- First RC for 9.8 was shared with a vote thread
- One does not have to be committer or PMC member to vote on the RC
- Mailing list thread
(David) CHANGES.txt generation via logchange – SOLR-17619 - Getting issue details... STATUS
- Instead of changing common CHANGES.txt, the tool has a CLI to generate a small YAML file
- No merge conflicts!
- Release manager will generate CHANGES.txt from that