![]() ![]() It’s not like we have a right to know what’s going on or anything, every info we get is a bonus. We can only imagine what’s involved and sit and wait till it’s here. It has already been stated a few times the current cycle is about getting the darn thing out the door. I plan for a software development team every day and you just don’t get any more accurate than “we’ll do that after we’ve done this and fixed the bugs we don’t know about yet”.Īlthough they’re not communicated beforehand (and I wouldn’t know why they’d be obliged to do that anyway), the focus and content of each cycle is actually pretty clear. I really appreciate the approach of tackling a design change and then following through on all of the fallout. ![]() These sort of follow-on issues seem to happen pretty regularly, and affect the pace at which development happens.Īlthough HQ isn’t doing the monthly blog posts a cool start up is expected to do these days, if you follow the dev releases and discussions on the forums it actually paints a pretty good picture of what’s going on. As we improved the implementation of the sidebar to be more efficient, bugs (and undocumented aspects) of the filesystem notification APIs provided by the operating systems were exposed and we had to find ways to work around those. Part of this was as I designed and then implemented a new theme, I found various deficiencies that needed to be addressed, and while I was working on those it made sense to fix the majority of theme engine bugs. I can tell you that when the last beta came out, I didn’t know I’d make nearly as many improvements and changes to the theming engine as I did. The reality of it is that priorities shift on a somewhat regular basis and we change our minds about relative priorities. That supposes that we are all-knowing and have exact insight into what combination of items will make for the best release, before any of the work is being done. It would have made a lot of sense if JPS had released a roadmap on what he was targetting as part of release 3 and then ticking off items off that list in the dev/beta release notes. In that case even if the pace of the development is slow, people would not be so frustrated about whats going on with Sublime. And then people can get a real sense of when it will be ready, even more so when in the release dev/beta notes people can start ticking off the items mentioned above. If you had said, we are working on issues/features x, y and z. Third read your own post, “we are working on getting 3.0 final ready to launch.”. It gives a false sense that we are close to a stable release. Second read JPS blog post when the last beta was released. People are being given no clue as to whats the roadmap for the beta or the stable release. ![]() Sometimes there is a huge gap even in the development releases. First of all development of Sublime 3 has started over 2 years ago. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |