Closed sarumpaet closed 6 years ago
As long as some developers are interested in working on a release, this might work.
'''To have a process that is a bit more transparent than the last release (Hedy-1.0.0), we should coordinate the Hedy-1.0.1 release here and release it only once several developers agreed, and all Hedy-1.0.1 blocker issues are resolved.
To me it seemed transparent as it was already announced on the berlin freifunk ml. Since there was no reaction vetoing a release, to me nothing looked like being wrong.
What does a blocker help, when only very few ppl are active in developing a new version? Getting more time to wait for a new release? I like coordinated work as well but it would be nice if some are coworking.
We had issues like this before, see https://github.com/freifunk-berlin/firmware/issues/367 , and this worked fine for coordination, and it increased transparency and communication between developers. We also had hackathons previously which were good for teamwork. I set up a Doodle - perhaps we manage to get together again this time (link see list).
I think the branch Hedy-1.0.1 is good to provide the migration from 0.3.0 -> 1.0.1 and 1.0.0 -> 1.0.1. The individual software-versions are not changed and are the same as in 1.0.0 release.
I called the mailinglist for testers (https://lists.berlin.freifunk.net/pipermail/berlin/2018-May/037667.html)
I think https://github.com/freifunk-berlin/firmware/pull/566 should be cherry-picked to 1.0.1 as well since it fixes a regression.
As per https://github.com/freifunk-berlin/firmware/milestones hedy-1.0.1 was alway planned to used the same code as Hedy-1.0.0, but have a working migration for previous releases - not more not less.
IF we start thinking of regressions and security-fixes and ..., we will end up in much more changes. But this is all planned for Hedy-1.0.2.
Doing such a small release nearly costs anything, and I'm sure, the users will handle the shock, when there are multiple releases within a year. Gluon-users also do.
Everything is tested and functioning, we should release. I will unblock now.
Re https://github.com/freifunk-berlin/firmware/pull/566 (not) in 1.0.1 - I'd just release fixes as they become available but whatever. 1.0.1 go! I created https://github.com/freifunk-berlin/firmware/pull/568 for 1.0.2.
closed, as Hedy-1.0.1 has been released
To have a process that is a bit more transparent than the last release (Hedy-1.0.0), we should coordinate the Hedy-1.0.1 release here and release it only once several developers agreed, and all Hedy-1.0.1 blocker issues are resolved.