[os-infrastructure] Re: Model discussion boiled dry(er)

[Bodo Bergmann]

Exactly right,
and that's why the "community branch" model
is less intrusive as it doesn't lock in "main"
where also the enterprise versions are branched from,
so x-integrations from our other (internal) branches
wouldn't be hold-up by community contributions.

-----Original Message-----
From: opensource-infrastructure-bounces at lists.ingres.com
[mailto:opensource-infrastructure-bounces at lists.ingres.com] On Behalf Of
Alex Hanshaw
Sent: Thursday, June 26, 2008 11:45 AM
To: Discussions about the infrastructure needed to support a true
opensourcecommunity
Subject: RE: [os-infrastructure] Re: Model discussion boiled dry(er)

Hi Joe

 If you do not have a lockstep between a community repository and a
piccolo repository then patching difs into piccolo becomes difficult.
Both of the proposed models will need a lockstep replication between
community branch/repository and piccolo the equivalent piccolo branch if
they want to avoid this problem. The community developer would still
need to integrate to head revs before submitting their change or posting
their difs for patching.

 Alex

-----Original Message-----
From: opensource-infrastructure-bounces at lists.ingres.com
[mailto:opensource-infrastructure-bounces at lists.ingres.com] On Behalf Of
Joe Abbate
Sent: 25 June 2008 23:21
To: Discussions about the infrastructure needed to support a true open
sourcecommunity
Subject: Re: [os-infrastructure] Re: Model discussion boiled dry(er)

Hi Daryl,

Daryl Monge wrote:
> Here are some scenarios, possibly colored with my viewpoint, that I 
> hope adds positively to the discussion.
>
> A while back when I first started looking at porting Ingres to OS/X we

> had source tarballs and the old SVN repository.  As my objective was 
> to pretend to be an external developer, I dutifully downloaded via the

> community source and started working on it.  In a very short period of

> time I found myself hopelessly out of date.  I had to have the ability

> to sync with the code respository whenever I needed or the project was

> going nowhere.

Could you explain why you *had* to sync with the code repository 
frequently?  In porting, at least on VMS, we start with a label 
typically from Linux and we work on it, sometimes for many weeks without

refreshing anything because we don't want to destabilize what we already

know is working.

And Jonah Harris, who I mentioned previously, did the FreeBSD port from 
the old SVN repository.

> I recently discovered a problem with the createdbms shell script
>     http://bugs.ingres.com/ticket/138
>     http://inspect.ingres.com/r/6/
> It is a three line change.  It has not been submitted yet.  In fact I 
> can't submit it.   :-(
>             or :-) depending on your point of view...........

The interesting part about createdbms is that AFAIK it is only in the 
community repository.  If it exists in Piccolo, please let me know
where.

Joe

_______________________________________________
opensource-infrastructure mailing list
opensource-infrastructure at lists.ingres.com
http://lists.ingres.com/mailman/listinfo/opensource-infrastructure
_______________________________________________
opensource-infrastructure mailing list
opensource-infrastructure at lists.ingres.com
http://lists.ingres.com/mailman/listinfo/opensource-infrastructure