Dear SeaBIOS folks,
with the latest NVMe fixes, would it make sense to tag a 1.15.1 release?
The 1.16.0 release is planned for end of February, as far as I understand it. Maybe that could be moved up two weeks?
Kind regards,
Paul
On Thu, Jan 27, 2022 at 05:43:32PM +0100, Paul Menzel wrote:
Dear SeaBIOS folks,
with the latest NVMe fixes, would it make sense to tag a 1.15.1 release?
The 1.16.0 release is planned for end of February, as far as I understand it. Maybe that could be moved up two weeks?
Going straight to 1.16.0 looks more useful to me. I don't feel like rushing a 1.15.1 release with patches commited only yesterday, also there are lots of fixes so a 1.15.1 would have a rather big portion of the patches in master cherry-picked.
take care, Gerd
On Fri, Jan 28, 2022 at 01:03:23PM +0100, Gerd Hoffmann wrote:
On Thu, Jan 27, 2022 at 05:43:32PM +0100, Paul Menzel wrote:
Dear SeaBIOS folks,
with the latest NVMe fixes, would it make sense to tag a 1.15.1 release?
The 1.16.0 release is planned for end of February, as far as I understand it. Maybe that could be moved up two weeks?
Going straight to 1.16.0 looks more useful to me. I don't feel like rushing a 1.15.1 release with patches commited only yesterday, also there are lots of fixes so a 1.15.1 would have a rather big portion of the patches in master cherry-picked.
That makes sense to me.
To the original question - I don't see moving up the v1.16.0 release. Indeed, if we continue to see bug reports then we may have to push it back. (Though, end of February still seems reasonable at this time.)
-Kevin
-
Gerd Hoffmann -
Kevin O'Connor -
Paul Menzel