New Releases

[T.S. Excreta]

We waited a couple of weeks for the release of Client B12 and Server B16 and were told with that that we would get more frequent releases.

Are we back to the 2+ week release schedule? Just curious because the permissions system is still a bit flaky, banning isn't as good as it should be (people can totally ignore it, and banning entire subnets is ridiculous to get rid of ONE person) and the client has some quirks as well. Things like plugins that stop working for no reason at all.

Any ideas, team? I am just curious here.

[Peter]

Fast releases do NOTHING to fix problems (only maybe to get the fix faster to the users, once it is found). Rather than saying releases are not frequent enough make posts for each issue you find with a way to reproduce etc. so we can fix it. Much of what you say as issues is very unspecific and vague.

[ZeroTKA]

We waited a couple of weeks for the release of Client B12 and Server B16 and were told with that that we would get more frequent releases.

Are we back to the 2+ week release schedule? Just curious because the permissions system is still a bit flaky, banning isn't as good as it should be (people can totally ignore it, and banning entire subnets is ridiculous to get rid of ONE person) and the client has some quirks as well. Things like plugins that stop working for no reason at all.

Any ideas, team? I am just curious here.

Security levels will be your friend.

[T.S. Excreta]

Security levels will be your friend.

This has exactly what to do with my questions?

Fast releases do NOTHING to fix problems (only maybe to get the fix faster to the users, once it is found). Rather than saying releases are not frequent enough make posts for each issue you find with a way to reproduce etc. so we can fix it. Much of what you say as issues is very unspecific and vague.

I never said releases weren't frequent enough... I asked about the schedule.

Learn to understand what you've read before you try to flame and/or attack someone for a post.

As far as vague.. the issues are all over the forums. Are you not reading them? Are you ignoring them? Like with the issue on banning... I made a post about that, explained what was happening and got a vague answer there from a "team" member.

Everything else is self explanatory. How much more detail do you need outside of "plugins stop working suddenly" here?

[Slater]

Sorry, but Security Levels is not a solution. It's a way how to complicate things on a public server with 200+ users.

[theeggman]

Maybe I too have missed the point of this post, but I am here wondering the same thing. We were informed of a more frequent release schedule... Here we are again about a week has gone by and there has been no new releases..

Not looking to flame, just wondering what is the timeframe is for the next release, and what will it contain? Any kind of development update would be wonderful

[ZeroTKA]

This has exactly what to do with my questions?

Sorry i didn't specify. I was referring to your complaint on how people can totally ignore bans and banning by entire subnets.

[R. Ludwig]

=== Client Release 3.0.0-beta13 - xx Jan 2010
+ Added customizable toolbar buttons
* Updated German translation
- Fixed bug where users removed from contacts could no longer be unmuted
* Added Edit virtualserver menuitem to Self menu
- Closing edit virtualserver dialog with Escape will also trigger the discard/apply dialog
- Fixed possible marking the edit virtual server dialog modified after opening
- Fixed typo in hotkey setup, so "Status change - Deactivate" works again. 
* Individually handle permissions to view server/channel group tabs and display
  notification in the permission and client widget if they cannot be viewed.
* Initialize only those permission tabs for which permission was granted to
  avoid invalid permission error spam.
- Removed -enableallactions commandline option.
- Fixed restoring server and channel groups on reconnect when keeping the
  permissions window open.
- Fixed strange behaviour of toggle microphone hotkey in combination with auto-
  activate microphone when switching server tabs.
* Reload chatlog when connecting to a new server in the same tab
* Tweaked autoscrolling after reloading logs
- Fixed creating hotkeys (no keys were accepted / gray box stayed always open)
* Play talk-power-requested sound only if user has permission to grant it
* Changed serverquery clear highlight button shortcut to Backspace, so Escape
  key is available for closing the window again.
+ Escape always closes hotkey dialog, even if hotkey input doesn't work.
* Allow multiple whitespaces in channel description.
+ Added use of server-, channel- and client info templates. Look into
  the folder styles\default for premade templates, which can be modified
  for different styles and languages.
+ Added server address:port in server info.
- Fixed pasting a text into hotkey rename field.

=== Server Release 3.0.0-beta17-pre2 xx Jan 2010
- fixed possible crash while deleting subchannels
- clientlist option -VOICE added CLIENT_IS_PRIORITY_SPEAKER property
- fixed issue where query could start an stopped virtualserver while
  instance terminating
- fixed channel_flag_password was not set automatically while creating
  a new channel over query  
- fixed strange behavior while changing b_group_is_permanent permission value
- fixed licensing issue with max slots below 32
- query_ip_whitelist.txt removed out of package and is created if not available
- fixed PERMISSION_b_client_channel_textmessage_send not working properly
- fixed ghosting channel bug with certain default sub channel setups
- fixed critical after editing an perm/semi channel to an temp
! added command line parameter dblogkeepdays (default 90)
  defines how many days to keep database log entries
  (triggered on every start and while running on every new month)
! added command line parameter dbclientkeepdays (default 30)
  removes all clients which had not connected the last x days and dont
  got an servergroup assigned
  (triggered on every start and while running on every new month)
! added custominfo command (check docu for details)  
! added permissions PERMISSION_b_client_custom_info_view
! added permidgetbyname command (check docu for details)

[nightlore]

I really want too know why so many people are impatient for next releases.
Take a chill pill and wait.

If you want good applications then be prepaired too let the guys remove all the bugs and have it running superb.


If you have any idea on how too program any VOIP then why not help instead of asking silly questions like when is the next release.


We all want it but some are more patient than others.

It's a great product guys I will always look forward too seeing it in the final stage myself when that day comes.


Good Luck to you all on TS3

[T.S. Excreta]

I really want too know why so many people are impatient for next releases.
Take a chill pill and wait.

If you want good applications then be prepaired too let the guys remove all the bugs and have it running superb.


If you have any idea on how too program any VOIP then why not help instead of asking silly questions like when is the next release.


We all want it but some are more patient than others.

It's a great product guys I will always look forward too seeing it in the final stage myself when that day comes.


Good Luck to you all on TS3

Think you could be patient enough to understand what you've read?

I am not impatient for next releases. I was asking both about the release schedule and the promise that newer releases with newer features and bug fixes would come more frequently.

I don't mind waiting. But don't make one statement and then live by another.

Now, it's not that I want the next release really bad... it's that I want to know when to expect the next release because there are still issues.

Issues like not being able to edit the minimum client version from the client, even through ServerQuery. Seriously... I understand they think it would break a lot of servers and generate many complaints on the board, but I am sure MOST of the userbase here is competent enough to make sure they have the latest client before locking themselves out of the server with that setting.

Anyway, it's not an attempt to rush the next release. It's an attempt to understand how the devs plan to work the release SCHEDULE.

[-{HGH}-GEN.Skylab]

I wouldn't even ask. Knowing isn't making it come any sooner, let the devs do what it is that they do, not create a schedule for a single client who feels he would like to 'know' what their schedule is. They most likely don't have a schedule. They're busy reading bugs, suggestions, etc. Thread is pointless.

[T.S. Excreta]

I wouldn't even ask. Knowing isn't making it come any sooner, let the devs do what it is that they do, not create a schedule for a single client who feels he would like to 'know' what their schedule is. They most likely don't have a schedule. They're busy reading bugs, suggestions, etc. Thread is pointless.

Again, the post isn't about how soon. It's more about how the schedule is going to work over the course of the beta and which features will be and need to be fixed.

If they don't have a schedule, that isn't good development. However, I am sure they do have a schedule.

And your useless, yet completely pointless reply, is useless.

Either be constructive, or don't reply at all.

[maggy]

We alpha testers have not gone away. When the devs have a new build we work on it and report back. If there is not a new beta release going on then one of two things is going on behind the scenes: either the devs are busy programming or we are busy breaking their new stuff. The devs of course are still working on their to-do list of things they still want to add to the program and some of that comes from the feedback on the forum.

So even though they may have had an idea of what the "schedule" was going to be like back at beta1, as we have had hundreds of thousands of users playing with the program, ideas have come back that that may not have been considered originally, but given some careful consideration, they have decided that it is better to do those things for the first stable release than to push it off to subsequent patches. Ultimately they are the drivers here and it's their program so they call the shots on this.

But if you really must know, as you've seen in past beta releases we've gone sometimes with a testing turn-around of less than a day or more than a week. It depends entirely on the complexity of the things that need to be tested and the many different scenarios they are tested under. In addition, more recently the client releases have been paired up with required server releases so there are two carts that the horse is pulling that have to be at the same place at the same time to do coherent testing. A blocking bug in the server would delay a client test and vice versa.

Nobody has gone on vacation yet.

[-{HGH}-GEN.Skylab]

Again, the post isn't about how soon. It's more about how the schedule is going to work over the course of the beta and which features will be and need to be fixed.

If they don't have a schedule, that isn't good development. However, I am sure they do have a schedule.

And your useless, yet completely pointless reply, is useless.

Either be constructive, or don't reply at all.

I made a statement and also to your...whatever you want to call it. Take care bro

[T.S. Excreta]

We alpha testers have not gone away. When the devs have a new build we work on it and report back. If there is not a new beta release going on then one of two things is going on behind the scenes: either the devs are busy programming or we are busy breaking their new stuff. The devs of course are still working on their to-do list of things they still want to add to the program and some of that comes from the feedback on the forum.

So even though they may have had an idea of what the "schedule" was going to be like back at beta1, as we have had hundreds of thousands of users playing with the program, ideas have come back that that may not have been considered originally, but given some careful consideration, they have decided that it is better to do those things for the first stable release than to push it off to subsequent patches. Ultimately they are the drivers here and it's their program so they call the shots on this.

But if you really must know, as you've seen in past beta releases we've gone sometimes with a testing turn-around of less than a day or more than a week. It depends entirely on the complexity of the things that need to be tested and the many different scenarios they are tested under. In addition, more recently the client releases have been paired up with required server releases so there are two carts that the horse is pulling that have to be at the same place at the same time to do coherent testing. A blocking bug in the server would delay a client test and vice versa.

Nobody has gone on vacation yet.

Finally, a worthy reply. Thank you, Maggy.

I understand that testing needs to be done in-house before new releases are pushed to the masses. I know that they want to add new features either the community asks for, or that they simply didn't think of originally. That's a great thing. So far, I am extremely impressed with TS3. The client is nice with the new features it has PLUS the fact that it has a familiar feel to it. All around, this project has been great under testing. I give the team a lot of credit for what they've made here as it is better than any other VOIP application out there currently.

I know they are working on it. I am sure no one is on vacation right now, hehe. I am just curious because most developers have a roadmap they follow as far as feature additions, bug fixes and releases go. That was basically my question. Sadly, everyone here, except you possibly, has thought I was trying to rush releases. I am not. I am simply wanting to know what to expect.

Thanks for a well thought-out reply, maggy. Much appreciated.