Since Beta 1.4 is expected to come any day now (possibly today), I thought it would be smart to post a few reminders for everyone about what they need to do and what they should expect over the next few days:
1. Get the latest Minecraft launcher if you have not yet done so.
This is important to do especially for the recent newcomers to Eagleworld. While the new installer has been out for a while, it is possible some of you might not have it yet. If you are using the launcher with news updates right in line, there's nothing you need to do. If you are using the older launcher (with just the login prompt), please make sure to get the new version on www.minecraft.net. Not doing so will leave you in a lurch come Beta 1.4, because...
2. Eagleworld.net will not automatically update to Beta 1.4.
I know this may disappoint a bunch of you, but this is the way it's going to need to be. After the last two beta updates, everyone gave me way too much stress and hassle over things I have little to no control over. I'm not going to go through that again. Instead, the server will stay running on Beta 1.3 until it is good and ready. This means...
3. Do not upgrade to Beta 1.4 if you wish to play on Eagleworld.
Simple as that. If this disappoints you, I am not going to fret over it. Like I said before, my previous attempts at accommodating everyone were met with harsh criticism and very impatient nagging. Remember that this is beta software, and every plugin we use/depend-on breaks every time Minecraft is updated. If you simply cannot wait for Beta 1.4, either back-up your install or forget playing on Eagleworld until 1.4 is rolled out on it. I simply can't please everyone, and I'm not attempting to do so anymore.
4. I do not want constant nagging about the updates.
Every time the server's been updated or something broke, people just don't leave me alone about it. If something isn't working or updated on the server, it's either out of my control, or I simply haven't had enough time to do it yet. I do not offer time-frames or ETA's in any way, because I am not committing myself to any form of deadline. I can promise you that asking me a million times about it will NOT make me go any faster. In fact, the opposite might happen.
To make a long story short, if you want to nag me about the update or criticize how long it takes, don't expect an answer you will like. Let me work at my own pace and I promise you it will get done as fast as my spare time and mental health will allow.
5. Check the blog regularly to stay informed.
In exchange for your not-nagging me about Beta 1.4, I'll make sure you're not kept in the dark about what's going on. As long as I have any information to pass along to the players, I will make sure I give an update about it. While I can't give ETA's on how long it'll take, I can at least make sure you know what has been done and what there is left to do.
6. Here's the basic upgrade plan I'm going to follow.
If you're really interested in what I actually have to do to get this going, take a look at my basic upgrade plan below. Otherwise, just skip it. Note that these steps are linear and require the previous steps to be done before I can work on them:
Spoiler Inside: Minecraft Beta 1.4 Upgrade Plan
Prepare the testing environment for Beta 1.4 once it is released
Clean environment and duplicate the production environment
Tweak settings so environment will not touch production data
Run test server under Beta 1.3 to ensure no issues pre-upgrade
Install Minecraft Beta 1.4 and perform testing as a vanilla server
Download all necessary files/configs for Beta 1.4 SMP
Perform and validate all new configs necessary for latest version
Test vanilla server for bugs/configuration issues and fix as needed
Move on to next steps once bugs are eliminated or minimized
Document any persistent bugs/issues from Minecraft SMP
Install Craftbukkit (Bukkit API) once stable version is released
Check Bukkit.org for a recommended build compatible with Beta 1.4
Download and install craftbukkit once recommended build is released
If recommended build is not released in acceptable time, test with a build preferred by plugin developers
Move on to next steps once craftbukkit successfully launches SMP 1.4
Check for Essential build compatible with version of craftbukkit
Download and install all modules of Essentials used, including GroupManager
Test server with old configs for server stability
Play with versions of Essentials/craftbukkit until acceptable level of stability is achieved
Redo configuration of Essentials to take advantage of latest features
Redo configuration of GroupManager to provide new functionality to user groups
Move on to next steps once bugs are eliminated or minimized
Document any persistent bugs/issues from Essentials plugin
Install core group of plugins on top of existing server install
Core group of plugins to install: iConomy, Townymod, LWC, and BigBrother
Copy all configs from production server and make sure to tweak as to not affect production databases
Download and install latest builds of each plugin one-by-one and test each one for stability/functionality
Tweak version of craftbukkit and releases of each plugin to find a balance of functionality across all core plugins
Document any bugs/loss of functionality from core plugin group
Install secondary group of plugins on top of existing server install
Plugins that depend in iConomy: SimpleShop, LocalShops
Other secondary plugins: CreativeStick, FlatEarth
Copy all configs from production server and make sure to tweak as to not affect production databases
Download and install latest builds of each plugin one-by-one and test each one for stability/functionality
Tweak version of craftbukkit to work with plugins only if it does not break functionality of Essentials and core plugins
Test a migration of SimpleShop and LocalShops SQLite Databases to MySQL Databases
Document any bugs/loss of functionality from secondary plugin group
Make a determination whether or not server is ready for live use
Check documented buglist and and see if any bugs can be eliminated
For bugs that require developer work to fix, determine whether or not bug is release-critical
Once buglist is acceptable for production use, proceed to live rollout
Roll out new server build to production
Back up server state completely for failback purposes
Back up all pertinent databases
Bring down server and lock down network from users
Move all plugin versions to production
Deploy all server configs, ensuring all configs are set for the production environment, not the test environment
Migrate databases from SQLite to MySQL if applicable
Bring server up and perform tests on all plugins/functionality
Perform health checks on the server and application
Bring network up and allow users to log in
Update and install Dynmap to work with latest version
Dynmap cannot be worked on from the test environment due to its configuration
Once Beta 1.4 is in production, Dynmap plugin can be updated/tested
If Dynmap does not work after rollout, add to buglist
Over time, update craftbukkit and plugins to reduce/eliminate buglist
As bugs are fixed in future versions of craftbukkit and the plugins, rollout new versions
Perform testing in test environment to ensure no regressions occur
If regressions do occur between plugins after rollout, weigh regressions to functionality gained and determine which rollouts are desired
Make rollouts over the days after server is live on Beta 1.4 to improve server state over time
If you bothered to read the list, you can see it's a lot of work to upgrade the server. Eight of these steps are necessary just to bring the server up on Beta 1.4. After that, there's still a lot of pushing and pulling needed to bring the server back to full functionality. Hopefully this upgrade won't as bad as upgrading to 1.3 was (almost 50 hours of labor), but I'm not holding my breath.
Just reading all that is tiring. I can’t even imagine what it’s like to actually do it. Wow, I really do hope things progress a lot smoother than the 1.3 update. May the force be with you.
ok. Hand me the derp crown. I did a bad thing. I use minecraft in the very default state, and it auto updated before i read the blog. I will have to see about finding a copy of the older client to come back on, or i will just have to play solo for a bit. Just giving you all a FYI.
Don’t feel too bad, I tried to download and update MC on one of my flash drives. Turns out it didn’t just update on my flash drive, it also updated on my laptop. >_> So single player it is for me for a while.
March 31st, 2011 - 08:57
Sounds Good, I can’t wait for 1.4 and I hope everything goes smooth for you Pete
March 31st, 2011 - 14:09
Just reading all that is tiring. I can’t even imagine what it’s like to actually do it. Wow, I really do hope things progress a lot smoother than the 1.3 update. May the force be with you.
March 31st, 2011 - 17:04
And also the Derp
March 31st, 2011 - 18:33
ok. Hand me the derp crown. I did a bad thing. I use minecraft in the very default state, and it auto updated before i read the blog. I will have to see about finding a copy of the older client to come back on, or i will just have to play solo for a bit. Just giving you all a FYI.
March 31st, 2011 - 22:22
Don’t feel too bad, I tried to download and update MC on one of my flash drives. Turns out it didn’t just update on my flash drive, it also updated on my laptop. >_> So single player it is for me for a while.
April 1st, 2011 - 00:00
Well you see now, Pete DID tell you not to update
April 1st, 2011 - 00:01
Maybe we should listen to Pete more now, right Trevor?
April 1st, 2011 - 00:06
I didn’t say not to update. I said not to update unless you know what you’re doing. There’s a difference.