[coreboot] release engineering process

Kevin O'Connor kevin at koconnor.net
Fri Nov 7 05:33:26 CET 2014


On Thu, Nov 06, 2014 at 07:57:23PM +0100, Patrick Georgi wrote:
[...]
> With that in mind, I want to throw out some ideas:
> 
> * Let's have regular release cycles. maybe quarterly, eg in the
> middle of each quarter (that is, feb 15, may 15, aug 15, nov 15) to
> avoid certain vacation-heavy periods.

Just my $.02, but I think having regular coreboot releases would be a
very good thing.

[...]
> IMHO this gives us a couple of advantages over the current non-process:
> It gives us the opportunity for exposure to the world since releases tend to draw some media attention.
> And it may encourage some more focussed testing (on board-status) than the current approach, which may increase participation - having your port listed as working on the 2015.08 release notes is a bigger incentive than some green box on some obscure wiki-page.
> We can point people to certain revisions with more confidence (and with a nicer name than a SHA1 of a random tree), which will make vendors' lives easier (and in combination with that media exposure, also community support on #coreboot and the list when people ask what revision to use).
> 

Very well said.

-Kevin



More information about the coreboot mailing list