[os-infrastructure] Model discussion boiled down

Daryl Monge daryl.monge at ingres.com
Tue Jun 24 13:56:30 PDT 2008


I think the "fresh" model wins easily.

On Jun 24, 2008, at 3:36 PM, Andrew Ross wrote:

> a) The "fresh" model
>
> In this model, the latest and greatest Ingres code is mirrored between
> piccolo and svn. Headrev = headrev.
> ...........................
>
> Commentary:  While in theory customers could run with the community
> edition, GPL contamination and instability is a very real concern. I
> personally feel no customer would be willing to run their
> production/mission critical systems on an unstable/development  
> codeline.

The existence of up to date source in SVN will have no affect at all  
on any "normal" business.  I can't imagine any customer I have  
encountered that would even remotely consider using the SVN repository  
to avoid a proper support contract.

Still, one variation would be to only post source updates to SVN and  
not build distribution binaries after the initial GA release.  I'm not  
sure about this area; it needs more discussion.

>
>
>
> b) The "delayed" model
>
> In this model, the latest and greatest code is stored in piccolo. The
> code in svn is purposely out of date.
> ...........................

I think this gets us criticized in the Open Source community and  
generates poor public perception.  It tells the community we are not  
serious about Open Source and we become a Wolf (Closed Source) in  
Sheep clothing (Open Source)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ingres.com/pipermail/opensource-infrastructure/attachments/20080624/b3dbe9ab/attachment.html


More information about the opensource-infrastructure mailing list