[syslinux] Dedicated pre-release? WAS: [PATCH 0/1] update gnuefi to f64cef26

Ady ady-sf at hotmail.com
Mon May 4 00:53:41 PDT 2015


> Due to the changes involved, this may warrant a dedicated pre-release.
 
I have seen very-generic suggestions stating that a certain issue with 
Syslinux might, perhaps, be attributed to using an outdated gnu-efi 
submodule when building Syslinux. Since the release of version 6.03, I 
have not seen any specific indication of any specific issue that could 
be attributed to an old gnu-efi code by itself.

That is not to say that the submodule should be kept outdated. It 
should certainly be updated. BTW, the "subject" of the prior email, 
corresponding to the original patch as it was sent, is already 
outdated.

With regards to deserving a pre-release, what about the rest of the 
pending-for-review patches?

What would be the point of a pre-release, when there are important 
maintenance patches not yet merged (or not even reviewed)?

Considering that some relevant known issues are still present, and that 
there are pending patches with the potential of resolving some of them, 
why a beta-tester would invest time on a pre-release?

I hope that the other pending-for-review patches would be actually 
reviewed. Whether they are "perfectly %100 correct and ready for 
merging as-is", or not so much, I hope that the issues that the pending 
patches are trying to improve would be actually improved. I hope, 
sooner rather than later. Then, a pre-release would be worth, IMHO.

In the mean time, having public access to official repositories with 
the commits already merged since v.6.03 might be helpful for some 
developers trying to collaborate with The Syslinux Project (and to some 
users / testers too). I don't know whether publishing a pre-release is 
simpler than (or independent of) providing public access to an updated 
official git repository.

Regards,
Ady.



More information about the Syslinux mailing list