Traumflug Posted February 3, 2019 Share Posted February 3, 2019 Quote Are you going to use 1.7 base code for next TB major releases? Not really. PS 1.7 did a few things right and if thirty bees needs something similar, it'll implement this in a similar fashion. No need to alienate module developers more than necessary. But that's about it. thirty bees simply has distinct goals. Like improving reliability and ease of use. Look at the upcoming GitUpdater, Lesley has something in the works, too. 2 2 Link to comment Share on other sites More sharing options...
Briljander Posted February 4, 2019 Share Posted February 4, 2019 I think you have understood a lot of TBs earlier problem. The last updates with easier updaters and migrationtools is in the right direction. More of that and more error- and easier to understand reporting! Link to comment Share on other sites More sharing options...
Beeta Posted April 7, 2019 Share Posted April 7, 2019 On 2/3/2019 at 10:33 AM, Traumflug said: No need to alienate module developers more than necessary. I understand it and I agree. but I think, also, that’s a matter of time (2020?) that ps developers start to develop for ps 1.7 only and start to “forgot” 1.6 maintaining and without release 1.6 addons update. what do you think about that? Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now