Laca: I prefer "d". My second choice would be "a".
> d) Create individual spec file repos for groups of modules > that are on the same release schedule (typically those > originating from the same upstream community), branch > them according to their own schedules. > > This gives maximum flexibility for selecting the > branches for the builds, but makes it difficult > to find the spec that belongs to a specific build. I would think that a tagging mechanism could be defined to address this difficulty. Or perhaps we could define some metadata mechanism that automates building the "right" tags from the appropriate repositories to recreate what we think of as a "build". Brian
