Sublime Forum

How do I download a dev build?

#1

Sorry, I don’t understand it. On the downloads page, the link to the dev builds takes me to a similar download site, telling me I need to have ST registered (I have) in a blue message, and below are builds that are (one build) older.

So, the dev builds have been 3210 and older? Or do I need to enter credentials somewhere?

I believe I have seen higher build numbers than 3211 (can’t remember where), does anyone want to help me to find one of them for Microsoft Windows?

I’m trying to get a version that has a bug fixed in the replace dialog.

0 Likes
#2

Build 3210 is functionally equivalent to Build 3211, It came out first so the devs could get the bugs out of it, then stable build 3211 was released.

The real dev build today is ST4, but to obtain that as a dev build, you must be on the Discord channel, for reasons that remain unclear to me.

1 Like
#3

Being discord only probably means the dev stage is still more “alpha” than “beta”. I initially checked it out a few months ago and found too many issues. I checked again recently and have been using ST4 exclusively for the past couple weeks, pretty stable now.

1 Like
#4

The reason is the amount of changes and a high chance of possible issues and numerous known issues or incomplete new functions. sublimeqh wants to iron out the new stuff based on power user’s feedback first before publishing it to a wider range of users who might expect perfect working betas only or might be unsattisfied with still in progress developments which might cause some details to change.

1 Like
#5

A perfect working Beta is a contradiction of terms. That is what a dev build is for, to iron out the bugs. I could accept the current situation in the beginning, but as it is mostly stable now, I can’t see why it isn’t released to a wider body of testers.
There must be some other reason.

0 Likes
#6

The “perfect working” is a more or less ironic statement. And yes, the current ST4 builds are pretty stable. Using it since day one trying my best to provide hopefully helpful feedback.

There is no other reason, that’s for sure.

Some of the new functions are just not in a final-enough state to publish them. In the current state it is easier to introduce some breaking changes here and there which might still be needed to finalize functions. Once everyone knows about them, it is harder to do so as one of sublimeqh’s goals is to provide complete functionality and keep compatibility for it “forever”.

Documentation needs to be written for new stuff as well, first.

etc.

They just want to complete/fix the known issues first. Otherwise the heavy amount of feedback from a wide user base might be too overwhelming.

1 Like
#7

In the current state it is easier to introduce some breaking changes here and there which might still be needed to finalize functions.

This is a really important point. While ST4 may be more or less stable, we don’t want all the plugin developers updating their plugins until we’ve stopped making breaking changes. Public betas also mean a public announcement. That hasn’t been made yet.

1 Like
#8

Public betas also mean a public announcement. That hasn’t been made yet.

That’s for sure.:slightly_smiling_face:.
That’s all from me.

0 Likes
#9

There’s also the issue of a missing official upgrade plan to python 3.8 for existing packages and st dependencies. That absolutely needs to be sorted out before it turns into a wild-west situation.

3 Likes