[Lazarus] Release schedule and policy

[Florian Klaempfl]

Am 25.10.2010 10:47, schrieb Graeme Geldenhuys:
> Op 2010-10-25 10:35, Vincent Snijders het geskryf:
>>
>> No, there is a limit on the number of branches you - sorry, I mean *I*
>> - can overview. For me, two long living branches are already too much.
> 
> Distribute the work-load. The developer working on whatever branches are
> responsible for keep it up to date. Why do you think you must do that? All
> you (meaning the person maintaining the key public branches like Fixes,
> Trunk etc) need to do, is merge those "feature" branch into others. If they
> don't merge, revert the changes, email the maintainer of that branch to get
> his work in order.
> 
> The key is to delegate! :-)

Let me quote you from a few days ago on fpc-other:

"I've taken the following stance with the Lazarus team. I contribute,
and forget about the patch. They can do with it as they please, I did my
part."