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

[Joe Abbate]

Daryl Monge wrote:
> Stable releases would be created as a branch from the head-rev much 
> like our Piccolo release branches are done and binaries  can be build 
> from them.  I have seen that described in several previous messages 
> and it is in the wiki diagrams.  In 
> http://community.ingres.com/wiki/Image:Branch-strategy-1.png
> It is called CR1 and CR2.
>
> The head-rev is source only, or possibly with nightly builds on select 
> platforms, and can be downloaded by community developers to do 
> whatever.  Big projects might wish to create branches early on in the 
> project.  Again, I consider these things to be process questions, not 
> strategic questions.  They would be needed for either scenario.
>
> I don't see it as being any different process than our internal 
> systems process of creating "ingres2006r3" or the various labels used 
> for patches.

In order for someone to build a release from say, CR1, with D Language 
support that is in, say, the PROJD branch, the relevant changes from 
PROJD *have* to be part of CR1, i.e., they have to be cross-integrated, 
or merged into CR1.  In other words, although the changes "stay" in the 
PROJD branch, they're also part of CR1.  Any fix made to PROJD has to be 
merged again to CR1 and vice versa.  When CR2 is ready to be created, if 
PROJD isn't part of the Main Community Mirror, as exemplified by the 
downward pointing arrows from the CDBn branches, the PROJD branch will 
have to be *again* crossed-integrated or merged into CR2.

Joe