[os-infrastructure] Re: [os-engineering] Closed source components

[Daryl Monge]

I have to disagree.  Yes it can remain in a branch and it should.

In fact, it is the beauty of the approach as it places the  
responsibility of keeping the head-rev and experimental/project branch  
up to date in the hands of the people responsible for the special  
project, rather than moving the complications of integration to us  
internally between the community head-rev and enterprise head-rev.   
Project D becomes a community branch project and the responsibility of  
maintaining the "fork" is with project D.

Which may lead to another strategy comment:  The primary, central  
community edition we have been calling the "head-rev" should not fork  
in any substantive way from the enterprise edition mainline in either  
scenario.  Community variations that will never or not in the near  
future be brought into the enterprise product should not be placed in  
the community head-rev.



On Jun 30, 2008, at 4:21 PM, Joe Abbate wrote:

> No, it's an example of the the former, but what if the community  
> wants D Language support in the Community Edition?  It cannot remain  
> in a project branch.

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