ON SCM-Related Tools

OpenSolaris

WebHomeDiscussions Communities Projects Download Source Browser Last updated: 5/19/06

ON Consolidation: SCM-related Tools

There are two tables of data

• Tools owned by the ON Gatekeepers
• Tools owned by the ON Community

 COLUMN DESCRIPTIONS

• Name/Description/Owner
  • Name of the tool
• Short description of the tool
• Owner, if not noted by the table title
• ++ in this column with text denotes standards enforced by the tool
•  in this column denotes functionality the owner(s) or user(s) would like to have
• User(s)
  • Known user(s) of the tool
• Use Frequency
  • How often the tool is used/run
• Source Location
  • Where the source can be found
• Implementation Language
  • Language in which tool is written
• UI Employed
  • User interface(s) employed by the tool, i.e., the UI the tool presents to the user
• SCM Hooks Used by Tool
  • SCM hooks used to invoke the tool
• Run Type
  • How the tool is run: on demand or automatically
• Dependencies
  • Dependencies on SCCS and/or TeamWare
• Usually denotes 
  • • the use of SCCS and/or TeamWare in the tool's normal operations
• intimate knowledge about the internals of SCCS and/or TeamWare
• Access Needs
  • Does the tool need to access history information, i.e., non-current data in the tree
• Input Data
  • Does the tool require input data from sources other than what is (currently) found in the SCM repository
• Produced Data
  • Does the tool produce data that is in turn consumed by other systems such as e-mail
• Output Archived
  • Does the output of the tool require archiving

 TABLE NOTES

• Tables are numbered with prefixes to make entries unique
  • OG = Tool owned by the ON gatekeepers
• OC = Tool owned by the ON community
• C = Tool owned by another community
• Tools are listed alphabetically within a table

CONTENT NOTES

• For ON, there are tools whose only connection to SCCS or TeamWare are that they explicitly avoid the SCCS directory or make some other incidental use of the SCM.  These types of tools are believed to number between one and 24.  They are not listed on these tables.

Tools Owned by the ON Gatekeepers

• • • • • • It would be great to have a real email address for the person bringing over, rather than a username which might be unique to someone's laptop.  We have to prune the lists wenever someone with a non-global userid brings over.  There's a bunch of hackery in there right now that almost completely reduces that to zero, but that won't scale outside Sun.

• • • • • • It would be nice for the clone to be a ZFS snapshot of the gate which would require (other than actually having the gate on ZFS) a productized version of zbringover.

• • • • • • ZFS integration would be fantastic.  Danek is currently running a parallel clone that does take a snapshot every night, but those snapshots need to be available as separate workspaces.

• • • • • • This tool shouldn't exist.  If the SCM we choose requires something like this, we've picked the wrong SCM.

• • • • • • It should perform its check before the putback happens.  It should also do the full "wx pbchk", plus a few other things, but wx doesn't have the ability to check an arbitrary workspace based on a putback that's already happened (it's possible, but hacky, and hasn't been high enough priority).

• • • • • • RTI should be checked before putback.  There should be no need for the daily workspace - indeed, diffs generation should be a trivial operation with any modern SCM.

• • • • • • NLP to merge updates to flag-day/heads-up messages.

Tools Owned by the ON Community

• • • • • • Following bugs are filed against keywords:
             4701837 keywords should also work on files not in SCCS
             4747405 RFE: keywords should have an option to generate canonical ident strings
             4793568 keywords -p should complain about #pragma in non-C files
             At least on keywords wad is in flight, which will fix 4793568.  Unclear whether others have plans for keywords that aren't logged in bugster.
            Owner: ON community.  Usually maintained by people on the gatekeeping alias.

• • • • • • There are 40+ bugs in bugster against nightly, and probably everyone has his/her own set of pet peeves about it since it is one of the most highly visible faces of ON.
            Owner: ON community.  Usually maintained by people on the gatekeeper alias.

• • • • • • As with nightly, lots of people have their own ideas about what other cools things it could do.
            Owner: ON community.  Usually maintained by people on the gatekeeper alias.

• • • • • • cf nightly, webrev
          • Suggestion to replace this with a tool that performs the same functions but that operates faster (performance is very bad, at least for remote users)
            Owner: ON community.  Usually maintained by people on the gatekeeper alias.  Will Fiveash currently has the dirtiest fingers.