Joshua D. Drake wrote:
>>> we will know whether this is a great thing we should continue, or we
>>> should stick to our traditional laissez-faire style of project
>>> management. I figure that even if it really sucks, it wouldn't kill us
>>> to try it for one release cycle --- at the very worst, w
Josh Berkus writes:
>> I propose a modest experiment: for the 8.3 development cycle, let's try
>> to agree (in the next month or so) on a roadmap of what major features
>> should be in 8.3 and who will make each one happen.
> Well, I think the what is more important that the who -- we can switch
Tom,
> I propose a modest experiment: for the 8.3 development cycle, let's try
> to agree (in the next month or so) on a roadmap of what major features
> should be in 8.3 and who will make each one happen.
Well, I think the what is more important that the who -- we can switch "whos"
if that's w
we will know whether this is a great thing we should continue, or we
should stick to our traditional laissez-faire style of project
management. I figure that even if it really sucks, it wouldn't kill us
to try it for one release cycle --- at the very worst, we'd make up lost
time in future by no
On Aug 31, 2006, at 8:47 PM, Tom Lane wrote:
[ hijacking this thread over to where the developers hang out ]
Alvaro Herrera <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
It's pointless to suppose that individual developers would really be
answerable to any project-wide management, since that's
[ hijacking this thread over to where the developers hang out ]
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> It's pointless to suppose that individual developers would really be
>> answerable to any project-wide management, since that's not who they're
>> paid by. So I tend to
