2012/5/23 Bert Freudenberg <bert at freudenbergs.de>:
>
> On 23.05.2012, at 20:14, Nicolas Cellier wrote:
>
>> 2012/5/23 Bert Freudenberg <bert at freudenbergs.de>:
>>> On 23.05.2012, at 19:49, Eliot Miranda wrote:
>>>
>>>> On Wed, May 23, 2012 at 10:28 AM, Bert Freudenberg <bert at freudenbergs.de>
>>>> wrote:
>>>>>
>>>>> Accessing the repository gets slower and slower due to the ever increasing
>>>>> number of versions there.
>>>>>
>>>>> To make it faster we could remove old package versions. Say, everything
>>>>> older than a year (but keep at least one version of each package). We could
>>>>> move those to an "attic" repository.
>>>>>
>>>>> Sounds good? Other ideas?
>>>>
>>>>
>>>> Sounds good.  I would have attics for each year.  The history identifies the
>>>> publication date so finding the right attic for a given version is fine.
>>>>  One attic is OK since attic access is presumably rare and  hence
>>>> performance not a premium.  But attic will be worse than trunk as soon as
>>>> older packages are moved there.
>>>
>>>
>>> Igor's suggestion is worth considering. One could make a new trunk
>>> repository for each release.
>>>
>>> To me, multiple attics sounds better than multiple trunks. But one attic
>>> sounds better than multiple, because, it's simpler, and YAGNI, and we're
>>> going to buy a faster machine soonish ;)
>>>
>>> - Bert -
>>>
>>>
>>
>> I would prefer a delimitation per release than per year...
>> The previous release files would stay in trunk until next release...
>>
>> I would also duplicate the last file if release n-1 as first file in release n.
>>
>> Nicolas
>
> What about Eliot's argument that limiting by year makes it simpler to find the right repository for a specific version?
>
> - Bert -
>

Maybe...