Hi Norbert 2018-05-25 23:50 GMT+03:00 Norbert Hartl <norbert@hartl.name>:
Really?? Donât you think the overhead is massive compared to the gain?
I am sure that you were agreed with this when we push Beacon two yeas ago. But look at my explanation in previous mail.
Norbert
Am 25.05.2018 um 21:08 schrieb Tudor Girba <tudor@tudorgirba.com>:
Hi,
Yes, we want to have the concrete loggers managed with separate baselines. I would also put them in individual repositories.
Cheers, Doru
On May 25, 2018, at 5:58 PM, Denis Kudriashov <dionisiydk@gmail.com> wrote:
2018-05-25 17:21 GMT+03:00 Stephan Eggermont <stephan@stack.nl>: Denis Kudriashov <dionisiydk@gmail.com> wrote:
Hi.
I was looking at Beacon again to prepare integration. Some changes was needed in baseline for better granularity. So I send pull request because I have no permissions.
But now I remember that we had idea to integrate only core part of Beacon which requires MemoryLogger and TranscriptLogger. And we wanted to manage logger backends using separate baselines. So we need separate repos to have separate versioning.
Why would you want separate baselines for that? And on top of that separate repos?
Because when you will fix or improve Beacon-SysLog you will probably do not want to update Beacon-Core version which will force you to update Pharo (where SysLog is not loaded).
Stephan
-- www.tudorgirba.com www.feenk.com
"In a world where everything is moving ever faster, one might have better chances to win by moving slower."