Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "OSEE/OSEE Milestones"

Line 1: Line 1:
 
OSEE Deployment Milestones
 
OSEE Deployment Milestones
  
* <b>2020 - May  - Onboard first F18 OSEE Developer
+
* <b>2020 - May  - Onboard first F18 OSEE Developer</b>
* <b>2020 - May  - Create REST API to get commit data from a git change id
+
* <b>2020 - May  - Create REST API to get commit data from a git change id</b>
* <b>2020 - Apr  - Provide a link between Cameo and OSEE
+
* <b>2020 - Apr  - Provide a link between Cameo and OSEE</b>
* <b>2020 - Apr  - Create types in support of FACE
+
* <b>2020 - Apr  - Create types in support of FACE</b>
 
* <b>2020 - Mar  - Convert to using full type tokens</b>
 
* <b>2020 - Mar  - Convert to using full type tokens</b>
 
* 2020 - Feb  - Setup and run Coverity Scans against OSEE
 
* 2020 - Feb  - Setup and run Coverity Scans against OSEE

Revision as of 09:45, 1 June 2023

OSEE Deployment Milestones

  • 2020 - May - Onboard first F18 OSEE Developer
  • 2020 - May - Create REST API to get commit data from a git change id
  • 2020 - Apr - Provide a link between Cameo and OSEE
  • 2020 - Apr - Create types in support of FACE
  • 2020 - Mar - Convert to using full type tokens
  • 2020 - Feb - Setup and run Coverity Scans against OSEE
  • 2019 - Dec - Performed a Posgres database initialization in the Cloud
  • 2019 - Sept - Add ability to deploy OSEE to a CITRIX environment for US Navy access
  • 2019 - Aug - Add ability to save ATS searches
  • 2019 - Jul - Create Web UI for PL Config including Edit
  • 2019 - Mar - Import first set of requirements for F18
  • 2019 - Feb - Analyze use of OSEE for modernization of US Navy's Operations tooling
  • 2019 - Apr - Create GIT commit hooks into OSEE to track commit history for Boeing AvionX
  • 2017 - Nov - Analyze and deploy OSEE toolset for F18 tool modernization
  • 2017 - Feb - Create Data Rights support in OSEE
  • 2016 - May - Create ORCS Writer for external/mass artifact editing and re-importing
  • 2016 - Apr - Deploy Product Line approach using OSEE to Apache and AOP
  • 2016 - Apr - Add Product Line capabilities to OSEE branches and artifacts
  • 2015 - Jan - Create Agile tracking in OSEE and move OSEE dev team to Agile
  • 2013 - Mar - Move disposition of test failure UI to Web
  • 2012 to Now - BOSCH-RBEI begins using OSEE within the automotive industry
  • 2012 - Jun - Add ability to easily port changes from one branch to another
  • 2012 - Feb - Create RESTful interfaces on OSEE server for any client use
  • 2012 - Feb - Create RESTful artifact query feature (ORCS Script)
  • 2012 - Apr - Convert OSEE build and test to use Maven and continuous integration
  • 2011 - Jan - Migrate all Software Test change report tracking to OSEE ATS
  • 2010 - Sep - Create ability in OTE to batch selected set of Mission Software tests overnight
  • 2010 - Nov - Deploy OSEE tool suite to new AH-6 program/platform for use in all areas of engineering
  • 2010 - Aug - Create customer facing web interface for live delivery of project data
  • 2010 - Aug - Add ability to store mission software code coverage results over time and disposition
  • 2009 - Mar - Add automated historical Test Script Development Metrics generation
  • 2009 - FEb - Add automated code build memo generation for mission software
  • 2009 - Aug - Auto-generate OSEE Help from existing OSEE Wiki documentation
  • 2008 - Jun - Develop advanced requirement merging capabilities
  • 2008 - Jul - Incorporate System Safety into Apache Mission Software OSEE model

Back to the top