Release / Activity
!Friendica Developers
Hi :)
I made some PRs and noticed that we're way over schedule (2025.02) for a next release. Shall we introduce the RC branch for a release like 2025.06 ?
A second thing is that it feels like @Artur Weigandt is currently very active in refactoring parts of the code (thanks!) but it seems like our overall responsiveness decreases more and more. That's sad, but I know from myself that there's a lot to do outside of Friendica ;)
Friendica Developers reshared this.
Michael 🇺🇦
in reply to Philipp Holzer • • •Philipp Holzer likes this.
Philipp Holzer
in reply to Michael 🇺🇦 • •Oooohh India sounds nice :) hope you enjoyed it!
As said we all have a life beside Friendica, and a trip to India sounds like a good alternative :D
Friendica Developers reshared this.
Michael 🇺🇦
in reply to Philipp Holzer • • •Philipp Holzer
in reply to Philipp Holzer • •Friendica Developers reshared this.
Michael 🇺🇦
in reply to Philipp Holzer • • •Philipp Holzer likes this.
Philipp Holzer
in reply to Michael 🇺🇦 • •@Friendica Developers
Hi :)
I think we should fokus on possible major issues for a release. @Tobias would it be possible for you somewhere in the near future to help creating the release?
@Michael 🇺🇦 / @Artur Weigandt what do you say?
Friendica Developers reshared this.
Wilhelm
in reply to Philipp Holzer • • •Expected delay due to @Michael 🇺🇦 s absence.
What I would love to see is another stab at moving to Forgejo: github.com/friendica/friendica… as the issues seen on first attempt should (TM) be resolved. At least OrganicMaps had done the switch with similar number of issues: git.omaps.dev/organicmaps/orga…
Using Forgejo may also increase chances of bookface being merged into core: gitlab.com/randompenguin/bookf…
For backup redundancy GitHub could serve as mirror.