[Lazarus] Release schedule and policy

[Graeme Geldenhuys]

Op 2010-10-25 10:52, Marco van de Voort het geskryf:
> 
> The problem is keeping track of them. See my other reply in this thread.

Again, use the right tools for the job. Git (I really didn't what to say
this again) makes this easy.


> What I haven't seen:
> - the problem

Good lord, read you damn emails. Read my messages in the past with a
similar topic. Read Juha's original post. Listen to what the many Lazarus
users post quite often on this mailing list.


> - the solution

Again, read some responses in this and many other similar threads.


> - practicality of implementing the solution

like with everything else, things evolve and change over time. KDE used
CVS, then SubVersion, then Git. Linux project, a similar thing. tiOPF
project used emailing patches, CVS, then Team Coherence then SubVersion.
Thousands of other open source project are changing there ways over time -
as newer and better tools become available. FPC and Lazarus projects still
seem oblivious to this fact. God only knows what a struggle it must have
been to come to the consensus to move from CVS to SubVersion - thank God it
was before my time.



Regards,
  - Graeme -

-- 
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://opensoft.homeip.net:8080/fpgui/