From my reading of the SuSe website, I sort of got to the understanding of the process stages listed by @Knurpht.
However, much like the answer from @Knurpht, nobody ever seems to give a timeframe, even an average one ? It would be nice to know if we’re likely talking weeks, months or years here before I see 3.4.2 in LEAP because that impacts my decision on whether to use SuSe at all for this application, because the "old’ version of SA potentially has a few issues on it.
Well, there is some sort of time frame: Leap package versions will stick to the version in the distro, apart from bug- and security fixes. I.e. no newer KDE, Apache etc. But, if you are really in need of a certain version, you can add it’s repo ( do not use home:/ or devel:/ repos ) and use the package from that repo. Another option you have is to run Tumbleweed, which currently serves 3.4.2 builds. Be careful, do not add Tw repos to your Leap install.
FWIW: I do use TW for production use, albeit only for my own work/production use, and have been doing so without issues for a couple of years now. At the time I needed some newer versions of some packages, which were all in TW and would have caused addition of half a dozen repos on Leap.
In your case I might add the repo, install the newer version, then disable the added repo. Moving to TW for just one piece of software maybe is a bit too much.
Given the source of the Spamassassin – the Apache Software Foundation – IMHO that build result can be interpreted as being “OK - reliable” …
But, as Knurpht has indicated, this isn’t true for all the builds in the “devel:” repository and therefore the “switch it on, and then switch it off” advice should avoid any nasty surprises with other packages …
I should have elaborated a bit more, given my previous replies. But that would have been what dcurtisfra already wrote. If it works as expected, indeed disable the repo.
Given the LTS strategy re. Leap, one sometimes has no other options.