Gerald Pfeifer wrote: <snip>
One idea I had reading this thread is to establish a list of packages/ components that shall explicitly and transparently be considered for an update with every point release. <snip> That still requires volunteers to do the actual work (like you described above); it does help us keep things on the radar, documents decisions, and in turns supports timely and transparent discourse.
What do you think?
Gerald
IMHO, this is a great idea. Speaking as someone fairly new to SUSE/openSUSE, I think that doing this will make contributing back to the project a bit easier. Often, when I look at Leap/SLE packages in the main repos, and some of them are out-of-date to a various degree, I am not sure if that's on purpose (kept on some version because the project that depends on it breaks with more recent one, or more recent library/application version breaks API/ABI, or something else outlined in the maintenance policy), or the update is on developers/maintainers huge TODO list, but they didn't get to it yet :) As for doing the work, that's, for the most part, pretty straightforward(and there are helpful souls on factory/OBS IRC channels that patiently answered my stupid questions/gave tips/clarified things and procedures). After being given access to something as awesome as b.o.o, it's only fair to give something back, to the best of my (and my potato PC) abilities, and I am fairly sure I am not the only one thinking that :) And having a list like this would certainly help with contributing back. Pedja