I have great news: I created items for the release in our bugtracker!
Here is a parent issue “Release v1.3” https://ticket.coreboot.org/issues/353
and it has 23 subtasks. The subtasks are the items from the original starter email. Thank you so much Nico for going through the long history and making the list, that’s a lot of work and time!
The very good thing is that now the big task is trackable, parallelizable and open to anyone who can join the effort.
I looked into commits and gerrit reviews that correspond to those, I tried to get some context. Surely all of the descriptions can be improved, or more info can be added to issues. Especially if you are taking an issue and start working on it.
Also, of course, more tasks can be added, if something is missing. Please set the parent issue #353, category “Release prep” and target release 1.3 if you add a new task.
I assigned the parent issue to myself. Please tell me if anyone has objections. I did it because at the last dev meeting the community decided that I will be “release manager”. It was completely unexpected for me, but it is true to say that I very much want the release to happen.
I really appreciate any help and advice from people!
As a separate note, the question of meson and make has been discussed in this thread. And we now have a One Build System working group with the goal to converge two flashrom build systems into one (meson). Here is the doc with more info
. Everyone who is interested in contributing to the effort can join! This effort goes in parallel with release prep.
I haven’t done any releases before, so tell me if I am wrong. But what I am thinking when looking at the list of issues: maybe we can have some time for “just fixing issues on master” and after that do a release branch? Does it make sense?
“Some time” won’t take forever (AU winter maybe?). I have issue #353 assigned to me, so now it has to happen :)