Jens-G commented on pull request #2333: URL: https://github.com/apache/thrift/pull/2333#issuecomment-781650250
> These are all "corner cases" that only affect a small subset of use cases, Or bad testcase design. I tend refuse to accept such explanations, because it opens the slope to banana software. Sure, shit happens but as developers we should strive to not let it happen. We expect our stuff to work perfectly and are astonished when it does not. The key problem with tests is, that developers are used to think *constructive*. But to write good test cases you have to be *destructive*. Pick the evil guy's hat and ask yourself: What would potentially break it? Then put that it into a test case. > push the built artifacts to package managers Problem is, we can't. [The ASF has very clear rules](http://www.apache.org/legal/release-policy.html): Everything that gets published has to be voted and accepted as a release. We can have internal pre-releases, but are not allowed to upload it to package managers. So if I don't overlook a thing (which is certainly possible) the only way would indeed be to have two official releases. > Publication > > Projects SHALL publish official releases and SHALL NOT publish unreleased materials outside the development community. > > During the process of developing software and preparing a release, various packages are made available to the development community for testing purposes. Projects MUST direct outsiders towards official releases rather than raw source repositories, nightly builds, snapshots, release candidates, or any other similar packages. The only people who are supposed to know about such developer resources are individuals actively participating in development or following the dev list and thus aware of the conditions placed on unreleased materials. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
