Difference between revisions of "Publish 30"
(New page: {{tocright}} ==Updates== ===Update 1=== On February 16, 2005, the following was published: "If everything goes according to plan, we will be conducting an ERT publish to all shards in o...) |
m (→Updates) |
||
| Line 4: | Line 4: | ||
===Update 1=== | ===Update 1=== | ||
| + | On February 11, 2005, the following was published: | ||
| + | * Update that will fix the tithing\vendor buy and runebook rename issues introduced with Publish 30 | ||
| + | |||
| + | ===Update 2=== | ||
On February 16, 2005, the following was published: | On February 16, 2005, the following was published: | ||
Revision as of 03:48, 22 July 2007
Contents
Updates
Update 1
On February 11, 2005, the following was published:
- Update that will fix the tithing\vendor buy and runebook rename issues introduced with Publish 30
Update 2
On February 16, 2005, the following was published:
"If everything goes according to plan, we will be conducting an ERT publish to all shards in order to address an exploit. The tentative schedule is as follows:
- 16 February 10:00AM PST (6:00PM GMT) - Chesapeake, Atlantic, Catskills, Siege Perilous, Legends, Great Lakes, Lake Superior
- 16 February 11:00AM PST (7:00PM GMT) - Pacific, Lake Austin, Baja, Napa Valley, Sonoma, Origin
- 16 February 2:00PM PST (10:00PM GMT) - Oceania
- 16 February 3:00PM PST (11:00PM GMT) - Yamato, Izumo, Wakoku, Hokuto, Asuka, Mizuho, Mugen, Sakura
- 16 February 4:00PM PST (17 February 12:00AM GMT) - Arirang, Balhae, Formosa
- 16 February 9:00PM PST (17 February 5:00AM GMT) – Europa, Drachenfels
We are expecting each publish window downtime to last approximately one hour.
We will keep you updated if any of this information changes."