[Lazarus] Release schedule and policy

[Marco van de Voort]

On Mon, Oct 25, 2010 at 08:10:18PM +1100, Alexander Klenin wrote:
> > What I haven't seen:
> > - the problem
> 
> Lazarus project is unable to do releases in a timely manner.

Major or minor?

> > - the solution
> 
> Make a releases time-based, as suggested at the start of the thread.

This has been discussed many times, and as current release manager of FPC
I've tried to do this. (6 months). 

The problems are always that people only start moving when release building
is already upon them. And then these people have no time, and then those.

Then other people are discussing GIT on the maillist instead of testing
2.4.2-rc1.

> > - practicality of implementing the solution
> 
> Most other open-source projects are doing that.

That is not an argument, only an indication.
 
> > which is the problem with all the GIT noise. Much throwing in gratituous
> > principles, little practical implementation.
> 
> While it is true that git may help, time-based releases can be practiced
> using subversion too. All that is needed is to avoid Debian trap
> of striving for unattainable goal of the "perfect" release.

I hate the debian situation too, but there is a reason for this: both FPC
and Debian are entirely volunteer driven efforts.