CE v2.1.2 bugs and slow or no responses from forum/github

[Rick Whitehead]

Dear Alan,
Please forgive any negative undertones to this post, it's not typical of me but I'm losing the will.
I've been experiencing a show stopper bug now for months without resolve. It's listed on mag2 Github https://github.com/magento/magento2/issues/4184 with some replies and confirmations from other users/contributors but the issue has relatively recently been marked closed and fixed with no actual signs of the fix materialising? - and no answers to my questions for the last number of weeks or at all? This is typical in my experience to-date  
I've been experimenting (theming/subtheming & module writing) with M2 now since the supposed stable CE versions were released. But my reality is that listing github issues appears to be completely wasted time and that I'd be better off hacking core myself or choosing an alternative truly stable platform for e-commerce. 
I'd be delighted to hear how I can have actual real time communication with maintainers/contributors in order that I retain the teeniest bit of sanity I have left, and so that I may actually obtain a fix for this bug and no doubt help the community fixing others when I find them, which I undoubtedly will - if I'm still bothering with Magento that is.
kind regards
Rick

[akent99]

I am doing some internal digging to work out what happened to this ticket. Feel free to harass me in a few days if someone has not responded by then. 

[Rick Whitehead]

Thank you very much.

[Rick Whitehead]

Dear Alan,
Harassing as advised.

[akent99]

The person I had lined up to respond got swamped unexpectedly - trying to track down someone else to look into the issue you reported. I found the internal issue, but did not completely understand its history. So I am calling in an expert!

So sorry for delay, but not forgotten.

[Rick Whitehead]

Hi Alan,
Thank you. I do hope you can provide some useful feedback for me asap.
As I've said, I'm happy to investigate myself but there's no point in doubling up if it's already being looked at - other than if this is my only hope of a solution.
I look forward to hearing from you soon.
Kind regards
Rick

[Anton_Kril]

Hi Rick,

I've replied in Github thread. Internal issue number was provided for you to be able to track issue progress by commit messages. But I agree that it's hard to do it on GitHub.

I'll raise the internal discussion about more informative Github issue resolution messages.

[Rick Whitehead]

@antonkril @alankent?

I'm trying to patch v1.1.2 to test this fix https://github.com/magento/magento2/issues/4184. And this list of 7 related commits is only changes from current dev branch not current stable release [v1.1.2]. So we/I have no easy way to track when/why a change has occured wthout tracing parent commits?

Please advise why on the develop branch the vendor code is in  /app/code/Magento ?

kind regards

Rick

[akent99]

That is unrelated to this thread, but GitHub holds the master code for the project. At release time, we go through a publish process that creates Composer packages from our code base. When a merchant creates a site, we recommend using Composer, which will download the code and put under vendor.

One way to think about it is "code under vendor is 3rd party code - not code I should be editing in my project". So when using our GitHub repo, you are working on the core (not on a merchant site), so our code is not under vendor there. When you build a merchant site, our code is not yours - you should not touch it - you do not commit to git etc - and so it goes under vendor.