CHANGELOG or BUGTRACKER

As my posts have been 2 times removed in 6.32.3 thread with comment:

Once again remember this is a topic about 6.32.3 version release. If you have suggestions about changelog or other features, post it in the appropriate thread.

I am asking here as I do not know what “proper thread” means:

This fix is for /1 /2 specific networks, in 6.32.2 networks were changed incorrectly.

[admin@rack1_b2] /routing bgp network> add network=0.0.0.0/1
[admin@rack1_b2] /routing bgp network> add network=128.0.0.0/1
[admin@rack1_b2] /routing bgp network> add network=0.0.0.0/2
[admin@rack1_b2] /routing bgp network> add network=64.0.0.0/2
[admin@rack1_b2] /routing bgp network> add network=128.0.0.0/2
[admin@rack1_b2] /routing bgp network> add network=192.0.0.0/2

[admin@rack1_b2] /routing bgp network> print
Flags: X - disabled

NETWORK SYNCHRONIZE

0 0.0.0.0/25 yes
1 0.0.0.128/25 yes
2 0.0.0.0/26 yes
3 0.0.0.64/26 yes
4 0.0.0.128/26 yes
5 0.0.0.192/26 yes

Three questions arise:

  1. Why such info as error + fix could not be in changelog.txt ? I know…changelog is downloaded in Winbox to show changes…too large…OK…maybe we should have “short story” in changelog.txt and “long story” in off-line changelog_extended_version.txt ?

  2. Why there is no public bugtrack ? Even small one maintained by MKT, to prevent flooding it with all possible “bugs”, should be better than none.

  3. Could changelog for RC be lead by date to easy follow what changes are made ? It is not easy to save each changelog version to compare it each time.