generated from camaraproject/Template_API_Repository
-
Notifications
You must be signed in to change notification settings - Fork 9
Open
Labels
subproject managementIndicating issues with subproject repository or release management processIndicating issues with subproject repository or release management process
Description
Problem description
This issue should serve for collecting topics to be addressed by next release of population-density-data API:
Meta-release Sync26
Please add your proposals in the comments and open issues if needed.
A new label Sync26 has been defined to track all items in the population-density-data Sync26 meta-release scope.
The WG should review as candidates those issues labeled with Sync26 to decide whether to include or discard them (at least for now). And WG participants can submit new proposals for the next release to be considered as well.
| Milestone | Target date | Status |
|---|---|---|
| M1 (Commonalities & ICM) | nov 30 | from Spring26 |
| M0 | jan 15 | kick-off preparation |
| M2 (Commonalities & ICM) | jan 31 feb 15 | from Spring26 |
| M4 (Commonalities & ICM) | mar 15 | from Spring26 |
| M1 (API Sub Projects) | apr 30 | |
| M3 (API Sub Projects) | jun 15 | |
| M4 (API Sub Projects) | sep 30 | |
| M5 | oct 15 | |
| M6 | oct 31 |
The scope for the PopulationDensityData API should be defined until M1, leaving two month to create the release candidate
Expected action
Targets for Sync26 (proposed/to be discussed)
- Clarification and improvement of documentation
- Incorporation of feedback from implementations
- Alignment with Commonalities & ICM changes Spring26
Target versions
- population-density-data 1.0.0
Issues to be addressed in Sync26 scope
- Some model names use SNAKE_CASE in place of CamelCase #107
- Provide a list of GeoHashes in the API request #110
- Create a User Story for the Population Density Data API (Stable readiness prerequisite) #114
- Fix incorrect ATP time-range assertions #118
Potentially in scope, depending on Commonalities
Action Points
- Define scope
- Update Release Plan
- Alpha 1 with features updates for March 30
- M1: Alpha 2 with alignment to Commonalities for April 30
- M3: RC for June 15
- M4: Public for September 30
Auxiliary tasks:
- Update Test Cases (at least for release number)
- Update Changelog
- Update Readme.md
- Update Readiness Checklist
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
subproject managementIndicating issues with subproject repository or release management processIndicating issues with subproject repository or release management process