Conference smurf::buildhelp

434.0. "11/11/93 zso/zk3 meeting" by SMURF::FILTER (Automatic Posting Software - mail to flume::puck) Fri Nov 19 1993 14:02

Date Of Receipt: 	12-NOV-1993 16:12:28.70
From: 	ABYSS::decwet::anderson
To: 	abyss::odehelp, abyss::odestaff
CC: 	
Subj: 	11/11/93 zso/zk3 meeting
Thursday 11/11/93 11: 	00-12:00
Attendance: 	
zso: 	Tina and Rima
zk3: 	Josh, Carolyn, Grant, John, Sean
Next meeting: 	?  It would be Thanksgiving.  Do you want to

    make it Tues the 23rd?  The Thursday after Thanksgiving?
    The time is good for me from 11:00-.  Let Josh know, and
    he can set up a time with me.

1) Went over survey results.

    a)  We all agree to discontinue mips/silver mips/tin for
        any new functionality/bugfixes we do in the future.
	I'll send out a statement. Ah, one less platform to
	do nightly builds/tests on!

    b)  Grant will be sending me a copy of the "quick sheet"
        he has. This came up with one of the lowest scores
	being learning.

    c)  We agreed there is a need to continue the bookreader for
        ode documents.  But don't need to put the man pages under
	the bookreader.  So we won't.

    d)  We all would like more platform information.  Wish I had
        asked it in the questionnaire.  O Well.
            I'll put together another questionnaire to obtain:
		If you ultrix
		    pmax?	vax?	4.2, 4.3, 4.4 (coming)?
		If you alpha
		    pmax?	alpha?	1.2, 1.3, 2.0 3.0?
	    I'll also include an announcement that we will not be
	    releasing any bugfixes/new functionality on mips/silver
	    and mips/tin.

    e)   Zk3 requested that ode images be at a minimum STATIC.
         In general, their tools are also built STATIC, so
	 developers can continue to do work in an unstable
	 shared library environment.  The request is at a minimum
	 to provide STATIC images. I don't see why not.  It adds
	 more disk space, but we know that.  O.K. to provide dynamic
	 linking images as well if we wanted.

     f)  In light of the survey and scores Tina brought up osf's
         latest common interface. For example: 
		
      "For instance, 'bco -r1.2 foo.c' is now 'bco -r 1.2 foo.c'.
	
	 The reminder was made to remember backward compatibility
	 for our users.  i.e. to allow both bco -r1.2 and bco -r 1.2.
	 We will look into this, when looking into the code.


2)  Discussed bco -jCOMMON:CHILD my-file
	 Specifically discussed:  common ancestor and .BCSconfig entry.
	 (notes on that in mail message after this one)

3)  Discussed what is most need'ed yesterday. The answer was
	 the merging tasks.  After which we had talked for an
	 hour, and were ready for a break till next time.

	 I have started looking at the merging tasks and what
	 we can give you soon. Will keep you informed.

4) Question?
    When will V3.0 release?  Tina stated the plan was a year,
    with interim bugfixes and also what some new functionality
    before a year.


Till later,
Tina