Just one SNAPSHOT for each maintained released should be plenty. A dev is either testing off of the latest build or a specific version, not necessarily a specific day's build. So for the snapshots:
trunk: 1.10-SNAPSHOT 1.9.x: 1.9.0-SNAPSHOT 1.8.x: 1.8.4-SNAPSHOT 1.7.x: 1.7.4-SNAPSHOT 1.6.x: 1.6.5-SNAPSHOT (and then we have these for the proper releases as well: 1.8.3, 1.8.2, 1.8.1, 1.8.0, 1.7.3, 1.7.2, 1.7.1, 1.7.0, 1.6.4, 1.6.3, 1.6.2, 1.6.1, 1.6.0) 1.9-alpha, 1.9-beta, 1.9-rc, 1.9-rc2, 1.9rc34, etc could be removed once 1.9.0 is released. So thats approx 22 diff versions up there. Even with us including the war file in that, thats less than 700MB. Ben On Fri, Dec 16, 2011 at 2:10 AM, Darius Jazayeri <[email protected]>wrote: > I don't think we need any history. Just the latest snapshot for each > release. > > -Darius (by phone) > > On Dec 15, 2011 2:21 PM, "Michael Downey" <[email protected]> wrote: > > These are now publishing to the Snapshots repository on our nightly > builds. I am concerned about growth of the size of the repository, though. > I'd like to create a scheduled task in Nexus to remove old snapshots from > the Snapshots repository. Three questions: > > 1. Is this OK? > 2. How many do we need (in terms of days and/or N versions)? > 3. Do we need to keep snapshots for released versions? > > Michael > > > > On Thursday, December 1, 2011 at 11:09 AM, Mark Goodrich wrote: > > > > Michael-- > > > > I'd like to be a... > > Click here to > unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from > OpenMRS Developers' mailing list > > ------------------------------ > Click here to > unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from > OpenMRS Developers' mailing list > _________________________________________ To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
