dms2013 Posted February 6, 2014 Report Share Posted February 6, 2014 Hello Devs.It's been 2+ months since anything was written in the changelog.What is new/fixed in the 1.2.87 and 89 that some people got. What are upcoming features?The wishlist is a mile long, so it's difficult to speculate what will actually come and not. I'm sure lots of people are wondering Thanks for a great product! Quote Link to comment Share on other sites More sharing options...
GreatMarko Posted February 6, 2014 Report Share Posted February 6, 2014 It's been 2+ months since anything was written in the changelog.The team are actively working on Sync 1.3. No recent beta builds doesn't equal no development!Around 60% of their development time goes purely to optimizing and improving the stability of Sync. Some issues require significant work and won't be noticed by the majority of users. However the team believe that the core value of Sync is fast and reliable synchronization and this remains their top priority. What is new/fixed in the 1.2.87 and 89 that some people got.There are no new features in these builds, just bug fixes (such as this rather strange one related to the use of the number 9!). New features will come with Sync 1.3.x What are upcoming features?This hasn't been publicly revealed yet, so far as to say Sync 1.3 will add some "major features" The wishlist is a mile long, so it's difficult to speculate what will actually come and not.Don't worry about the length of the Wishlist - the developers DO take note of all requests made in that thread, and they are keeping track of how popular and frequently requested each feature request posted there is. Quote Link to comment Share on other sites More sharing options...
jah Posted February 7, 2014 Report Share Posted February 7, 2014 Did the new build address this bug by chance? link Quote Link to comment Share on other sites More sharing options...
GreatMarko Posted February 7, 2014 Report Share Posted February 7, 2014 Did the new build address this bug by chance? link I think this was actually fixed for 1.2.82? That particular issue seemed to crop up in 1.2.73, indeed, I encountered it a couple of times in my testing of 1.2.73 too - but I've not encountered it 1.2.82 (or later), or heard of reports of others who have, so I would summize that it was indeed fixed for 1.2.82 back in November Quote Link to comment Share on other sites More sharing options...
jah Posted February 8, 2014 Report Share Posted February 8, 2014 I am running 1.2.89 and still very definitely getting this bug. It's debilitating. FYI I have a log showing some of the errors. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.