Future of kexec-tools-testing
Subsystems (2)
Hi,
SUSE uses now kexec-tools-testing releases since about one year and we never had severe problems (compared to other software). It's well maintained (thanks Simon!), gets frequent releases, patches are accepted, so:
- I would suggest that kexec-tools-testing could be renamed to kexec-tools somewhere in the future since kexec-tools is not maintained any more by Eric. It only causes confusion since some distributions still use kexec-tools (the original ones) with lots of patches.
I think current IA64 versions even do not work with kexec-tools since there were some incompatible changes related to the position of ELF core headers.
- I would suggest that kexec-tools gets normal release numbers. The date releases are quite bad for package managers since it's not possible to go back (in terms of a clean update path) from something like 20080101 to 1.5 since 2008 is always greater.
Currently SUSE ships still the old 1.101 version and the real release is only visible in the changelog. Of course it's possible to do something like 1.101+20080101, but it's nasty.
If I could help out doing some work to help to get that done, then just tell me.
Bernhard
Signature · 6 lines
Bernhard Walle, SUSE LINUX Products GmbH, Architecture Development _______________________________________________ kexec mailing list [email protected] http://lists.infradead.org/mailman/listinfo/kexec
Quoted 7 lines · Bernhard Walle
Hi,
SUSE uses now kexec-tools-testing releases since about one year and we never had severe problems (compared to other software). It's well maintained (thanks Simon!), gets frequent releases, patches are accepted, so:
Quoted 5 lines
- I would suggest that kexec-tools-testing could be renamed to kexec-tools somewhere in the future since kexec-tools is not maintained any more by Eric. It only causes confusion since some distributions still use kexec-tools (the original ones) with lots of patches.
I agree.
Perhaps we could make the next release kexec-tools 2.0.0, perhaps after a few beta releases?
I can rename my git tree to coincide with this move.
Quoted 3 lines
I think current IA64 versions even do not work with kexec-tools since there were some incompatible changes related to the position of ELF core headers.
Yes, I think you are right.
Quoted 8 lines
- I would suggest that kexec-tools gets normal release numbers. The date releases are quite bad for package managers since it's not possible to go back (in terms of a clean update path) from something like 20080101 to 1.5 since 2008 is always greater.
Currently SUSE ships still the old 1.101 version and the real release is only visible in the changelog. Of course it's possible to do something like 1.101+20080101, but it's nasty.
That is fine by me. But we may as well rename the package to kexec-tools at the same time.
Quoted 2 lines
If I could help out doing some work to help to get that done, then just tell me.
You're already helping a lot.
Perhaps the best thing to do now would be to hash out a release roadmap. Fortunately the code is pretty small, so it shouldn't be a very long road.
Do you think there is anything currently missing from the tree? If not, I can make a beta release early next week (I have to leave my desk for an extended weekend shortly).
Signature · 7 lines
Horms _______________________________________________ kexec mailing list [email protected] http://lists.infradead.org/mailman/listinfo/kexec
Quoted 13 lines · Simon Horman
Quoted 11 lines · Bernhard Walle
SUSE uses now kexec-tools-testing releases since about one year and we never had severe problems (compared to other software). It's well maintained (thanks Simon!), gets frequent releases, patches are accepted, so:
- I would suggest that kexec-tools-testing could be renamed to kexec-tools somewhere in the future since kexec-tools is not maintained any more by Eric. It only causes confusion since some distributions still use kexec-tools (the original ones) with lots of patches.
Quoted 4 lines
I agree.
Perhaps we could make the next release kexec-tools 2.0.0, perhaps after a few beta releases?
Sounds reasonable.
Quoted 1 line
I can rename my git tree to coincide with this move.
I think the name of the git tree is not that important, but it makes also sense to rename that. Since there is no "kexec-tools" tree anyway.
Quoted 6 lines
Perhaps the best thing to do now would be to hash out a release roadmap. Fortunately the code is pretty small, so it shouldn't be a very long road.
Do you think there is anything currently missing from the tree? If not, I can make a beta release early next week (I have to leave my desk for an extended weekend shortly).
No, the current state is fine for me (from a functional point of view). So, just release kexec-tools-2.0.0-rc1 next week. I think we don't need alpha and beta versions here.
I'll help to test that release then (by updating SUSE/Factory :-)).
I think we don't need changes in the release policy because it worked out fine in the past. And when 2.0.0 is out, I think then also all other major distributions like Debian, Fedora, etc. update to that release and drop their patches.
Thanks a lot for your effort!
Bernhard
Signature · 6 lines
Bernhard Walle, SUSE LINUX Products GmbH, Architecture Development _______________________________________________ kexec mailing list [email protected] http://lists.infradead.org/mailman/listinfo/kexec