[openfabrics-ewg] Getting EWG off to a rapid and positive start

[Tziporet Koren]

I already replied regarding the branch/trunk relations in another email
so no need to repeat.

Regarding the patches directory - The idea was to work with the tag
method and stay as close to the trunk and as possible.
Also all the backport are in patches so in any case the install script
already knows how to handle patches and apply them.

The patches directory is also very good for testing & updating the
package since one can add there a patch and rebuild the package with it,
even before it's committed to the tree.

But these are all technical details that have to be closed after the
release frame will be set next Monday.

Tziporet




-----Original Message-----
From: openfabrics-ewg-bounces at openib.org
[mailto:openfabrics-ewg-bounces at openib.org] On Behalf Of Bryan
O'Sullivan
Sent: Friday, March 17, 2006 6:22 PM
To: Sujal Das
Cc: Openfabrics-ewg at openib.org
Subject: RE: [openfabrics-ewg] Getting EWG off to a rapid and positive
sta rt

On Thu, 2006-03-16 at 10:51 -0800, Sujal Das wrote:

> EWG DISTRIBUTION MANAGEMENT + SYNCH WITH OFR RC BRANCH
> 
> Copy a specific trunk/branch version to EWG area you can call this a
> tag. The main idea of a tag is that you do not commit changes to the
> tagged area.

We should maintain one branch for EWG development, the existing 1.0
branch.  I don't mind there being a separate EWG tag of some kind.

> In addition there is a directory called patches where EWG places the
> fixes wanted that were not in the trunk/branch.

No.  Just commit changes directly to the 1.0 branch.  There's no reason
to have a directory full of patches.

	<b

_______________________________________________
openfabrics-ewg mailing list
openfabrics-ewg at openib.org
http://openib.org/mailman/listinfo/openfabrics-ewg