Hi Christoph,

> From the perspective of someone who has only gotten to know SqueakSource
> from the client side: The possibility to enumerate *all* trunk versions is
> important for me in several situations.
>
Would you mention or describe one or more of those situations, because...


> It would be quite a shame if one could no longer access the full ancestry
> of a version or browse an ancient version of any package through the UI.
>
... this change would not affect the above use cases.  They could still be
accomplished via the "History" button, because it accesses those very old
versions *directly*, by name or UUID.  What we're talking about here is
just the "list of files", NOT the list of ancestors, which we still have.
The lists in the Repository browsers wouldn't show everything in the
ancestry, but the ancestry is a better place to review that anyway.  I'm
not convinced there is _any_ use case that needs a list of *all* Repository
files (Versions) since the beginning of time.  If there is one, it's on an
eternal linear degradation path, and some alternative approach should at
least be considered.

> The release notes generator in the ReleaseBuilder could also be affected,
> I think.
>
It shouldn't be.  As above, it's in the ancestry.


> With a view to modern REST and GraphQL APIs, would it be possible to add
> support for some parameters to the requests in question to enable
> pagination or filter the retrieved information vertically (i.e., leave out
> some metadata)?
>
I'm sure it is, but right now I'm just looking for TSTTCPW for getting
trunk development back online.  I think the round-robin with date-based
balancing sounds like a good possibility for something that could be done
quickly.

Best,
  Chris

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20221227/5612e117/attachment.html>