BDU Script Maintenance

Howto manage the release specific Build Docker Unreleased (BDU) scripts, for example bdu64-sales25b.

When a developer gets their component into the state "I wish to inflict my component on the rest of the community", they should add the component to the release specific BDU script. This is effectively advertising the state of the component as being (sort of like) a "release candidate". If the component can "go stable" without this intermediate step, then that is also acceptable.

The hope is that early access to the component "unrelease" means people can find integration issues before the component goes stable, and it exposes the component to OpenArbor testing.

Maintainers should ensure that the unrelease components satisfy the Component_Constraints.

---