nasa-pds / pds-swg Goto Github PK

Release Plan

*The release plan outlines the planned PDS software enhancements, bug fixes, and impacted requirements for the upcoming Build. A more detailed breakdown of these tasks by date and priority can be found:

• In our Zenhub Roadmap (login required)
• In our schedule on the Engineering Node website (login required)

Use the Backlog links associated with the tool in order to see those issues that have been pushed to later builds.*

Plan: https://nasa-pds.github.io/releases/12.0/plan.html

SWG Review

PDS SWG (@NASA-PDS/pds-swg) members, please review the release plan linked above and provide any comments below regarding re-priorization of tasks, missing issues, etc.

The release plan approval process follows the Apache Software Foundation Voting Process, including expressing votes with +1, 0, -1, and fractions and Lazy Consensus:

Lazy consensus is simply an announcement of 'silence gives assent.'

Vote

After you have sufficient reviewed the release plan and any concerns you have been discussed, feel free to vote in the comments below with a +1 (approve), 0 (don't really care either way), -1 (disapprove), or fractions.

If no-one objects by , I'll assume lazy consensus and move forward with approval of the plan.

Added to Release Plan:

• Perform User Interviews - NASA-PDS/web-modernization#1
• Perform heuristic analysis from existing metrics - NASA-PDS/web-modernization#2
• Formulate user stories - NASA-PDS/web-modernization#3
• Identify opportunities for improvement with PDS web integration - NASA-PDS/web-modernization#4
• Synthesize interview results into user research knowledge base - NASA-PDS/web-modernization#5
• Model workflows and initial design directions based upon user analysis - NASA-PDS/web-modernization#6
• Develop tailored PDS design system - NASA-PDS/web-modernization#7
• Design mockups and develop prototype - NASA-PDS/web-modernization#8

Removed from Release Plan:

• None

Rationale:

• Rationale for late planning: User Experience staff was onboarded after Release Plan was presented to SWG. That staff was responsible for identifying tasks for this work.
• Rationale for tasks being included: https://docs.google.com/presentation/d/1In0Tjh1cuECCqF68D3d_fybLByDRUHwQtrlDd8cromI/edit#slide=id.g88d0673ea2_0_0

Added to Release Plan:
https://nasa-pds.github.io/releases/13.1/plan.html#pds-api
https://nasa-pds.github.io/releases/13.1/plan.html#registry

Removed from Release Plan:

• registry#99 Populate EN Registry with PDS3 Data Sets

  • registry#62 As a user, I want to ingest legacy PDS3 data sets from EN legacy registry
  • registry#63 Deploy harvest / registry-mgr as cron to regularly upload PDS EN data to registry
  • operations#270 Deployment of Registry Loader Tools and Initial Ingestion of Engineering Node Registry on Latest AWS Deployment

• registry#85 Enhance Registry Delete Functionality

  • registry-mgr#52 As a user I want to delete whole bundles at once

• pds-api#182 Implement Faceting

  • pds-api#70 As an API user, I want to know the unique values for a specific API field.
  • pds-api#103 As a client developer, I want to facet on 1 or more fields in the registry

Rationale:
Numerous bugs arose from initial rollout of Registry Workshop and increased usage over the past 6 months that required more effort than expected. NASA-PDS/registry-api#257

registry#85 was missed on the roadmap and in our schedule.

Removed from Release Plan:

• NASA-PDS/nucleus#66
• NASA-PDS/planetary-data-cloud#35

Rationale:
Issues with NGAP and MCP access and policy definitions. Additionally, working to establish more refined OpenSearch deployment architecture for moving to multi-tenancy.

Added to Release Plan:
N/A

Removed from Release Plan:

• NASA-PDS/registry-api#285
• NASA-PDS/registry#181
• NASA-PDS/software-issues-repo#67

Rationale:
Registry enhancements delayed due to NASA-PDS/registry#178.

JIRA migration delayed due to additional timeline available and lack of resources to focus on the task.

Added to Release Plan:
N/A

Removed from Release Plan:

• NASA-PDS/planetary-data-cloud#34 - Plan and Architect SBN-PSI Catalina Sky Survey Migration
• NASA-PDS/planetary-data-cloud#33 - Plan and Architect GEO PDS3 Diviner Migration Pilot
• NASA-PDS/planetary-data-cloud#32 - Plan and Architect ATM Annex Pilot Project
• NASA-PDS/planetary-data-cloud#5 - NAIF Website Migration AWS and DMZ

Rationale:
All pilot projects are being tabled until next FY when the EN Team has a better grasp of NGAP and how we are able to easily architect and deploy these applications, services, and data into NGAP.

please work with your node personnel to complete by next meeting

1. Task Planning Guide - https://docs.google.com/presentation/d/1U0puzuUR-1ryWylTElYgd7pZDx0IiXxBu-dZbCIikMw/edit?usp=sharing
2. B11.1 Task Plans (where to find previous plan) - https://drive.google.com/drive/u/1/folders/15D4Bsht-L_OaIpYjbfR0bcFVZANV27Ig
3. B12.0 Task Plans (where to put new plan) - https://drive.google.com/drive/u/1/folders/1NhRfTL89vJ3PK-vlcSrOkf0o_x236Bn7

Plan: https://app.zenhub.com/workspaces/pdsen---all-projects-5c87e859b7a0872dd10b87c5/roadmap

Added to Release Plan:
N/A

Removed from Release Plan:

• Tracking Service
  • Refactor Tracking Service
  • Develop OpenAPI Spec and Postman for Tracking Service API

Rationale:
Tracking Service design and partial implementation was completed in 2018. Misunderstanding during handoff from previous developers that the software design did not include requirements definition, and design did not form to common API standards. Caused significant increase in scope for requirements definition task

Release Plan

The release plan outlines the planned PDS software enhancements, bug fixes, and impacted requirements for the upcoming Build. A more detailed breakdown of these tasks by date and priority can be found in our Zenhub Roadmap or by clicking through the links of the Plan linked below. Use the Backlog link associated with each of the software tools and services in order to see those issues that have been pushed to later builds.

Plan: https://nasa-pds.github.io/releases/13.1/plan.html

SWG Review

PDS SWG (@NASA-PDS/pds-swg) members, please review the release plan linked above and provide any comments below regarding re-priorization of tasks, missing issues, etc.

The release plan approval process follows the Apache Software Foundation Voting Process, including expressing votes with +1, 0, -1, and fractions and Lazy Consensus:

Lazy consensus is simply an announcement of 'silence gives assent.'

Vote

After you have sufficient reviewed the release plan and any concerns you have been discussed, feel free to vote in the comments below with a +1 (approve), 0 (don't really care either way), -1 (disapprove), or fractions.

If no-one objects by 01/09/2023, I'll assume lazy consensus and move forward with approval of the plan.

Release Plan

The release plan outlines the planned PDS software enhancements, bug fixes, and impacted requirements for the upcoming Build. A more detailed breakdown of these tasks by date and priority can be found in our Zenhub Roadmap (login required) or the schedule on the Engineering Node website (login required). Use the Backlog link associated with the tool in order to see those issues that have been pushed to later builds.

Plan: https://nasa-pds.github.io/releases/11.1/plan.html

SWG Review

PDS SWG (@NASA-PDS/pds-swg) members, please review the release plan linked above and provide any comments below regarding re-priorization of tasks, missing issues, etc.

The release plan approval process follows the Apache Software Foundation Voting Process, including expressing votes with +1, 0, -1, and fractions and Lazy Consensus:

Lazy consensus is simply an announcement of 'silence gives assent.'

Vote

After you have sufficient reviewed the release plan and any concerns you have been discussed, feel free to vote in the comments below with a +1 (approve), 0 (don't really care either way), -1 (disapprove), or fractions.

If no-one objects by 11/04/2020, we will assume lazy consensus and move forward with approval of the plan.

Added to Release Plan:

N/A

Removed from Release Plan:

https://github.com/nasa-pds/pds-registry-app/issues/191 - B12.1 Initial external source integration

Rationale:

With Product_Metadata_Supplemental and accompanying CSV ingestion supported, a workaround exists for ingesting database data. More use detailed use cases needed for what data needs to be ingested and how we can support it. Additionally, other API tasks have taken precedence (Staging vs. Operational Data, Handling "deprecated" LIDs and Versions)

Added to Release Plan

N/A

Removed from Release Plan

Improve File Path Handling #502

• validate does not work correct when path name contains a space on mac #427
• pds4.bundle option seems to not travel through enough subdirectories #444
• Refactor code to use URL objects instead of file paths wherever possible #465
• Validate can't find files in directory specified by <directory_path_name> #474

Referential Integrity Checking with the Registry #414

• As a user, I want to perform referential integrity checking against a registry #415
• As a user, I want validate to throw an error when the LID specified for secondary context product in a collection inventory is not valid #462

Improve Content Validation Performance through Spot Checking #498

Rationale

Significant delays in the implementation needed to support #481 B13.0 Content Validation Improvements: Intermingled Headers have impacted numerous planned improvements.

Added to Release Plan:

• NASA-PDS/registry#185
• NASA-PDS/registry-sweepers#92

Removed from Release Plan:

• NASA-PDS/registry#181
• NASA-PDS/registry-api#285
• NASA-PDS/registry#230
• NASA-PDS/harvest#131

Rationale:

• Increased scope of NASA-PDS/registry#185 to use Cognito for multi-tenant OpenSearch requires developer needed for other tasks
• NASA-PDS/registry-sweepers#92 was necessary in order to decrease cost and improve scalability of registry sweepers

Release Plan

The release plan outlines the planned PDS software enhancements, bug fixes, and impacted requirements for the upcoming Build. A more detailed breakdown of these tasks by date and priority can be found in our Zenhub Roadmap (login required) or the schedule on the Engineering Node website (login required). Use the Backlog link associated with the tool in order to see those issues that have been pushed to later builds.

Plan: https://nasa-pds.github.io/releases/12.1/plan.html

SWG Review

PDS SWG (@NASA-PDS/pds-swg) members, please review the release plan linked above and provide any comments below regarding re-priorization of tasks, missing issues, etc.

The release plan approval process follows the Apache Software Foundation Voting Process, including expressing votes with +1, 0, -1, and fractions and Lazy Consensus:

Lazy consensus is simply an announcement of 'silence gives assent.'

Vote

After you have sufficient reviewed the release plan and any concerns you have been discussed, feel free to vote in the comments below with a +1 (approve), 0 (don't really care either way), -1 (disapprove), or fractions.

If no-one objects by 2021-11-10, we will assume lazy consensus and move forward with approval of the plan.

Added to Release Plan:
Numerous bug fixes per registry workshops

Removed from Release Plan:

• Support Loading PDS3 Data with Product Metadata Supplemental
• Support LBLX extension in Registry Loader tools
• Search Improvements to Support Web Modernization
• Implement Faceting

Rationale:
enter rationale for deviation from plan here

Added to Release Plan:
links to tasks being added to release plan

Removed from Release Plan:
NASA-PDS/registry#55
links to tasks being removed from release plan

Rationale:
Not critical yet, focused for this release on a robust v1 release of the registry and management of scalable harvesting for bigger bundles.

Added to Release Plan:
N/A

Removed from Release Plan:

• Update Validate to handle additional File_Areas added after original implementation - NASA-PDS/validate#229
• Update Validate and PDS4 JParser to better handle additional data types - NASA-PDS/validate#212
• Fix bug where caching is not sufficiently recognizing dictionary versions - NASA-PDS/validate#188
• Update validate per SR requirements for collection inventories - NASA-PDS/validate#230

Rationale:

1. Improvement from Build 10b, Validate Table_Character groups and their specified lengths match the specified group_length, had numerous ripple effects throughout the validate software, which required numerous bug fixes that used all the schedule slack for Build 11.0 delivery.

   • NASA-PDS/validate#149
   • NASA-PDS/validate#222
   • NASA-PDS/validate#177
   • NASA-PDS/validate#215
   • NASA-PDS/validate#220
   • NASA-PDS/validate#233
   • NASA-PDS/validate#234
   • NASA-PDS/validate#243
   • NASA-PDS/validate#243

2. Validate expert was pulled off onto M2020 Science Data System development work. Plans to train up new "expert" for Build 11.1.

Added to Release Plan:

• NASA-PDS/pds4-information-model#368
  • multiple tasks associated with the GEOM LDD split efforts. this has required a significant amount of effort from @jshughes to support refactoring of the LDDTool / Information Model code for generating XSD / SCH.

Removed from Release Plan:

• NASA-PDS/pds4-information-model#306
  • the code sitting under the hood of IMTool needs some refactoring. not a critical task, but something we need to get to in the future

Rationale:
The GEOM LDD split effort is fully underway and we have pretty much dug the hole too deep at this point. Pulling back on that effort is most likely a non-starter, so we have to pivot to support that. The "B12.0 Refactoring of IMTool" effort is not critical and should not impact LDDTool for the near-term.

Plan: https://app.zenhub.com/workspaces/pdsen---all-projects-5c87e859b7a0872dd10b87c5/roadmap

Added to Release Plan:

• PDS4 Information Model / LDDTool

  • CCB-319: Add 'ns' – The abbreviated unit for 'Units_of_Time' (1/10^9 s)
  • CCB-320 : Add 'W/m**2/sr/nm/(DN/s)' under Units_of_Misc
  • CCB-311: Value meanings for <rule_type> permissible values should be rewritten
  • CCB-264: Make the Line Feed (LF) character an allowed record delimiter
  • CCB-323: Fix schema formation rule for lidvid_reference (Part II)
  • CCB-304: Cleanup unused Vector classes in IM before 2.0.0.0

• Validate

  • CCB-264: Make the Line Feed (LF) character an allowed record delimiter

Removed from Release Plan:
N/A

Rationale:
Several additional SCRs passed by the CCB.

Description

All issues currently open for Validate Tool are listed in the spreadsheet below. The spreadsheet contains all open validate issues / requirements with issue types and EN priorities. The On Deck column are EN's tentative plans for B12.0.

Action

Each node (led by their SWG member) is responsible for reviewing and prioritizing the tickets using the $100 Test Prioritization method. Each node gets $100 they can distribute however they would like amongst the open bugs / enhancements / requirements (within your applicable column in the spreadsheet), and EN will use this to re-prioritize and plan accordingly.

https://docs.google.com/spreadsheets/d/1wfszWW6ac1qX58T80_TE3V_KTQbQntmptGQyKrnAl78/edit?usp=sharing

Plan: https://app.zenhub.com/workspaces/pdsen---all-projects-5c87e859b7a0872dd10b87c5/roadmap

Added to Release Plan:

• NASA-PDS/web-modernization#70 - Develop detailed plan for new PDS Web Modernization working group activities, milestones, and deliverables

Removed from Release Plan:

• NASA-PDS/web-modernization#60 - Revise and review user stories with an organized review
• NASA-PDS/web-modernization#35 - Content Management System
• NASA-PDS/web-modernization#45 - WDS Mobile Considerations
• NASA-PDS/web-modernization#41 - Review Feedback Widget Design
• NASA-PDS/web-modernization#30 - User Documentation Consolidation
• NASA-PDS/web-modernization#55 - Apply PDS WDS to PDS software documentation

Rationale:
Deferring these tasks to B12.0 in order to develop a comprehensive, detailed plan, milestones, and activities for a PDS Web Modernization Team. NASA-PDS/web-modernization#70

Added to Release Plan:
https://nasa-pds.github.io/releases/13.1/plan.html#validate

Removed from Release Plan:

• validate#534 B13.1 Content Validation Improvements: Additional Table Types, Additional File Areas
  • validate#217 As a user, I want to validate content for all possible PDS4 table types
  • validate#436 Improve error messages for overlapping objects in a label
  • validate#480 Validate does not calculate overlaps correctly when Header is not first object in file

Rationale:
Numerous bug fixes added onto the front half of the build implementation pushed out all other higher priority improvements. This will move onto B14.0 stack. Additionally, a lot of these tickets may have been fixed or improved from some of the bug fixes from B13.1, but we have not had the time to come up with sufficient test data to test all the table types.

Added to Release Plan:

N/A

Removed from Release Plan:

NASA-PDS/validate#414 - Referential Integrity Checking with the Registry
NASA-PDS/validate#422 - B12.1 Re-imagine Output Logging for Validity vs Metadata Quality

Rationale:

Validate CogE retired in December causing significant delays in content validation improvements and bug fixes (NASA-PDS/validate#426). Considering content validation is a critical component ensuring a valid archive, these tasks for improvements to existing capabilities is being tabled to B13.0.

Added to Release Plan:
links to tasks being added to release plan
Numerous bug fixes have take developer time away from improvements, including:

• NASA-PDS/validate#368
• NASA-PDS/validate#372
• NASA-PDS/validate#380
• NASA-PDS/validate#379
• NASA-PDS/validate#375
• NASA-PDS/validate#382

Removed from Release Plan:
links to tasks being removed from release plan

• NASA-PDS/validate#319
  • NASA-PDS/validate#150

Rationale:
enter rationale for deviation from plan here
Depending on triaged priority of bug fixes, the tend to move towards the top of validate dev queue as they are often blockers to allowing a user to successfully validate their archives.

Release Plan

The release plan outlines the planned PDS software enhancements, bug fixes, and impacted requirements for the upcoming Build. A more detailed breakdown of these tasks by date and priority can be found in our GitHub Project or the schedule on the Engineering Node website (login required). Use the Backlog link associated with the tool in order to see those issues that have been pushed to later builds.

Plan: https://nasa-pds.github.io/releases/14.0/plan.html or https://github.com/orgs/NASA-PDS/projects/4/views/1

SWG Review

PDS SWG (@NASA-PDS/pds-swg) members, please review the release plan linked above and provide any comments below regarding re-priorization of tasks, missing issues, etc.

The release plan approval process follows the Apache Software Foundation Voting Process, including expressing votes with +1, 0, -1, and fractions and Lazy Consensus:

Lazy consensus is simply an announcement of 'silence gives assent.'

Vote

After you have sufficient reviewed the release plan and any concerns you have been discussed, feel free to vote in the comments below with a +1 (approve), 0 (don't really care either way), -1 (disapprove), or fractions.

If no-one objects by 5/17/2023, we will assume lazy consensus and move forward with approval of the plan.

Plan: https://app.zenhub.com/workspaces/pdsen---all-projects-5c87e859b7a0872dd10b87c5/roadmap

Added to Release Plan:
N/A

Removed from Release Plan:

• NASA-PDS/pds-api#24 - Define PDS handling of enriched / supplemental metadata
• NASA-PDS/pds-api#15 - Query passing and search integration design
• NASA-PDS/pds-api#25 - PDS API extension convention for discipline-specific search engines

Rationale:
Inaccurate estimates for time to complete other designs and implementations with PDS API WG.