On 06.07.2009, at 10:07, Nicolas Cellier wrote:

> 2009/7/6 Ian Trudel <ian.trudel at gmail.com>:
>>
>> Besides, you're also missing the trick when it comes to contribution.
>> On one side, there is quick and simple community development process,
>> based on MC repositories, and on the other side, some matis+installer
>> mantis+...+whatever. While the later might better fit to the release
>> process, it is not the case when it comes to contributions.
>>
>
>
> That raises the question: where will we find a database for tracing
> changes and providing some rationale?
> Mantis might be unefficient, but discussions in a mailing list does
> not cover much of mantis classification features.
> Can it be the work of the release team to classify and document the
> work from other guys? I bet they would soon be flooded.
> It's also important to trace why a change has not been accepted. A
> mailing list is too much a short memory and some subjects might come
> back recursively.
>
> Andreas' proposition is certainly worth a try, but I don't see yet how
> these questions will be addressed.
>
> Nicolas


Good questions.

For keeping up-to-date on what's happening to the trunk the RSS feed  
is quite useful:

http://source.squeak.org/trunk/feed.rss

- Bert -