Issues and Merge Requests related to the µD3TN agent subsystem and AAP.

Issues and Merge Requests that address defects in the code or its documentation.

Issues and Merge Requests related to the µD3TN convergence layer adapters.

Issues and Merge Requests related to the µD3TN core components.

Issues and Merge Requests related to building and packaging µD3TN or parts of it for distribution.

Issues that discuss specific topics for which it was not yet decided in which exact manner they should be addressed.

Issues and Merge Requests related to the µD3TN documentation.

Issues and Merge Requests related to µD3TN's external dependencies (even if they're shipped in external/).

Issues and Merge Requests that address an extension to the functionality or the documentation.

Issues and Merge Requests related to µD3TN's forwarding logic and BDMs

Issues and Merge Requests that improve the quality of the program, the tests, or the documentation.

Issues and Merge Requests related to components that are part of the µD3TN library and might be re-used externally, such as the AAP, BP, CLA protocol, or SPP implementations.

Issues and Merge Requests that are not yet assigned to a specific release or milestone, but should be strongly considered for incorporation into the next release or release milestone.

Issues and Merge Requests related to the Python modules that are part of the µD3TN repository.

Merge Requests that are ready for review.

Issues and Merge Requests that are currently part of active development efforts.

Merge Requests that are ready to be merged into master.

Merge Requests that have been reviewed at least once and need changes to be accepted.

Merge Requests that are currently blocked. The reason for assigning this label should be explicitly noted in the comments.

Issues that indicate a task which cannot be assigned to one of the other categories (e.g., Bug, Feature, Improvement).