3 ms·
You have misunderstood, the latter refers to "download the .php files, 'require' them", which is the situation you say exists right now. I'm going to leave thi
by heurisko 5y ago
You have misunderstood, the latter refers to "download the .php files, 'require' them", which is the situation you say exists right now.
I'm going to leave this by saying that I think the idea that you can make developers more conscientious by increasing busywork, is false. All it achieves is creating more busywork. Unconscientious developers will do the busywork and not scrutinise the library anyway, conscientious developers will just have to do extra busywork.
A better solution would be to provide a composer metadata file and to publish each new release using a new major release number each time, which is arguably the proper way to signal to consumers of the library that each version needs careful scrutiny and testing, as major release numbers signal breaking changes.
- notRobot 5y agoThanks for the suggestions, I'm not yet convinced, but I will give this more thought!
- mannykannot 5y agoIf I understand notRobot correctly, each instance of this 'busywork' is initiated by an email, which is an opportunity for pointing out the importance of testing. It is a matter of fact that most people are susceptible (in some degree) to such influences, so if notRobot is making this point with each announcement, it may have some effect (though probably small) - and regardless, if the process turns away some people who consider this busywork too onerous, and some of those also take the same attitude with regard to testing, then so much the better, from notRobot's point of view! NotRobot is under no obligation to do anything any differently, or give any justification at all.
- notRobot 5y agoYes, you get it! :D