---
# System prepended metadata

title: A few notes on the GitHub tracking Project for DUNE DAQ releases
tags: [DUNE-DAQ, Software Management]

---

# A few notes on the GitHub tracking Project for DUNE DAQ releases
###### tags: `DUNE-DAQ` `Software Management`


## Priority Field

Assign `Critical` to issues blocking the release (the release must be postponed if those are not ready).


Agree on some criteria on if a release should be postponed and if issues should be deferred to future releases. Something like: 
* when it comes to the tag creation deadline, if 100% critical issues are addressed ( >90% high priority issues addressed, etc), all unfished tasks shall be deferred to next release, and SW coord team should start creating the release; 
* when it comes to the tag creation deadline, if any critical issues remain unresolved, the release deadline shall be postponed.

## Adding targeted deadline/delivery date for issues?

Having targeted releases may not be enough. There are some tasks which need to be completed early in the release cycle, so that other subsequent tasks can proceed. 

"Projects Beta" is coming up with user defined workflows soon. One of the supported feature will be automatically assigning `on_schedule` status to issues when certain conditions are met. So having a "date" field might be future-proof.

[Instructions on how to add a "date" field.](https://docs.github.com/en/issues/trying-out-the-new-projects-experience/creating-a-project#adding-custom-fields)

## If possible, an additional field to track:
if the issue is:
* atomic (contained within the WG);
* if it requires subsequent tasks from other WG;
* if it requires preceding tasks from other groups.
