1. Friendica has 4 possible release dates (02, 05, 08 and 11). So if we skip the .02 release, we should simply switch to the next one (.05). 2. I will adjust the deprecation messages from 2025.02 to the new release. So it would be nice to keep with this release so I don't have to change the messages again. 3. It takes the pressure off us. If we aim for April but aren't ready by early May, we'll have to release the 04 release in May (which feels wrong) or change the release to 05 (see reason above). But if we're ready by mid-April, it's very easy to just wait until May.
@Artur Weigandt traditionally we have a end-of-the-year release (12), 9, 6, 4 would make sense as well. the release in December is the only fixed release from the top of my head, all the rest is shuffled at will and as they are needed during the year.
@Tobias This complicates some things for me, especially for the deprecation messages. It would help me a lot if we would have specific release dates. So if we can come to an agreement that 04, 06, 09 and 12 would be the release months I would prefer 04 or 06 for the actual release. But to be really sure that we will be ready on time we should set the release to 06.
I guess this could be a longer RC phase, since there is so much new code. My hope is, that when the RC is forked, all developers will focus on fixing bugs then and pause developing on the develop branch.
Tobias
in reply to Artur Weigandt • • •Artur Weigandt likes this.
Michael 🇺🇦
in reply to Tobias • • •Artur Weigandt likes this.
Artur Weigandt
in reply to Tobias • •@Tobias Thank you very much. No offense, family and health is more important than the friendica roadmap. 🙂
What do you think about skipping the 2025.02 version and directly create a 2025.05-rc branch?
Friendica Developers reshared this.
Tobias
in reply to Artur Weigandt • • •Artur Weigandt
in reply to Tobias • •@Tobias
1. Friendica has 4 possible release dates (02, 05, 08 and 11). So if we skip the .02 release, we should simply switch to the next one (.05).
2. I will adjust the deprecation messages from 2025.02 to the new release. So it would be nice to keep with this release so I don't have to change the messages again.
3. It takes the pressure off us. If we aim for April but aren't ready by early May, we'll have to release the 04 release in May (which feels wrong) or change the release to 05 (see reason above). But if we're ready by mid-April, it's very easy to just wait until May.
Friendica Developers reshared this.
Tobias
in reply to Artur Weigandt • • •@Artur Weigandt traditionally we have a end-of-the-year release (12), 9, 6, 4 would make sense as well. the release in December is the only fixed release from the top of my head, all the rest is shuffled at will and as they are needed during the year.
But we can use May as well.
Artur Weigandt
in reply to Tobias • •Friendica Developers reshared this.
Matthias
in reply to Artur Weigandt • • •I still have problems with this bug and it's mean on the RC 🤕
github.com/friendica/friendica…
Michael 🇺🇦
in reply to Matthias • • •