I mean you can't demand that they fix every bug from every project the use somehow indirectly, even if only 2 people out of thousands have a use case with this.
It's not about fixing upstream bugs, is about warn users about possible issues due to removed features in your product. The entire pve kernel is a proxmox product, it's not a module, afaik.
And as everything IS open source and for example if you look at this here:
https://git.proxmox.com/?p=pve-kernel-2.6.32.git;a=summary the entry on the "2015-02-27" shows clearly without hiding anything, or silently dropping something, what happened. For sure, your right, a notification about something would be nice, but then we have a big pile of change logs somewhere linked which say exactly them same as the git commits (they do exactly what changelogs do, say what changed even better the state also why), and maybe also then some (for sure not a lot but) people would give proxmox shit if something doesn’t worked any more for them, even if it's clearly stated there.
I love pve, since years, use it professionally, have subscribed my servers, and Dietmar is my hero, really, I appreciate even more that he's personally posting on general forums, and not only on dev mailing lists.
They all are great developers, and they have (they always had) a vision, and that's why pve is unique and quite rock solid.
But, pve users, many of which also subscribers I guess, are now frequently pointed, in forum replies, to the git to know nearly everything changed. Otherwise, with new releases a sticky post appears, mostly about new great features, and that's the only source. Comments to those posts frequently ask many details about the release, because otherwise you have to dig into git. But git is for developers, not for users, imho.
At least the most important changes (apart from new great features, which everyone is happy to discuss about) should be mentioned somewhere: probably the wiki should have a dedicated page for every release changes (a sort of git changes summary, perhaps) even if it comes a few days later... obviously volunteers could contribute, on that wiki page, I am not saying pve staff should do everything. But they should keep an eye on those pages, if possible, to be sure people get right infos.
(That said, I am probably biased because I am also fond of another great FLOSS software (
Blender), which: has git, where you can find atomic changes to code, mailing lists and IRC to discuss most tech things.
For more general users, though, they also have an online manual, a wiki where, amongst other topics,*** every release ***, since its start, has a release log, quite detailed, and developers or others are maintaining those.
Everything is open to contributions for registered users. There's plenty of information suited to different kind of users, even those which are just evaluating the software.
Then, on their website, volunteers (and I am one of those, you can ask to volunteer) put release logs in a nicer shape and pictures, and with a summary, for less technical users or people just interested in what's new.
If a feature is removed, users are warned there, also. Quite different.)
A bit off topic,and I didn't what to call you out or something, but is often a bit easier to complain when your not thinking that there are people who work really hard behind some open source projects, and try to do their best.
I am not just complaining: I did something similar on pve wiki, about upstream changes on something that's quite important for pve: windows virtio drivers.
I created this page
http://pve.proxmox.com/wiki/Windows_VirtIO_Drivers/Changelog and I see that later someone else jumped in.
Can't something like that be done, by skilled enough people, for upstream changes but also for all (relevant) changes made from pve ?
Could it be useful?
Marco
