Hi Eliot,

We do not copy package versions from Trunk/Treated to the inbox. In this case, most likely, a server reboot triggered some Image-Filesystem sync protocol and hence mails were sent again for old versions. This happens quite rarely. It has happened in the past. Even though, I would flag this behaviour as a bug.

Whoever took care of this one, thanks for that voluntary administration effort!

Best,
Marcel
________________________________
From: Squeak-dev <squeak-dev-bounces at lists.squeakfoundation.org> on behalf of Eliot Miranda <eliot.miranda at gmail.com>
Sent: Friday, July 15, 2022 10:45:55 PM
To: The general-purpose Squeak developers list <squeak-dev at lists.squeakfoundation.org>
Subject: [squeak-dev] The Inbox

Hi All,

    I was dismayed to see a large number of emails informing me of packages that were committed to trunk that had been committed to Inbox.  Apart from the annoying noise (I already have to delete many commit messages a day only to see the ones i'm interested in), I have to ask why we are copying packages to Inbox. Doesn't this defeat the purpose?  My understanding is that Inbox is a place for non-core developers to submit proposed changes, and for core-developers to submit proposed code that needs review.  Duplicating the packages that are already in trunk simply drowns out those submissions.  How are we supposed to recognise suggested submissions if they're lost within the tide of trunk submissions?

_,,,^..^,,,_
best, Eliot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20220716/e6ea5a6d/attachment.html>