Is there any chance that the VyOS team will change their mind on ISO builds?

Development
25

And looking at VyOS there is no Debian unstable or Debian testing involved in the VyOS releases (as I know of).

1.3 series uses Debian 10.x Buster and 1.4 and currently 1.5 both uses Debian 12.x Bookworm.

The current stable release of Debian is named 12.x Bookworm.

The oldstable is 11.x Bullseye and the oldoldstable is 10.x Buster according to:

So this gives that if you use 1.5-rolling you get:

Which gives that VyOS 1.5-rolling contains (TLDR edition):

  • Latest stable of Debian.
  • Latest longterm stable Linux Kernel (custom compile).
  • Latest stable FRR (custom compile).
  • Custom scripts which is the VyOS magic sauce compared to if you just install Debian on your own and gets latest longterm stable Linux Kernel + latest stable FRR (again disclaimer that stable/10.0 of FRR was released in april and not yet implemented in 1.5-rolling).

And I agree with you, people seems to read in incorrectly things with LTS vs rolling which isnt true when it comes to VyOS.

They seem to think that 1.5-rolling would be Debian unstable (that explodes every other dist-upgrade), Linux-next (with all its drama of which updates to include or not) and whatever is going on at FRR with whatever unstable branch they might offer (if any).

26

Most people I know of would test a new release from the vendor before deploying it no matter what the vendor label the release as (alpha, beta, gamma, hotfix, update, critical update, stable, unstable, testing, lts, next etc).

Which gives if you run into issues (and oh boy I have been running into issues no matter who the vendor is) you either contact the vendor/check the forums or you try the previous edition. Beauty of open source is that the changes are more transparent so its easier to find out which version it is that borked whatever feature you think is broken and you can get the release from the day before the break occured instead of having to moonwalk back to a release thats +6 months old.

This also gives that you wont update all your routers every night (even if you select a 1.5-rolling) but you will test and verify it in your labs/verification environments and then slowly roll it out to the rest of your organisation over a selected timeframe (days or weeks).

Because again, just look at the changelog at 1.3 vs 1.5. Or if you dont want to look at 1.5 then look at changelog between 1.3.1 and 1.3.2 and so on. All the changes between 1.3.0 and 1.3.8 are issues identified and fixed which existed in 1.3.0 (and some arrived along the road).

Which again gives that LTS to me when it comes to VyOS isnt something magical but rather a way to have a point release when you have paid support so both of you are looking at the same binaries when troubleshooting something.

28

@dd010101 I understand why people want access to the 1.4 LTS release. I’m not arguing that point.

Sure. But find an image that isn’t broken for your configuration and be happy. You’re aware that there’s bugs and issues in 1.4 as well, right? It’s not a panacea.
1.4-epa3 release notes:

image
image1782×2142 310 KB

Your argument still appears to be a version of “There might be something wrong with one of the 1.5 releases, therefore I require access to the 1.4 releases”

If you want the project to move forward, help find and report the issues that are in 1.5.

29

epa1 release (that is differences between this release candidate and the 1.3 branch):

epa2 release (that is differences between epa2 and epa1):

epa3 release (that is differences between epa3 and epa2):

And the changelogs are just for the VyOS parts, not all the changes made by each of the approx 775 packages from the Debian distribution…

And then somehow some people still think that 1.4.0 LTS is somehow magical as in no issues what so ever because its named “1.4.0 LTS” instead of “1.5.0 Rolling”?

32

You mean posts made by the 2-3 people who requested that their posts shall be removed and their accounts on the forum deleted?

34

No, he’s referring to the posts that have since been marked “Unlisted” and edited within the last 24 hours to remove links to the external resources that provide the guide/solution for a user to build Equuleus or Sagitta images.

1 Like
35

As I told you before, get your forum and promote your stuff there; there is no need to do it here.

36

Answering the original question about this topic - there was no backlash from the community, as the actual community is perfectly fine; nothing changed for them, unhappy only people who did not participate in the VyOS project but just wanted software without any effort.

The source code is on GitHub.
Yes, you will need to have knowledge and spend time to build your image.

We will share our work only with people who support the project,

Which external developers are you talking about? One month later, everything is ok, key people continue and several more developers joined.

If you read forum tos, you should know that you can’t call people sneaky or defame the project (which you do). That you did not understand the rules does not make you exempt from these rules