>>> so that means nobody *actually* loads code without tests? :D (evil laugh). > > But i do not argue about what is the be best deployment scenario. > > I am arguing about leaving developers to choose: > - if (s)he wants to deploy with tests or not, it should be up to him.
it's also up to him to - write configurations - write tests - write documentation and examples - commit code to a repository - create jenkins jobs you see, there are many things that one can avoid to do in a project, yet it is a common standard to do ALL of these tasks for a project. Yet you have your liberty to ignore these things. It is about the good path and how you push people towards it. If you do not provide the tools for it we will be stuck in stone age forever. It has never been the liberty of ignoring things that brought a project forward, but the tools that open new possibilities. How does an ideal project look for you?
