I'm sure the third category, devs who want to use a LTS release, who will benefit from stuff that has arrived in 2018 already in pretty good shape, but dont need to keep up with the latest evolution of stuff that is still rather early, eg preview render pipeline packages, still exists. But I would agree that it could be smaller this year because of the timing of when major features have landed. I think the new prefab thing draws attention to this possibility, we don't often get such dramatic change to Unity and in many other areas Unity has been able to introduce new stuff without getting rid of the old way at the same time. Perhaps this is one of the reasons we are being asked for our thoughts on 2018.3 in this way now, I don't know, just as I don't know what the reasons were for the beta being delayed from its public release for longer than usual some months ago. Certainly I feel as though maybe 2018.3 needs to come with some kind of giant glowing caveat warning, but I haven't thought about what that could be exactly. I don't think I could attempt to properly judge how good and useful the 2018.4 LTS release will be until we see quite how well 2018.3 goes for everyone once it is out of beta. If there are issues that cannot quickly be squashed, then it is possible that the fixed calendar nature of Unitys LTS release plans will not serve anyone too well this year. In which case I would encourage Unity to reconsider how that stuff works, and in future either be prepared to do LTS releases at whatever point makes sense rather than fixing to a calendar, or to plan the timing of your new features for the year so that any biggies tend to arrive in the .1 or .2 versions so they have a chance to mature further throughout the year before LTS version comes around again. So yes I probably do believe that given the LTS timing, it is rather unfortunate that something which involves as big a change as the new prefabs system should arrive in a .3 version. Same may go for terrain changes, but I haven't tried it myself yet so I don't know how ripe it is. But overall 2018 has been a busy year with big changes, so I suppose I should not be surprised if the 2018 LTS feels less ripe and ready than the 2017 one, because 2017 felt like more of a year when stuff matured and solidified throughout the year, without too many major shocks to the system. I'm far more forgiving of unfortunate render pipeline timing issues as they relate to LTS, because I just see this as an inevitable consequence of how long that stuff is taking, and the relative immaturity of these systems. There was a lot of progress in 2018 with a lot more still to do, and most grumbling noises I could make are historical, in that a lot of what happened in 2018 was what I originally hoped would happen in 2017. I would certainly hope that during 2019 both LWRP and HDRP will get to a state where they have reached notable production ready milestones in good time for 2019 LTS to take advantage. Once we are passed that point I would certainly hope that future addition of features and general maturity of the system takes into account future LTS timetable, try to get things in sync a little better when it comes to major features, platform support, breaking/large changes and LTS releases. But that's not a luxury I think they've had the ability to achieve so far, due to immature state of pipelines and a fair amount of refactoring.