Open rinav opened 3 years ago
Hi @rinav,
we plan to release new version of the library early next year.
@zplesac Would you mind making a release?
Hi @mtrezza , unfortunately, the maintenance branch isn't fully ready for the release, especially since it's been over a year since it was last worked on. We don't yet have a set timeline for the update.
What is needed? Maybe we could find contributors who would give a hand?
That's a part of the problem 🙂 we need to take a good look at the current state of the 3.0.0 version update, test it out, and assess what still needs to be resolved. We would also like to revisit some existing features and see whether they make sense in the current state of Android or if they're easily replaceable with a native solution (meaning - there's no sense to keep a custom implementation in the library). Finally, we should make another round of dependency updates, including targeting API 31 and likely raising the minimum SDK version (to either 21 or 24, the current 19 is highly outdated).
Would you mind writing these tasks in a roadmap in a new issue, maybe try to break them down further into separate tasks? Then we can see if we find people here who could tackle these smaller chunks.
I created a 3.0.0 milestone: https://github.com/infinum/android_connectionbuddy/milestone/15
I also opened some tasks/issues. Unfortunately, I don't see a very good way of breaking those into chunks, as it's mostly investigative work. Suggestions are welcome.
I think it comes down to whether there is a community that can look into these questions, or whether you can. I don't see a lot of community activity, so maybe try to pin an issue or post on a social media channel that help is wanted. Otherwise, if you cannot look into these questions, should this library maybe considered unmaintained or possibly be archived? It seems from the commit history that you are the main / only contributor?
The library is officially still maintained by the Infinum organization, which I am a part of. We want to do the investigative work at some point for sure, after which we can decide whether it makes sense to put in the effort to maintain the library or not. I just can't promise the exact date until which it will happen.
Will there be a new release since there was a major refactoring and maintenance changes in
maintenence-update
branch