I think we have similar requirements for OpenStack; specifically I'd like to have the same structure for each openstack series being supported at a given point in time
- newton
- edge: Current git snapshot (untested)
- beta: Tested git snapshots, typically done after new features land
- candidate: Latest upstream stable release soaking/smoketesting
- stable: Latest stable release after it's sat for a few days in candidate
- mitaka
- edge: Current git snapshot (untested)
- beta: Tested git snapshots, typically done after new features land
- candidate: Latest upstream stable release soaking/smoketesting
- stable: Latest stable release after it's sat for a few days in candidate
....
and so on (today this would include liberty and kilo as well) - this could be achieved with a naming schema for snaps which includes the openstack release name.
I think we have similar requirements for OpenStack; specifically I'd like to have the same structure for each openstack series being supported at a given point in time
- newton smoketesting
- edge: Current git snapshot (untested)
- beta: Tested git snapshots, typically done after new features land
- candidate: Latest upstream stable release soaking/
- stable: Latest stable release after it's sat for a few days in candidate
- mitaka smoketesting
- edge: Current git snapshot (untested)
- beta: Tested git snapshots, typically done after new features land
- candidate: Latest upstream stable release soaking/
- stable: Latest stable release after it's sat for a few days in candidate
....
and so on (today this would include liberty and kilo as well) - this could be achieved with a naming schema for snaps which includes the openstack release name.