IMPORTANT: Multistream merge date, and 0.x branch #2855
Comments
|
Hi, Can you please publish 0.x releases documentation somewhere? |
|
That's what https://janus-legacy.conf.meetecho.com is for 🙂 |
Thx, TIL :) |
|
As a side note, the main website also has a link to the 0.x docs and demos in the top bar. |
Argh, correcting myself, looks like that link is wrong and still points to |
Fixed in b12228f |
|
As you may have noticed, we have merged the multistream branch and, as promised, the 0.x branch is live as well. For some more info, you cah check this blog post I wrote: https://www.meetecho.com/blog/multistream/ |
|
@lminiero, please I couldn't find a way to build janus on Fedora, I was trying to use docker for that but all are outdated only implementing janus 0.x. |
|
I use fedora ever day and it compiles just fine for me. Please ask questions like this on the meetecho-janus group, not here. |
I forked the canyan docker instance and updated the Janus version to 1.x: Repost your question in the google group and I'll reply with the docker compose file |
|
I tinnk we can close this now: the difference between |
Hi all,
as you probably know, we've been working on the multistream branch for quite a long time and in a couple of different iterations. We now have an official date for when that branch will be merged in master, which is February 11th 2022, that incidentally also is the 8th birthday of Janus 🤭
Of course, we know that many people use the current version of Janus in production today, and we're not planning to abandon that code, quite the opposite. In fact, while the multistream branch will become the
1.0version of Janus, the existing0.xcode will live on in the following branch instead:https://github.com/meetecho/janus-gateway/tree/0.x
As such, if you don't want to upgrade to the new version of Janus yet, you can get your code from that branch instead, and nothing should change for you. The branch is already active, and acting as a lazy mirror of the current master, so if you want to be sure you're not caught unprepared by the change we'll make in February and are currently pulling your changes directly from the
masterbranch, you can change your scripts to pull the0.xbranch instead and all should be fine. If you usually use releases instead, then all should be ok, as the plan is to still occasionally push releases for the0.xbranch well.That said, while we do indeed want to keep the
0.xbranch updated, especially when we become aware of bugs or security issues to fix, please notice that we'll start focusing much more on the new version as soon as it is merged, especially to start working on enhancements we've kept on hold so far, and we'll likely greatly limit the addition of new features to the old version instead. As such, while the current version of Janus will indeed be kept alive for quite some time, you'll definitely want to have a look at the new version as well to plan an upgrade sooner or later, especially if you'll want to take advantage of new features.I guess that three weeks are enough of a heads up to prepare for the change (whether you plan to keep the old version of switch to the new one), but in case you have feedback to share or suggestions to make on how to keep this as painless as possible for everyone, please let us know.
The text was updated successfully, but these errors were encountered: