Legolash2o Posted January 28, 2013 Share Posted January 28, 2013 Before I talk about long term plans, I will talk about the next release. v22.214.171.124 already has a few bug fixes and enhancements.Short Term - Next release:*126.96.36.199^FIX: "KB2670838" will always be integrated before IE10. Because it is required for IE10 to be integrated.*188.8.131.52^FIX: Typo on new 'Windows ISO' screen. Nothing special.*184.108.40.206^New method of detecting update integration. Usually updates go green fine but some stay red. This new method gets the package name which you can see when you put your mouse over item. Anyways, all updates should now go green unless it's for the wrong version of Windows. For example, Windows 2012 updates won't integrate into Windows 8 and will show red.*220.127.116.11^KB2764913 and KB2764916 (IE10 files) can now be integrated on x64. Any processor architecture neutral updates can now be integrated. *18.104.22.168^'Windows ISO' > 'Exclusive ISOs' now displays download speed and time remaining.I won't release v22.214.171.124 yet as I will be going through the automated error logs to fix what I can.Long Term:I'm still very behind with the code refactoring so I will have to dedicate at least an hour a day to get the job done. I haven't really done much recently and it really needs to get done before I can add new features. I will of course keep you guys updated on its progressIn case you've forgotten, code refactoring is where you replace older and possibly more complex code with newly learnt and simpler code. This helps create an efficient, simple and more streamlined program but also helps me squash bugs.Also Win Toolkit production may end (except bugs) when Windows 9 comes out but I will start a new tool dedicated for Windows 9 Anyways, back on point. When the code refactoring is completed I will finally be cycling throw ALL the request topics for the v1.5.0 release. I really need to get the code refactoring done first.Releases:Sometimes I can get carried away with release and release multiple updates a day, this tends to annoy people and therefore I am thinking about trying to release a beta build every night (assuming if anything has changed) and a public build every Sunday night.This will also allow me to gather enough log data to release bugs and give you guys a chance to report more errors. The only time I will release an update before then is if there is a massive bug which needs to be addressed.Automation:I'm trying to make more processes in Win Toolkit automated for me. For example, the new update integration check will make life a lot more simpler for every body as you should no longer receive red updates.Error logging is already fully automated which is brilliant as most users don't report bugs at all. There are, however, more things which could be automated for me which will give me more time for programming.I will try and make donations more automated so users don't have to wait for me to give them a key. McRip 1 Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.