The answer is: when contributors help us close issues marked for 1.4 milestone.
-
Vote in the Final TFS Icon Competition!
When will TFS 1.4 be released?
- Thread starter Don Daniello
- Start date
sounds fun
- Joined
- Jul 27, 2013
- Messages
- 508
- Solutions
- 3
- Reaction score
- 393
You can go back few commits and recompile the distro till you find the commit that broke that feature that would help a lot.
- Joined
- Dec 23, 2014
- Messages
- 1,878
- Solutions
- 51
- Reaction score
- 594
Trying to figure out what it is. Pretty much after sitting for a while the tibia client says "attempting to reconnect", kicks me, then I can't log back into the server (sometimes the server shuts itself off). It is a completely clean server.
This has never happened to me.
Ok yes, XD But it's always because of something I do wrong, then I fix it and it looks good again
Leaving the topic of jokes, the block you mention has not really happened to me
F
Ok yes, XD But it's always because of something I do wrong, then I fix it and it looks good again
Leaving the topic of jokes, the block you mention has not really happened to me
F
- Joined
- Dec 23, 2014
- Messages
- 1,878
- Solutions
- 51
- Reaction score
- 594
It was something I did.....
- Joined
- Nov 17, 2010
- Messages
- 5,366
- Solutions
- 352
- Reaction score
- 3,475
Yeah.. that was posted months ago. Here.
Simonalina
Member
When they release 1,5? 
zbizu
Legendary OT User
2050? Maybe 2030 if some bored student discovers tibia. 1.4 is still stuck on already solved issues no one bothers to test.When they release 1,5?
Simonalina
Member
hahah yea
zbizu
Legendary OT User
Jokes aside I think the snapshot model of minecraft releases would move the project forward.
It could go this way:
1. News "1.3 (insert new feature here) test 1" (or something like that)
2. The post would contain experimental build with new feature that didn't got merged to the main repo yet.
3. People would test it because muh new tfs and report bugs.
A little spoonfeeding (compiling for them the ready feature that needs to be tested and posting it in news/download) would give you more testers because let's be honest, no one bothers to compile pull requests of other people and you advise against using appveyor builds.
Now, while we're at it: was the bug with random disconnecting fixed? I intend to fork in order to rework area spells, but I need a playable build.
Of course not every pull would be posted, but something big ready to testing is fine imo.
A successful test could lead to test 2 or stable sub-release. A failed test could lead to test 2 with fixed bugs.
Two biggest things that are stopping tfs from going forward are lack of spoonfeeding new users like in the past and no support for newest game versions. With these two satisfied you could have lots of testers, just saying.
It could go this way:
1. News "1.3 (insert new feature here) test 1" (or something like that)
2. The post would contain experimental build with new feature that didn't got merged to the main repo yet.
3. People would test it because muh new tfs and report bugs.
A little spoonfeeding (compiling for them the ready feature that needs to be tested and posting it in news/download) would give you more testers because let's be honest, no one bothers to compile pull requests of other people and you advise against using appveyor builds.
Now, while we're at it: was the bug with random disconnecting fixed? I intend to fork in order to rework area spells, but I need a playable build.
Of course not every pull would be posted, but something big ready to testing is fine imo.
A successful test could lead to test 2 or stable sub-release. A failed test could lead to test 2 with fixed bugs.
Two biggest things that are stopping tfs from going forward are lack of spoonfeeding new users like in the past and no support for newest game versions. With these two satisfied you could have lots of testers, just saying.
Last edited:
1.3 is stable.
templosamurai
New Member
We need that release version man, its a good new.
- Joined
- Dec 26, 2013
- Messages
- 1,288
- Solutions
- 4
- Reaction score
- 416
Seems like the only thing really waiting to be done is the icon. Everything else marked is pretty much ready for merger, we got one milestone that just needs a review, one that says its waiting on changes that have already been done, one that looks like the fix was found, but then the pr was closed for no apparent reason (unless im mistaking and the pr didn't fix the issue), at least from what I read of the conversations on each pr. Then the last one left is the icon...
Similar threads
