We're still working out the kinks. It is a bit odd to sync a server and the find it immediately not be compatible with the latest released client, even if that window of time when they are out of sync is small. Perhaps we could release the new server on a different branch. (Perhaps "prerelease"?) That way, syncing to the default branch would always sync to whatever server is compatible with the latest client. If you don't want to download your server ahead of time, you don't have to mess with any of this.
Switching an installation between branches on steampipe is not a complicated thing, it is exactly the same as doing an update. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of ics Sent: Monday, May 13, 2013 1:38 PM To: Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] Mandatory TF2 update coming Actually in the past many server owners wanted server updates in advance so that they were able to have a server online ready for players and not to update at the same time when update hits to players. That was due to content servers being too busy at those times and we were unable to update servers. Personally i like the new way so far. -ics Mike Vail kirjoitti: > > Eric, > > I'm sorry, but I don't like this at all. Why are you changing the way > releases are done? Please don't release future updates like this. It > worked just fine before and after years of doing client and server > updates at the same time, people know how to deal with them and this > will create more confusion when it just isn't needed. And Lord help us > if the Client update is delayed after the server update is released. > People won't be able to play on a ton of updated servers. Thank you > for your consideration. > > *From:*[email protected] > [mailto:[email protected]] *On Behalf Of > *fiveofeight > *Sent:* Monday, May 13, 2013 1:22 PM > *To:* Half-Life dedicated Win32 server mailing list > *Subject:* Re: [hlds] Mandatory TF2 update coming > > I'm pretty sure it will say "The server is running a newer version of > the software.", since this is a mandatory update. > > On Mon, May 13, 2013 at 4:18 PM, Albert Davis <[email protected] > <mailto:[email protected]>> wrote: > > Will the clients still be able to join the updated server until the > clients been updated? > > On Mon, May 13, 2013 at 4:06 PM, John <[email protected] > <mailto:[email protected]>> wrote: > > Eric, > > We're working a mandatory update for Team Fortress 2. The dedicated > server update is now available for you to download ahead of time... > > > For those of us that have automated systems that look at these > announcements and check for updates, this sort of pre-release can > cause servers to be upgraded too soon and kick a lot of clients who > then cannot reconnect. It may be better to send out pre-releases under > the optional update channel, or with some sort of other special tag. > > -John > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds > > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds > > > > -- > Sent from my Asus G53 > > > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, please > visit: > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
