Community discussions

 
User avatar
normis
MikroTik Support
MikroTik Support
Topic Author
Posts: 23590
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

v6.30.x bugfix release

Wed Jul 15, 2015 12:00 pm

We have published v6.30.1 bugfix only release. The only changes here are verified fixes, no new features have been added. Since the current v6.29 version does not yet have the branch support, 6.30.1 will be offered as the regular next upgrade. The "Branch" selector will become available in v6.31
What's new in 6.30.1 (2015-Jul-14 11:22):

*) quickset - fixed HomeAP mode;
*) lte - Fixes bug that causes Sierra Wireless modems with LTE interface to change interface name;
*) trafflow: fix in-interface reporting in flow;
*) ipsec - disallow changing dynamic peer;
*) quickset - crashes introduced in 6.30 fixed
*) fixed :execute file=
*) bonding: fix arp monitoring in active backup mode
To clarify how the new release system will work, we made an image
Screenshot 2015-07-15 11.58.18.png
A small addendum: the Bugfix only will only contain verified fixes, and no new features. The Current release contains the same fixes but also new features and other improvements, sometimes also less critical fixes than in Bugfix. And finally the Release Candidate is more likely to a nightly build. We will not to intensive testing before publishing these, only quick check if upgrade can be done and if most features work fine.
You do not have the required permissions to view the files attached to this post.
No answer to your question? How to write posts
 
User avatar
rextended
Forum Guru
Forum Guru
Posts: 2932
Joined: Tue Feb 25, 2014 12:49 pm
Location: Capalbio, Tuscany, Italy

Re: v6.30.1 bugfix release

Wed Jul 15, 2015 12:14 pm

WARNING: "/tool user-manager user export" DO NOT EXPORT USERNAMEs
I'm Italian, not English. Sorry for my imperfect grammar.
 
User avatar
normis
MikroTik Support
MikroTik Support
Topic Author
Posts: 23590
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: v6.30.1 bugfix release

Wed Jul 15, 2015 12:17 pm

WARNING: "/tool user-manager user export" DO NOT EXPORT USERNAMEs
Yes, curently not fixed, but known.
No answer to your question? How to write posts
 
User avatar
macgaiver
Forum Guru
Forum Guru
Posts: 1688
Joined: Wed May 18, 2005 5:57 pm
Location: Sol III, Sol system, Sector 001, Alpha Quadrant

Re: v6.30.1 bugfix release

Wed Jul 15, 2015 12:34 pm

somebody wake me... it can't be really happening..

when will we get RC versions the same way? it will make my life so much more easier
With great knowledge comes great responsibility, because of ability to recognize id... incompetent people much faster.
 
User avatar
normis
MikroTik Support
MikroTik Support
Topic Author
Posts: 23590
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: v6.30.1 bugfix release

Wed Jul 15, 2015 12:38 pm

We have to make support for multiple independent Changelog files, then we will also release RC this way, and remove the RC section that is currently below the download boxes. It will go into the dropdown menu on the Download page and in your routers.
No answer to your question? How to write posts
 
User avatar
tomaskir
Trainer
Trainer
Posts: 1102
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: v6.30.1 bugfix release

Wed Jul 15, 2015 1:41 pm

Awesome job on the new release system!

Thank you for doing it!
Unimus - configuration management, automation and backup solution
Mass Config Push, network-wide RouterOS upgrades, and more!
 
User avatar
omega-00
Forum Guru
Forum Guru
Posts: 1165
Joined: Sat Jun 06, 2009 4:54 am
Location: Brisbane, Australia
Contact:

Re: v6.30.1 bugfix release

Wed Jul 15, 2015 1:45 pm

Awesome work guys, can't wait to give it a try :-)
brightwifi.com | mikrotik-routeros.com | MTCNA,MTCWE.MTCTCE | Give karma where due
 
User avatar
nz_monkey
Forum Guru
Forum Guru
Posts: 1792
Joined: Mon Jan 14, 2008 1:53 pm
Location: Straya
Contact:

Re: v6.30.1 bugfix release

Wed Jul 15, 2015 1:47 pm

THANK YOU !!!

This is easy to understand, and will hopefully result in better RouterOS stability and lower load on Mikrotik support.
http://thebrotherswisp.com/ | Mikrotik MTCNA, MTCRE, MTCINE | Fortinet FTCNA, FCNSP, FCT | Extreme Networks ENA
 
User avatar
docmarius
Forum Guru
Forum Guru
Posts: 1196
Joined: Sat Nov 06, 2010 12:04 pm
Location: Timisoara, Romania
Contact:

Re: v6.30.1 bugfix release

Wed Jul 15, 2015 4:06 pm

Great approach, way to go Mikrotik team!
Torturing CCR1009-7G-1C-1S+, RB450G, RB750GL, RB951G-2HnD, RB960PGS, RB260GSP, OmniTIK 5HnD and NetMetal 922UAGS-5HPacD + R11e-5HnD in my home network.
 
KBV
Frequent Visitor
Frequent Visitor
Posts: 72
Joined: Mon Nov 10, 2014 7:02 pm

Re: v6.30.1 bugfix release

Wed Jul 15, 2015 4:08 pm

you are somewhere lost x86 "Extra packages" in 6.30(x) :)
link on the download page is not available, but the package can be downloaded if you enter a direct link
 
gius64
Member Candidate
Member Candidate
Posts: 197
Joined: Tue Jan 14, 2014 3:43 pm

Re: v6.30.1 bugfix release

Wed Jul 15, 2015 4:15 pm

WARNING: "/tool user-manager user export" DO NOT EXPORT USERNAMEs
Yes, curently not fixed, but known.
Also print (and print via API) doesn't print username.

When will it be fixed? MikroTik support says 6.31, I hope it will be released soon. This is a critical bug for who use API with user-manager, so I expected it fixed in a short time.
 
User avatar
normis
MikroTik Support
MikroTik Support
Topic Author
Posts: 23590
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: v6.30.1 bugfix release

Wed Jul 15, 2015 4:20 pm

WARNING: "/tool user-manager user export" DO NOT EXPORT USERNAMEs
Yes, curently not fixed, but known.
Also print (and print via API) doesn't print username.

When will it be fixed? MikroTik support says 6.31, I hope it will be released soon. This is a critical bug for who use API with user-manager, so I expected it fixed in a short time.
Both issues will be fixed in v6.31rc7
No answer to your question? How to write posts
 
ANZO
just joined
Posts: 1
Joined: Wed Jul 15, 2015 4:40 pm

Re: v6.30.1 bugfix release

Wed Jul 15, 2015 4:44 pm

PPP connections dead after update =\
1. connecting
2. auth
3. terminated
without any detail log.

EDIT:
After update in all PPP connections Profile changed from "default" to "default-encryption".
I changed this back to "default", but router didn't share internet from PPP to internet (masq action exist).
Resetring all configs and reconfiguration fixed this issue.
Last edited by ANZO on Wed Jul 15, 2015 9:17 pm, edited 1 time in total.
 
arturrenato
just joined
Posts: 7
Joined: Fri Oct 29, 2010 3:44 am

Re: v6.30.1 bugfix release

Wed Jul 15, 2015 7:02 pm

It's not working to use "0.0.0.0" (dynamic IP address) as the "S.A. Src. Address" on IPsec Police.
 
tvrebac
just joined
Posts: 8
Joined: Wed Feb 11, 2015 6:58 pm

Re: v6.30.1 bugfix release

Wed Jul 15, 2015 10:15 pm

Please tell me what is changed with SSL certificates, since 6.30 when I import my ca.crt it is being recognised as plain certificate, not CA. In versions prior to 6.30 the same ca.crt file is recognised as CA.

Also, something is messed with "/tool fetch" which I use in dyndns updater script, I get an error "failure: closing connection: <400 Bad Request> 204.13.248.114:80".
The script works fine in 6.29.1 and earlier.

Here is the script:
# DynDNS update script
# using http://checkip.dyndns.com/index.html
# response should be:
#	<html><head><title>Current IP Check</title></head><body>Current IP Address: aaa.bbb.ccc.ddd</body></html>
:local mDebugging "true";
:local mCheckIPURL "http://checkip.dyndns.com/index.html";
:local mFileName "dyndns.checkip.html";
:local mUsername "test";
:local mPassword "test";
:local mHostname "test.dyndns.org";
:local mDynDNSURL "members.dyndns.com";
:local mStartStr ": ";
:local mEndStr "</body>";

#:global mForceUpdate;
:global mPreviousIP;

# log some data, disable this while not debugging
:if ($mDebugging = true) do={
    :log info ("UpdateDynDNS: username = $mUsername");
    :log info ("UpdateDynDNS: password = $mPassword");
    :log info ("UpdateDynDNS: hostname = $mHostname");
}

# get the current IP address
/tool fetch mode=http url="$mCheckIPURL" dst-path="$mFileName";
:delay 1;
:local mCheckIPResponse [ /file get "$mFileName" contents ];
/file remove "$mFileName";

# parse HTTP response
:local mIPStart [ :find "$mCheckIPResponse" "$mStartStr" -1 ];
:set mIPStart ($mIPStart+2);
:local mIPEnd [ :find "$mCheckIPResponse" "$mEndStr" -1 ];
:local mCurrentIP [ :pick "$mCheckIPResponse" "$mIPStart" "$mIPEnd" ];

# log some data, disable this while not debugging
:if ($mDebugging = true) do={
    :log info ("UpdateDynDNS: mCheckIPResponse = $mCheckIPResponse");
    :log info ("UpdateDynDNS: mIPStart = $mIPStart");
    :log info ("UpdateDynDNS: mIPEnd = $mIPEnd");
    :log info ("UpdateDynDNS: mCurrentIP = $mCurrentIP");
}
:if ($mPreviousIP != $mCurrentIP) do={
    :local mUpdateURL "/nic/update\?hostname=$mHostname&myip=$mCurrentIP&wildcard=NOCHG&mx=NOCHG&backmx=NOCHG";
    :local mFileName ("dyndns.".$mHostname);
    /tool fetch address="$mDynDNSURL" src-path="$mUpdateURL" mode=http user="$mUsername" password="$mPassword" dst-path="$mFileName";
    :delay 1;
    :local mTmp [ /file get "$mFileName" contents ];
    :if ($mDebugging = true) do={
        :log info ("UpdateDynDNS: mUpdateURL = $mUpdateURL");
        :log info ("UpdateDynDNS: mFileName = $mFileName");
        :log info ("UpdateDynDNS: mDynDNSURL $mDynDNSURL");
        :log info ("UpdateDynDNS: mTmp=$mTmp");
    }
    /file remove "$mFileName";
    :set $mPreviousIP $mCurrentIP
}
 
User avatar
honzam
Forum Guru
Forum Guru
Posts: 2169
Joined: Wed Feb 27, 2008 10:27 pm
Location: Czech Republic

Re: v6.30.1 bugfix release

Wed Jul 15, 2015 10:56 pm

Awesome job on the new release system!

Thank you for doing it!
Yes, this is the best change in recent years!
Thanks
LAN, FTTx, Wireless. ISP operator
 
shifto
just joined
Posts: 13
Joined: Wed Jul 15, 2015 1:58 am

Re: v6.30.1 bugfix release

Thu Jul 16, 2015 1:08 am

Really like this change!
 
dadoremix
Frequent Visitor
Frequent Visitor
Posts: 98
Joined: Sat May 14, 2011 11:31 am

v6.30.1 bugfix release

Thu Jul 16, 2015 1:41 am

+1 for dyndns script, 6.29.1!working and 6.30 broken
 
User avatar
ufm
Frequent Visitor
Frequent Visitor
Posts: 96
Joined: Fri Nov 15, 2013 12:02 pm
Location: Ukraine

Re: v6.30.1 bugfix release

Thu Jul 16, 2015 2:38 am

Hi!

net flow still broken (see Ticket#2015071166000057)

WBR,
Fyodor.
 
User avatar
paoloaga
Member Candidate
Member Candidate
Posts: 215
Joined: Tue Mar 08, 2011 2:52 am
Location: Vaprio d'Agogna (NO) - Italy
Contact:

Re: v6.30.1 bugfix release

Thu Jul 16, 2015 3:34 am

We have to make support for multiple independent Changelog files, then we will also release RC this way, and remove the RC section that is currently below the download boxes. It will go into the dropdown menu on the Download page and in your routers.
I see that in the dropdown menu, there are the following versions:

Bugfix: V6.30.1
Current: V6.30
Legacy: V5.26


If V6.30.1 is exactly as the V6.30 with bugfixes and no new features, what's the point for listing v6.30?

It is useless to download a version of the software that does the same things but includes old bugs. Am I missing something?
 
Hyperus
just joined
Posts: 2
Joined: Thu Jul 16, 2015 3:55 am

Re: v6.30.1 bugfix release

Thu Jul 16, 2015 4:03 am

Hi, I upgraded to 6.30.1 last night from 6.29.1 and also in turn to bootrom firmware 3.24 from 3.22.
I always install upgrade + new ntpd and thenupgrade bootrom firmware in a second reboot.

6.30.1 broke my VoIP to my second PABX server.

Running Bria 3.xx on latest OSX connecting to 2 different SIP servers via Mikrotik UDP/1701 L2TP VPN's
Server 1 : 10.1.100.253 (via VPN1)
Server 2 : 192.168.14.76 (via VPN2)

Server 1 login ok, Server 2 would not connect - SIP error 408.
The second server does also have a public IP which is for external handsets in other countries (ACL'ed of course).
Tried Server 2 connection via its public ip - also failed with SIP error 408
Rebooted OSX
Same errors still.

I need these both for my business so did not stop to take packet captures.
I reverted to 6.29.1 and ntdp 6.29.1 as I needed access urgently
All SIP issues resolved after reverting to 6.29.1
I would note firmware is still 3.24 offering upgraded firmware of 3.22

Thoughts anyone ?
Concurrent ALG issue ?

Hyp
 
pants6000
Frequent Visitor
Frequent Visitor
Posts: 64
Joined: Fri Sep 26, 2014 5:30 am

Re: v6.30.1 bugfix release

Thu Jul 16, 2015 4:42 am

Does "bug fixes" include security issues? If so, how long will a given release be supported?
 
User avatar
dimi
just joined
Posts: 9
Joined: Thu Feb 05, 2015 1:32 am
Location: Ukraine

Re: v6.30.1 bugfix release

Thu Jul 16, 2015 4:43 am

ISSUE with WiFi hide password checkbox.

Quickset section:
WiFi Password - Hide >> CHECKBOX issue. When checkbox is checked and settings are applied, after the next enter to winbox it's already unchecked.

Devices: 2011UAS-2HnD, Groove A-52HPn, RB951G-2HnD
Firmware: 3.24
RouterOS: 6.30

Please fix that issue in the new ROS release.

Thamks.
 
barkas
Member Candidate
Member Candidate
Posts: 258
Joined: Sun Sep 25, 2011 10:51 pm

v6.30.1 bugfix release

Thu Jul 16, 2015 8:47 am

Still kills my rb450g, last working os is 6.29.1.
 
User avatar
normis
MikroTik Support
MikroTik Support
Topic Author
Posts: 23590
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: v6.30.1 bugfix release

Thu Jul 16, 2015 9:24 am

We have to make support for multiple independent Changelog files, then we will also release RC this way, and remove the RC section that is currently below the download boxes. It will go into the dropdown menu on the Download page and in your routers.
I see that in the dropdown menu, there are the following versions:

Bugfix: V6.30.1
Current: V6.30
Legacy: V5.26


If V6.30.1 is exactly as the V6.30 with bugfixes and no new features, what's the point for listing v6.30?

It is useless to download a version of the software that does the same things but includes old bugs. Am I missing something?
When we release v6.31, it will take this place. Currently we included 6.30 for those, who don't want to risk any other version and need some packages for their current install
No answer to your question? How to write posts
 
User avatar
normis
MikroTik Support
MikroTik Support
Topic Author
Posts: 23590
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: v6.30.1 bugfix release

Thu Jul 16, 2015 9:30 am

+1 for dyndns script, 6.29.1!working and 6.30 broken
more likely that your script is broken. scripting language improves over time, the scripts need to be updated. MikroTik did not make th DynDNS script, you have to ask the person who wrote it, or maybe post this question in the "Scripting" section, someone could update it.
No answer to your question? How to write posts
 
User avatar
normis
MikroTik Support
MikroTik Support
Topic Author
Posts: 23590
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: v6.30.1 bugfix release

Thu Jul 16, 2015 9:30 am

Still kills my rb450g, last working os is 6.29.1.
Please describe "kills"
No answer to your question? How to write posts
 
User avatar
normis
MikroTik Support
MikroTik Support
Topic Author
Posts: 23590
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: v6.30.1 bugfix release

Thu Jul 16, 2015 9:32 am

Does "bug fixes" include security issues? If so, how long will a given release be supported?
Initially we plan to maintain X.YY.Z for 4-6 weeks, then it will be replaced by X.YZ.Z and X.YY.Z will not be updated anymore.

Otherwise, in two years we would have to backport a security fix to 24 different versions.
No answer to your question? How to write posts
 
User avatar
eworm
Member Candidate
Member Candidate
Posts: 171
Joined: Wed Oct 22, 2014 9:23 am
Location: Oberhausen, Germany
Contact:

Re: v6.30.1 bugfix release

Thu Jul 16, 2015 11:09 am

Does "bug fixes" include security issues? If so, how long will a given release be supported?
Initially we plan to maintain X.YY.Z for 4-6 weeks, then it will be replaced by X.YZ.Z and X.YY.Z will not be updated anymore.

Otherwise, in two years we would have to backport a security fix to 24 different versions.
You could think about picking LTS versions. Make 6.30 an LTS release and support it for two years. 6.31.x will receive updates for some weeks only, same for 6.32.x, ...
Any time in future you would pick a new LTS version and support that for two years.
 
User avatar
normis
MikroTik Support
MikroTik Support
Topic Author
Posts: 23590
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: v6.30.1 bugfix release

Thu Jul 16, 2015 11:15 am

We will see how this new plan goes, and will think about LTS in future. Thanks for the suggestion.
No answer to your question? How to write posts
 
florentrivoire
newbie
Posts: 43
Joined: Wed Feb 25, 2015 12:02 pm

Re: v6.30.1 bugfix release

Thu Jul 16, 2015 12:14 pm

We will see how this new plan goes, and will think about LTS in future. Thanks for the suggestion.
I've been following the new "feature" for "release branchs", and even if I think the new plan is better than the current situation, I do believe that LTS versions would be a much better idea (without too much work or complexity) !
Because, with the process that you have described now, each version will only be "supported" for 1 or 2 months, which is very short !

So I'd prefer to have some LTS versions (for example starting with 6.31) that will receive bugfix+security updates for something like 1 year. During that time, you release "standard" versions (6.32, 6.33, 6.34, 6.35). And those standard versions will only be supported until next version (a few weeks later) and that will be forgotten as that.

Example (in chronological order) :
  1. 6.31 is out, it's a LTS version, it will be supported until next LTS version is released (~ 1 year later).
  2. Then 6.31.1 (bugfix LTS) is released
  3. Then 6.31.2 (bugfix LTS) is released
  4. A few weeks later, 6.32 (standard version) is out
  5. Then 6.32.1 (bugfix std) is released
  6. Then 6.32.2 (bugfix std) is released
  7. A few weeks later, 6.33 (standard version) is out ==> 6.32 (previous standard) is forgotten
  8. Then 6.33.1 (bugfix std) is released
  9. Then 6.31.3 (bugfix LTS) is released
  10. A few weeks later, 6.34 (standard version) is out ==> 6.33 (previous standard) is forgotten
  11. Then 6.31.4 (bugfix LTS) is released
  12. Then 6.34.1 (bugfix std) is released
  13. Then 6.31.5 (bugfix LTS) is released
  14. A few weeks later, 6.35 (standard version) is out ==> 6.34 (previous standard) is forgotten
  15. Then 6.31.6 (bugfix LTS) is released
  16. Then 6.35.1 (bugfix std) is released
  17. A few weeks later, 6.36 (LTS version) is out ==> 6.31 (previous LTS) and 6.35 (previous standard) are forgotten
  18. Then 6.36.1 (bugfix LTS) is released
  19. ...
And at any given time, only 2 versions needs to be supported :
[*] the latest LTS version
[*] the latest standard version
So, no need to backport every fix to many versions ==> so probably doable for Mikrotik without major dev ressources.

And users need to choose between :
[*] LTS : missing some really-new features, but got continuous bugfix for 1 year WITHOUT MAJOR CHANGES ==> focus on stability
[*] Standard : all new features, but no update after a few weeks without upgrading to next release (which will include new features, so potential breaking configs) ==> focus on new features
 
User avatar
normis
MikroTik Support
MikroTik Support
Topic Author
Posts: 23590
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: v6.30.1 bugfix release

Thu Jul 16, 2015 12:35 pm

Good description, florentrivoire. Thanks. I had already understood what you all request, we simply need to take one step at a time. When the current new "metro" plan (as in the original image) is stremalined and working, we will consider expanding it like you describe.
No answer to your question? How to write posts
 
florentrivoire
newbie
Posts: 43
Joined: Wed Feb 25, 2015 12:02 pm

Re: v6.30.1 bugfix release

Thu Jul 16, 2015 12:39 pm

OK, keep working :D
We are going to the right direction !
 
User avatar
macgaiver
Forum Guru
Forum Guru
Posts: 1688
Joined: Wed May 18, 2005 5:57 pm
Location: Sol III, Sol system, Sector 001, Alpha Quadrant

Re: v6.30.1 bugfix release

Thu Jul 16, 2015 12:43 pm

I was expecting proposal like that :) Lets not jump too far ahead, to implement version policy like that you need system in place in development process. Current change is already a huge step forwards, and i can imagine MT is still adjusting and will continue to adjust for this system for some time until it is perfected.

also you need to note that differentiation in releases comes at the cost of new feature development speed - you need to test much more with different releases etc. And we all love new features and the speed they are implemented.
With great knowledge comes great responsibility, because of ability to recognize id... incompetent people much faster.
 
vortex
Forum Veteran
Forum Veteran
Posts: 706
Joined: Sat Feb 16, 2013 6:10 pm

Re: v6.30.1 bugfix release

Thu Jul 16, 2015 1:06 pm

You must not forget the previous standard version the moment a new current version is released. That is the whole point of the bugfix stream, not trusting new current versions.
 
florentrivoire
newbie
Posts: 43
Joined: Wed Feb 25, 2015 12:02 pm

Re: v6.30.1 bugfix release

Thu Jul 16, 2015 1:09 pm

You must not forget the previous standard version the moment a new current version is released. That is the whole point of the bugfix stream, not trusting new current versions.
If you're responding to me and my message of this morning : remember that the philosophy "dont trust new version, want bugfix" match the LTS versions that I described, and not the versions that I called "standard".
 
vortex
Forum Veteran
Forum Veteran
Posts: 706
Joined: Sat Feb 16, 2013 6:10 pm

Re: v6.30.1 bugfix release

Thu Jul 16, 2015 1:16 pm

Bugfix stream should be available for a reasonable time for all versions, not only LTS.

And an upgrade should not take you automatically to the latest version in the stream, it should be possible to upgrade along the stream one step at a time.

Of course, versions with massive problems should be forgotten.
 
florentrivoire
newbie
Posts: 43
Joined: Wed Feb 25, 2015 12:02 pm

Re: v6.30.1 bugfix release

Thu Jul 16, 2015 1:23 pm

Bugfix stream should be available for a reasonable time for all versions, not only LTS.
I don't think this is reasonable, because of the work this would require for Mikrotik team (you're requesting them to maintain : 1 LTS + several "standard" versions).
 
Zwodka
Frequent Visitor
Frequent Visitor
Posts: 69
Joined: Fri Sep 19, 2014 9:41 pm
Location: Hungary

Re: v6.30.1 bugfix release

Thu Jul 16, 2015 1:33 pm

+1 for florentrivoire LTS plant
 
User avatar
paoloaga
Member Candidate
Member Candidate
Posts: 215
Joined: Tue Mar 08, 2011 2:52 am
Location: Vaprio d'Agogna (NO) - Italy
Contact:

Re: v6.30.1 bugfix release

Thu Jul 16, 2015 1:37 pm

Bugfix stream should be available for a reasonable time for all versions, not only LTS.
I don't think this is reasonable, because of the work this would require for Mikrotik team (you're requesting them to maintain : 1 LTS + several "standard" versions).
I think that LTS should be granted maintenance for a known length of time. For example:

6.30 is picked to be LTS, it should be maintained for at least X months (suppose 24). A year later, 6.50 is picked as LTS. For the next year both 6.30 and 6.50 will be maintained, after which 6.30 may be not maintained anymore.

if you maintain only one LTS release each time, you are pushing a forced/unplanned update.
 
Hyperus
just joined
Posts: 2
Joined: Thu Jul 16, 2015 3:55 am

Re: v6.30.1 bugfix release

Thu Jul 16, 2015 1:53 pm

Maintaining LTS = Price goes up.... -1 from me for LTS

Hyp
 
jarda
Forum Guru
Forum Guru
Posts: 7560
Joined: Mon Oct 22, 2012 4:46 pm

Re: v6.30.1 bugfix release

Thu Jul 16, 2015 2:15 pm

Please, put back "all architecture" single zip file download link on the download page. Thank you.
 
User avatar
ufm
Frequent Visitor
Frequent Visitor
Posts: 96
Joined: Fri Nov 15, 2013 12:02 pm
Location: Ukraine

Re: v6.30.1 bugfix release

Thu Jul 16, 2015 2:17 pm

\
I've been following the new "feature" for "release branchs", and even if I think the new plan is better than the current situation, I do believe that LTS versions would be a much better idea (without too much work or complexity) !
Because, with the process that you have described now, each version will only be "supported" for 1 or 2 months, which is very short !
Semi mythical 7.0 - break this chain.
 
User avatar
mandrade
Member Candidate
Member Candidate
Posts: 104
Joined: Fri Sep 08, 2006 12:35 pm
Location: Brazil
Contact:

Re: v6.30.1 bugfix release

Thu Jul 16, 2015 2:21 pm

 
vortex
Forum Veteran
Forum Veteran
Posts: 706
Joined: Sat Feb 16, 2013 6:10 pm

Re: v6.30.1 bugfix release

Thu Jul 16, 2015 2:51 pm

Bugfix stream should be available for a reasonable time for all versions, not only LTS.
I don't think this is reasonable, because of the work this would require for Mikrotik team (you're requesting them to maintain : 1 LTS + several "standard" versions).
I did not say that they should maintain a bug fix stream for a long time after new current versions have been released, but that it should be selectable for download.

So, for example:

Release timeline:

6.31
6.31.1
6.31.2
6.32
6.31.3
6.32.1
6.33
<6.31 work stops but still selectable for install>
 
User avatar
normis
MikroTik Support
MikroTik Support
Topic Author
Posts: 23590
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: v6.30.1 bugfix release

Thu Jul 16, 2015 2:53 pm

Notice the Brown "Archive" in the image on the top.
No answer to your question? How to write posts
 
vortex
Forum Veteran
Forum Veteran
Posts: 706
Joined: Sat Feb 16, 2013 6:10 pm

Re: v6.30.1 bugfix release

Thu Jul 16, 2015 3:11 pm

Actually, I did not know what Archive meant in the diagram.
 
dadoremix
Frequent Visitor
Frequent Visitor
Posts: 98
Joined: Sat May 14, 2011 11:31 am

v6.30.1 bugfix release

Thu Jul 16, 2015 3:16 pm

+1 for dyndns script, 6.29.1!working and 6.30 broken
more likely that your script is broken. scripting language improves over time, the scripts need to be updated. MikroTik did not make th DynDNS script, you have to ask the person who wrote it, or maybe post this question in the "Scripting" section, someone could update it.
Yes yes script is broken
The same script isnworking from 3.x version till 6.29.1
Now in 6.30 broken, maybe you can fix it? Im not at that level expert for scripting, or mikrotik company can make addon for dyndns update? Every modem, router have it.
So i stuck on 6.29.1 version right now
 
vortex
Forum Veteran
Forum Veteran
Posts: 706
Joined: Sat Feb 16, 2013 6:10 pm

Re: v6.30.1 bugfix release

Thu Jul 16, 2015 3:24 pm

There's another obvious clarification about the diagram:

Given the timeline I wrote above, you would get just that if you are on Current, but if you are on Bugfix and 6.31*, your updates stop at 6.31.3

I haven't see the RC but then there should be a button for "Upgrade to next minor version" to jump to 6.32 then.

And when 7.0 releases and you are at the end of 6.x, "upgrade to next minor" should not take you to 7.x, there should be an explicit "Upgrade to next major version" button.

What about if you are on Current, but don't want to upgrade to the next major by mistake? I think Current should stick to the current major version, and you should use the latter button to jump.

These buttons need a good confirmation screen.
 
jarda
Forum Guru
Forum Guru
Posts: 7560
Joined: Mon Oct 22, 2012 4:46 pm

Re: v6.30.1 bugfix release

Thu Jul 16, 2015 3:25 pm

+1 for dyndns script, 6.29.1!working and 6.30 broken
more likely that your script is broken. scripting language improves over time, the scripts need to be updated. MikroTik did not make th DynDNS script, you have to ask the person who wrote it, or maybe post this question in the "Scripting" section, someone could update it.
Yes yes script is broken
The same script isnworking from 3.x version till 6.29.1
Now in 6.30 broken, maybe you can fix it? Im not at that level expert for scripting, or mikrotik company can make addon for dyndns update? Every modem, router have it.
So i stuck on 6.29.1 version right now
Maybe you can check what is not working in your script and correct it. I am using dnsexit and not dyndns, but my script works fine in 6.30...

Who is online

Users browsing this forum: jerryd, Mosfet and 10 guests