Wine-Staging 3.21 Released With A Handful Of New Patches

[oiaohm]

What? Dmitry wasn't a wine-staging maintainer. You're smoking something good again. You really love making stuff up don't you?

I also clearly advised you to read that whole thread, if needed (which obviously is needed for someone with your brain capacity). Codeweavers also didn't hire the wine-staging maintainers back then either. Again, "unproven bullshit" as always.

Dmitry was maintaining particular patches going into staging. So was Stefan Dösinger who is code weavers who was working on CSMT this is back in 2014 to 2017. Yes codeweavers developers were maintaining and fixing patches in staging well before that blow up and well after as a place to test patches that in time would be merged into wine mainline.

End of 2017 start of 2018 majority of those patches get merged into mainline at this point the codeweavers developers no longer have a reason to be fixing staging its not like fixing staging will bring them the test results they need.
Sebastian Lackner the head maintainer of staging at that point gets left holding the bag of patches that he had allowed to be dumped on him and then quit.. Problem was Weasel that complete thread is from 2015. Everything in that thread has been fairly addressed and was addressed by the end of 2015. Include how you should rework other people patches. The way Sebastian Lackner did patch rewrite in 2015 was bad by method used created a unclear copyright.

Weasel if you read though that thread carefully you will find some classic setup goofs.

https://www.winehq.org/pipermail/wine-devel/2015-June/108107.html

Bugzilla admin email alias was in fact fairly much pointing to void and no one reported issues until then. Yes void fairly the complete time wine had been using bugzilla up until mid 2015. Like the fedora email account over legal stuff. So yes wine staging part comes out of processes in wine being broken. But here is the big thing until the 2015 blow up most of the broken parts of wine development process were not being reported. Alex was getting quite annoyed before the blow he was sure there had to be other problems. Like Alex was the one who wrote the patch tracking system over 12 months of operations by mid 2015 and not a single complaint at that point. 0 complaints is abnormal someone hates something about even the most perfect interface. Weasel it takes two to tango. If things are not working right and no one report the problem the problem cannot get fixed. Wine staging comes out of issues on both sides. Worst one is that fact people attempting patches were running into issues with the development system then failing to report those issues. The new maintainers working on staging and even some of the patches coming in from valve are not running into the problems developers were hitting back in 2015 and before. Yes Sebastian Lackner accepting patches from developers with no interest in mainlining or maintaining the patches is what left him holding a impossible to maintain set of patches. Wine bugzilla maintainers deleting wine staging reported bugs was party because lot of patches allowed in wine staging were abandoned with no developer to refer problem to. Weasel remember I said those problems were mostly handled in sep 2015. https://wiki.winehq.org/WineConf2015 Yes that is the Wine Conf 2015 process debate. Weasel point to 2015 to make a point is pointless when what you are pointing caused major changes to wine project operations.

[Weasel]

Dmitry was maintaining particular patches going into staging. So was Stefan Dösinger who is code weavers who was working on CSMT this is back in 2014 to 2017. Yes codeweavers developers were maintaining and fixing patches in staging well before that blow up and well after as a place to test patches that in time would be merged into wine mainline.

End of 2017 start of 2018 majority of those patches get merged into mainline at this point the codeweavers developers no longer have a reason to be fixing staging its not like fixing staging will bring them the test results they need.

You have no idea what you're talking about. You're like those old ladies who love to gossip and it's all they can do.

I suggest you to read Dmitry's last paragraph again before you spout more nonsense about Codeweavers.

[oiaohm]

You have no idea what you're talking about. You're like those old ladies who love to gossip and it's all they can do.

I suggest you to read Dmitry's last paragraph again before you spout more nonsense about Codeweavers.

I suggest you go speak the the current 3 maintainers of wine staging branch. They are mainlining a lot of patches these days. Everything Dmitry talks about no longer applies at all.

You will find even that the 3 maintainers are not part of codeweavers they have direct contact with may other code-weavers staff for review and feedback information when up-streaming patches.

https://wiki.winehq.org/WineConf2015

I suggest you read up on Wine Conf 2015 notice that wine staging was introduced and processes were changed.

https://wiki.winehq.org/images/8/8d/Wine-Staging-Introduction.pdf

Yes WineCon2015 Dmitry's issues and others were addressed Sep 2015 Wine Conf. Yet you idiot Weasel brought some something that has been corrected.

What is the problem with wine staging now is really the back log that has to be cleared. 2015 there was a issue raised about the growing number of patches in wine staging at wine conf 2015 that were not progressing forwards with the forecast that this would at some point come unmaintainable what it did end of 2017.

The green curve on the last slide showing the increasing rate of wine upstream successfully processing patches. This leads to the current state that a patch submitted to wine is normally reviewed in under a day now. Yet when you go back to when staging started it could take a month or two to get a review. Even in 2015 it was over a month at times to get patches going into wine reviewed.

The process problems that created staging have been mostly solved.

Dmitry these days directly submits to wine mainline. 2015 he would submit stuff to wine staging first. The slow review process that annoyed Dmitry was started to be fixed by end of 2015 and it only got better since.

Codeweavers staff helping out staging stopped 2017. Those staff now review more submitted patches mainline.


You have no idea what you're talking about.
Weasel in this case you have no idea what you are talking about. You have not consider that that 2015 blow up was major talking point at that years Wine Conf or that it was dealt with.