---
# System prepended metadata

title: Partner Engineering - Galaxy NG 4.3.0

---

# Partner Engineering - Galaxy NG 4.3.0

### Priority 1s
* Galaxy_NG to understand the release train for a given collection. Metadata design
    * Priority 4 - Fall deliverable
* Content provenance - Support needs to be able to identify the "installed" collection origin
    * Priority 2 - Spring deliverable
* Galaxy_NG to project to the user the supported version of Ansible Base for any given collection
    * Priority 1 - Spring deliverable
* Rendering collection docs across dependencies (not on original spreadsheet)
    [Tracking on AAH-154](https://issues.redhat.com/browse/AAH-154)
    * Priority 3 ??

### Notes

## Release Train for Collections
* right now the galaxy release stream is the only way
* Release train slides: https://docs.google.com/presentation/d/1Zy-VuSpIvdQL7ZDNEd9CpWqi0GKd06__HMC2eKmvoPA/edit?ts=5e99c827#slide=id.g7762582b6f_0_0
* imagine a "release stream", e.g. RHEL 6 reached end of support, but RHEL7 and RHEL8 are active
* idea: treat galaxy as "rawhide" ... it's the latest and greatest
* question: how can we signify something is in a different train (semver does not apply on this case)
* will this live in the collection spec or no?
    * probably not in the collection spec because it doesn't make sense on galaxy itself
* idea: release streams allow "more experimental, newer" collections to be offered side-by-side trusted collections because they are separated by release trains
* needs to know start and end dates for release trains


## Content Provenance
* problem: the person installing the collection isn't the same person using the collection.
* problem: users could fork collection content, push it back and it would be difficult to sort out the difference
* Need a tool that verifies where the collection come from and if it has been changed
* Affects the CLI


## Supported ansible base for any given collection
* requires_ansible field - https://github.com/ansible-collections/cisco.nxos/blob/main/meta/runtime.yml#L2
* the metadata is part of the field 
* field is not enforced (optional)

## Rendering collection docs across dependencies
* pulp_ansible may need to send dependencies artifacts to the importer
