I would go even further, are the current packages really tested anyway? There are probably a couple ppl opening them up to see if things are at the right place but I can't imagine that a heavy testing is done.
-----Original Message----- From: cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Thomas Hallgren Sent: July-04-13 5:20 AM To: cross-project-issues-dev@eclipse.org Subject: Re: [cross-project-issues-dev] 6 month release cycle On 2013-07-03 23:42, Ian Bull wrote: > > While I do think most of this could be automated -- including the > creation of the packages -- we need to question if this will inevitably > reduce quality. I think quality comes from extensive automated testing and then hands-on usage. A fully automated release process would of course cover the first. So the question is really, do we want our users to do the hands-on testing for us? That in turn, begs the question, aren't we doing that already? Assuming that many projects do, then a more frequent release cycle will actually increase quality, not the opposite. And it shortens the bug-fixing cycle dramatically. - thomas _______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev _______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
