Thank you very much, Evgeny, and luckily I could see your additions
here: https://piratenpad.de/p/coreboot4.10-release-checklist
( https://review.coreboot.org/cgit/board-status.git/log/ - Lenovo T420
, Lenovo X200 , Lenovo X220 , Lenovo T530 baseboard )

On Sun, Jun 2, 2019 at 11:12 PM Evgeny Zinoviev via coreboot
<[email protected]> wrote:
>
> Your plan worked, I've just uploaded board status for 4 more boards.
>
> On 6/2/19 9:26 PM, Mike Banon wrote:
> > I've just added a "Recently tested mainboards:" section to the end of
> > https://piratenpad.de/p/coreboot4.10-release-checklist . I think its'
> > existence could encourage the people to submit a board status report
> > for their board, to increase its' visibility and attract more
> > potential users/developers who'll read these release notes at some
> > opensource-dedicated websites and may become interested at coreboot
> > project. This section includes 6 laptops and 2 desktops for which the
> > board status reports have been submitted during May and the beginning
> > of June. Luckily 4.10 release is not there yet, so the people still
> > have some time to submit a fresh board status for their board and then
> > it could be included to this list.
> >
> > Also, regarding the significant changes: " ### Tianocore UEFI
> > integrated as payload " . I hope it doesn't mean that Tianocore will
> > become the default payload, since there are ideological/technical
> > reasons against this ( I think there's a significant overlap between
> > the groups of people who love / interested in coreboot and hate UEFI )
> >
> > Recently tested mainboards:
> > ---------------------------
> > * Lenovo Ideapad G505S
> > * Lenovo Thinkpad T400
> > * Lenovo Thinkpad T430
> > * Lenovo Thinkpad T430s baseboard
> > * Lenovo Thinkpad X131e Chromebook
> > * Lenovo Thinkpad X230
> > * Gigabyte GA-B75M-D3H
> > * Asrock E350M1
> >
> > On Fri, May 10, 2019 at 11:17 PM Patrick Georgi via coreboot
> > <[email protected]> wrote:
> >> Hi everybody,
> >>
> >> with this mail I'm officially starting the 4.10 release process.
> >> As per the first step of our checklist 
> >> (Documentation/releases/checklist.md), I hereby announce the intent to 
> >> release coreboot 4.10 in about 2 weeks. I'm aiming for May 28th to avoid 
> >> releasing into the weekend or on Memorial Day in the US, but I'll likely 
> >> lock down the commit we'll designate 4.10 during those days to give some 
> >> room for testing.
> >>
> >> I created a copy of the checklist on 
> >> https://piratenpad.de/p/coreboot4.10-release-checklist, also including the 
> >> current state of the 4.10 release notes.
> >>
> >> Please test the boards you have around and provide fixes, please be 
> >> careful with intrusive changes (and maybe postpone them until after the 
> >> release) and please update the release notes 
> >> (Documentation/releases/coreboot-4.10-relnotes.md or near the bottom of 
> >> the etherpad doc, I'll carry them over into our git repo then).
> >>
> >> As promised with the 4.9 release there won't be deprecations after 4.10. 
> >> However we need to finalize our set of deprecations we want to announce 
> >> with 4.10 that will happen after the 4.11 release (those also belong in 
> >> the release notes).
> >>
> >>
> >> Regards,
> >> Patrick
> >> --
> >> Google Germany GmbH, ABC-Str. 19, 20354 Hamburg
> >> Registergericht und -nummer: Hamburg, HRB 86891, Sitz der Gesellschaft: 
> >> Hamburg
> >> Geschäftsführer: Paul Manicle, Halimah DeLaine Prado
> >> _______________________________________________
> >> coreboot mailing list -- [email protected]
> >> To unsubscribe send an email to [email protected]
> > _______________________________________________
> > coreboot mailing list -- [email protected]
> > To unsubscribe send an email to [email protected]
> _______________________________________________
> coreboot mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
_______________________________________________
coreboot mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to