Re: Bug tracker tool we need
От | Christopher Browne |
---|---|
Тема | Re: Bug tracker tool we need |
Дата | |
Msg-id | CAFNqd5VCec6kXych2fUQ+tV7WjrS_fb85NvH9Jj8gKQUVDy7Vg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Bug tracker tool we need (Magnus Hagander <magnus@hagander.net>) |
Список | pgsql-hackers |
On Wed, Apr 18, 2012 at 1:48 PM, Magnus Hagander <magnus@hagander.net> wrote: > The problem I've found with most tools is that they work reasonably > well if you let them control the entire workflow. But when you want to > do things your own way, and it doesn't match up with what they were > originally designed to do, it all comes falling down quickly... That's pretty much characteristic of the average SAP R/3 project. If you can change the organization's business processes to follow SAP's defined "best practices," then it's easy to install and use R/3.But that normally not being the case, every "SAP project"winds up having hideous customization costs to kludge the practices towards one another. -- When confronted by a difficult problem, solve it by reducing it to the question, "How would the Lone Ranger handle this?"
В списке pgsql-hackers по дате отправления: