[Lazarus] Release schedule and policy

Lukasz Sokol el.es.cr at gmail.com
Mon Oct 25 10:42:47 CEST 2010


Hi Marco,

On 25/10/2010 09:27, Marco van de Voort wrote:
> On Mon, Oct 25, 2010 at 09:20:39AM +0100, Lukasz Sokol wrote:
>>
>> [...]
>>
>> good idea, but what actually stops us from adopting the Linux model ?
> 
> About 6 dedicated paid people (and a whole bunch more volunteers) to manage
> all the branches and review and administrate each patch to reitegrate all
> the various patches into a few production trees.
>  
> The Linux kernel workflow, being security and stability sensitive in nearly
> every line of code is totally different from a normal project, and
> extremely costly in manpower.  Moreover it relies on some central (bosses)
> being able to put in a lot of time into the project on a regular, guaranteed
> basis, which is hard if they are not at least partially fulltime.
> 

I know the FULL Linux workflow won't fit - but what if it was scaled to our 
needs and manpower ?

One production (stable) tree.
One devel tree.
Peoples' private trees where the maintainer(s) of devel tree can pull from.
Communication between developers to let each other know what each branch contains.
Regression fixes always applied to top of both trees.
Top of devel tree periodically becomes merged to stable tree.

Juha's idea is actually exactly that if you read it carefully.

Lukasz





More information about the Lazarus mailing list