1 / 13

2006 Development Plan

2006 Development Plan. Amy Johnson Amy Ruskowski Doug Daniels. 2006 Development Plan. ClearCase Control Board Team Future Development Branch Plan WINT Prototype Branch Scheme Config Spec Management Build Management Rose Model Management. 2006 Development ClearCase Control Board.

emmett
Télécharger la présentation

2006 Development Plan

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 2006 Development Plan Amy Johnson Amy Ruskowski Doug Daniels

  2. 2006 Development Plan • ClearCase Control Board Team • Future Development Branch Plan • WINT Prototype Branch Scheme • Config Spec Management • Build Management • Rose Model Management

  3. 2006 Development ClearCase Control Board • ClearCase Control Board Lead – Joe Santos • Config Spec / Vobs Admin – Sandi Slack • Common Baseline Team Members – Amy Johnson, Amy Ruskowski and Doug Daniels • ClearCase Control Board members (vobadmins) • WinT Prototypes • CJMTK / Architecture – Julie Rego, Christina Rodriguez • QED – Paul Kendrew • DNA – John Graham • Spectrum- Eric Miozza • Netops ID – Doug Daniels • DNA ID – Vicki Nurse • Spectrum ID – Todd Proctor • Integrated Computing ID – Jim O’Malley • QED ID – Peter Maricle • Marconi – Paul Rego

  4. Future Development Branch Plan /fbn/vobs Main branch (COMMON_BASELINE 1.0 config spec) COMMON_ BASELINE_ 0.0 Start COMMON_ BASELINE_ 0.1 DNA COMMON_ BASELINE_ 0.2 NETOPS COMMON_ BASELINE_ 1.0 Review board determines what gets merged back to common baseline for future Common Baseline releases WinT Prototype Main Branch wint_prototype_main All existing branches off of /fbn/vobs are locked for development NETOPS ID 2006 Main Branch netops_id_main DNA ID 2006 Main Branch dna_id_main NO development in 2006 Will occur on MAIN/LATEST Branches will be made for Each area of development to Conduct builds and those will Serve as “project main” Spectrum ID 2006 Main Branch spectrum_id_main Integrated Computing ID 2006 Main Branch integrated_computing_id_main Marconi 2006 Main Branch marconi_id_main

  5. WinT Prototype Branch Plan(example for all 2006 branches) /fbn/vobs MAIN/LATEST branch (COMMON_BASELINE 1.0 config spec) COMMON_ BASELINE_ 0.0 Start COMMON_ BASELINE_ 1 DNA COMMON_ BASELINE_ 0.2 NETOPS COMMON_ BASELINE_ 1.0 Rose model checkins will occur off of “project main” Branch for Each Group by the ClearCase Control Board member. SIT Builds off of WinT Prototype Branch WinT Prototype Main Branch (WinT’s main branch) WINT PROTOTYPE 0.0 WINT PROTOTYPE 1.0 . . . WINT PROTOTYPE 2.0 CJMTK/Architecture Branch Cjmtk_arch _prototype_dev Interim testing and integration at each individual branch Spectrum Branch spectrum _prototype_dev DNA Branch dna _prototype_dev QED Branch qed_prototype_dev

  6. 2006 Branch Names /fbn/vobs MAIN/LATEST branch (COMMON_BASELINE 1.0) wint_prototype_main cjmtk_arch_prototype_dev spectrum_prototype_dev dna_prototype_dev qed_prototype_dev netops_id_main netops_id_dev dna_id_main dna_id_dev spectrum_id_main spectrum_id_dev integrated_computing_id_main integrated_computing_id_dev marconi_id_main marconi_id_dev

  7. Config Spec Management • Config Specs for each group will be created to represent the final branching structure and will be placed in /fbn/vobs/configspecs (both dynamic and snapshot view versions should be kept here) • ClearCase Control Board members will have privileges to change their teams config specs and will have to send an email to the group if an update is needed. • Sandi Slack will have authority over Config Specs. Please inform her of all changes and updates as they are needed. • Joe Santos will oversee the ClearCase Control Board – all future issues after development starts should be raised through him.

  8. Build Management • Interim testing and builds should be done at lowest level branching • ClearCase Control board members specified will be responsible for build scripts and builds done at the lowest levels • Each branch “project main” will be locked for development and only the ClearCase Control Board members will be allowed checkins on this branch • Official builds are performed by the build manager and should occur at specified schedule dates and be labeled on the branch “main”

  9. Rose Model Management • Rose model development will occur at the branch “project main” location and checkins will be done by the ClearCase Control Board Manager. (Snapshot view checkins can also be done by CCCB – please see Julie for instructions on this) • Project .cat files should exist for sequence diagram development for this year so they can be merged to the common baseline in the future. • Project .cat files for each group should exist in the Logical area for class file creation. Users indiviual .cat files per group can be placed here (however it is not required that your team use individual .cat files) • The logical area will be reverse engineered in the future when merges are needed.

  10. Releasing to a project main • To release a project to a MAIN branch you: • Set config spec to MAIN branch • c setcs /fbn/vobs/configspecs/netops_id_main/netops_id_main • Do a merge from the development branch to the MAIN branch. • c findmerge /fbn/vobs/* -fver …/netops_id_dev/LATEST –print

  11. Common Baseline PTRs • A separate DTT database has been created to document problems found in the common baseline • All PTRs need to be reviewed on each of the projects to ensure that PTRs are documented in the proper DTT database • A common baseline config spec is available to test if a problem is project-specific or a common baseline problem

  12. Changes to Common Baseline • A formal common baseline release must occur • Config specs will be updated to pull from new common baseline release label • Each project will then need to merge from the new common baseline into their project’s MAIN branch to merge any conflicting changes.

  13. Sample Config Spec • For netops_id_dev branch: element * CHECKEDOUT #Pull in specific versioned files here element configspecs/... /main/LATEST #For Rose modeling element */model/... .../wint_prototype_main/LATEST element */model/... COMMON_BASELINE_1.0 -mkbranch wint_prototype_main element */model/... /main/LATEST -mkbranch wint_prototype_main #For NETMAPS because they use older version of dnaUtil element */dna/dnaUtil/builds/... DNA_UTIL_00.00.03.01 #Development branch element * .../cjmtk_arch_prototype_dev/LATEST #MAIN Branch element * .../wint_prototype_main/LATEST -mkbranch cjmtk_arch_prototype_dev #Branch from COMMON_BASELINE element * COMMON_BASELINE_1.0 -mkbranch wint_prototype_main #Needed for making new elements on dev branch element * /main/LATEST -mkbranch wint_prototype_main

More Related