Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [egit-dev] retention policy for builds

What happens when 1.0.1 is released, will the updates-1.0 site still
have the 1.0.0 release?

For Mylyn we use composites for that purpose that aggregate releases
from an archive that retains all released versions forever (older
versions move to eventually). The maintenance site
for the each stream serves all released versions of a stream. That
allows integrator to use strict version constraints while still
providing the convenience of a site that serves the latest release.

The other nice property of composites sites is that you can move
things to the archive without affecting integrators.


On Tue, Jun 14, 2011 at 11:07 PM, Chris Aniszczyk <caniszczyk@xxxxxxxxx> wrote:
> On Tue, Jun 14, 2011 at 4:05 PM, Steffen Pingel
> <steffen.pingel@xxxxxxxxxxx> wrote:
>> I would prefer an update site that will serve the release build
>> "forever". Looking at ~/downloads/egit/updates-* it seems that these
>> only have the latest service release of a particular stream but I
>> could not find older service releases (e.g. 0.11.0).
> Sites that are labeled ~/downloads/egit/updates-<version> should be
> there forever... e.g., updates-0.12
> When we ship 1.0 tomorrow, you'll find 1.0 in updates-1.0 forever.
> Does that make sense?
> --
> Cheers,
> Chris Aniszczyk
> +1 512 961 6719

Steffen Pingel
Senior Developer,

Back to the top