Closed
Description
There are a number of things I believe we need to do to bring this repo back to life for the community:
- Restore some kind of CI solution for continuous testing + validation against various versions of Mongo. I suggest GitHub Actions. We'll also need to decide which versions of Mongo and OTP will be "officially supported".Post CI, update developer / contributing docs so that devs can run the same tests (or a subset thereof) on a local machine.Merge in the latest PRs, especially Ecto 3 supporting work #364 which has the side effect of addressing some other reported issuesGo through the issues triage / close as neededGo through the other PRs, triage / close as neededAdd / revise a CONTRIBUTING.md document to let devs know how to get up and running to make changes
There is plenty to do but I'd like to keep this particular issue in the scope of "project revival". We can look at other issues, bugs, feature requests and so on as separate issues.
I'm happy to take on the GitHub actions + developer contributing instructions work.
Please suggest anything else you think might be needed!
Metadata
Metadata
Assignees
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Activity
scottmessinger commentedon Sep 16, 2021
These look awesome! If you could take the CI & dev contributing instructions, I can take care of getting the PRs merged in and triaging the issues/PRs!
joeapearson commentedon Sep 16, 2021
Thanks Scott. I realised we probably need to decide which versions of Mongo and OTP will be officially supported going forward. I suggest:
scottmessinger commentedon Sep 16, 2021
Those sound great to me! We're on Mongo 4.0.26 in production. We'll likely upgrade to 4.2 or 4.4 this winter.
As for Elixir, we're on OTP 23.2 and Elixir 1.11.4.
So, Mongo 4 and OTP v23 sound great and doable!
joeapearson commentedon Sep 16, 2021
Alright that sounds good. I suggest we don't go out of our way to deprecate older versions but users that need it will either need to use an older version of this package or "at your own risk".
ankhers commentedon Sep 16, 2021
fireproofsocks commentedon Sep 22, 2021
I'd like to help out here if possible. Given the target items listed above, is there any way to evaluate which tickets (new or existing) should be given priority treatment?
joeapearson commentedon Sep 27, 2021
@fireproofsocks excellent and yes please! I think best thing is for us to get a basic Ecto 3 support merged into master, we cut a beta release, and then we go to town on fixes / improvements and so on. Otherwise I think we're going to end up with a merge nightmare.
scottmessinger commentedon Sep 28, 2021
@fireproofsocks Awesome! I think the biggest need right now is to get our CI setup on github actions working -- is that right, @joeapearson ?
scottmessinger commentedon Sep 28, 2021
@joeapearson To coordinate, I created a project with everything I think we've listed so far.
https://github.com/elixir-mongo/mongodb/projects/1
I think we're good to cut a beta.1 release, no? Obviously, we need to do more to get this live, but since it supports ecto 3, seems like we can cut that release and start having people testing it. Let me know your thoughts!
joeapearson commentedon Sep 28, 2021
Excellent. Yes I think we want the CI in place ASAP so we can accept contributions with confidence. I'm working on it in #370 . At least two issues are going to fall out of that work. There are the other outstanding issues too, which are in varying states of repair themselves (some of them are very old and I'm not sure relevant any more). These need going through too.
6 remaining items