[openib-general] Need for ONE OpenIB Release process that allmembers can agree to and that follows OpenIB Bylaws

[Peter Kjellström]

On Tuesday 28 February 2006 18:48, Bob Woodruff wrote:
> Bill Boas wrote,
>
> >There appear to be 2 groups within OpenIB thinking about different
>
> approaches to >preparing the code for Release 1.0. One group is thinking
> about downstreaming it >to RedHat and Novell, another group seems to be
> thinking about separate releases >from some IB suppliers than others.
>
> I think that it is pretty important that there be a way for customers
> to know exactly what version of openib code they are getting, so
> having  having a versioning (release) mechanism from openib is
> definately needed

maybe we should provide something similar to the "lsb_release -a" command. 

ex1:
$ openib_release -a
OpenIB version:  1.0.0
Distributor ID:  Mellanox
Release:         2.0.x
Codename:        IBGD-2

ex2:
$ openib_release -a
OpenIB version:  1.0.1
Distributor ID:  Redhat
Release:         5
Codename:        RHEL-5

..just a thought,
 Peter

> and is what has started with the release 1.0 branch 
> that was started last week.
>
> Also, lets not confuse release versioning with
> distribution. Projects like gcc do release versions, but end users
> typically get the code from the Linux distributors. OpenIB doing
> release versions will also make it easier for
> distros to pick up the code for distribution and be able to tell people
> what version it is, just like I can tell what version of gcc is on
> a particular RedHat or SUSE CD.
>
> my 2 cents,
>
> woody

-- 
------------------------------------------------------------
  Peter Kjellström               |
  National Supercomputer Centre  |
  Sweden                         | http://www.nsc.liu.se
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
URL: <http://lists.openfabrics.org/pipermail/general/attachments/20060302/4fdd66ec/attachment.sig>