>Regarding snapshots and the way your QA works it all looks like you have >adjusted your team workflow to the features the maven tool provides.
Yes, this comes from years of using the tool, but is also adapted to our current environment. >And >these features are not so flexible to cover all requirements of ISO >driven development for instance. For example, need to distinguish and be >able to recreate everything that gets officially built. If you say, that >in this case we need to do only releases, then we don't need snapshots >at all and would loose an option to use different repos for different >build types. I don't understand this statement. We produce releases whenever it needs to be traceable, those releases are deterministic and rebuildable if needed from source. In a previous company, the snapshots were not used by qa, all deliveries to qa where release builds. We used a 4 digit versioning where the last number was just a build number. We did this because it wasn't known ahead of time if a given build would pass qa and be officially released. How you use the system is up to your individual requirements. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
