-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 06/01/2015 06:54 AM, Haïkel wrote:
I agree with Thomas.
It will depend, if you want to maintain multiple releases and avoid retagging common build deps each time, you add a new release.
Moreover, some deps are quite common among products, so it makes sense to share them and have a common tag that your product tags inherits.
Looks like Thomas proposed as a start:
"nfv7-opnfv-latest or nfv7-opnfv-master is fine as a single tag. it's not about the number but the modularity."
Is that part of what you agree with Thomas about?
I think we just need a few +1s on schema from people who understand and will have to work the space; maybe Cloud * SIG members can give input too?[1]
- - Karsten [1] (Trying to solve the chicken/egg problem of new SIG needs where members are all new too.) - -- Karsten 'quaid' Wade .^\ CentOS Doer of Stuff http://TheOpenSourceWay.org \ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41