Here’s what you do:
Have an account on github.com.
Set maidsafe/safe_vault to “watch”.
In your profile, configure “notification” to be by email rather than by web.
Have a smartphone that beeps when a new email arrives.
Look at every email the moment it arrives.
(Although I cannot imagine why some people do those last two things).
Then forget about it, until…
A new entry appears under “maidsafe/safe_vault/releases”
Then, jump on here and let everyone know.
perfect plan - but sorry my phone doesn’t support push-notifications 
Look what is waiting to be committed:
yeeeeeeey apt 
i love apt!
If folk are wondering what ‘packaging’ is about, this article from Digital Ocean is very good:
This should make installs way easier. So will new installs be released as package manager files or as something we can order from the command line? Or do we need to do some configuring first?
I might set up an arch package to test the churn on my laptop while hopping around campus.
EDIT: @blindsite2k you can do anything from the command line! But I would love to see a v1.0 included in, say, gnome software center like tor or ipfs.
It looks like their using this method:
Install a Package from the Local Filesystem
Sometimes, even though software isn’t officially packaged for a given operating system, a developer or vendor will offer package files for download. You can usually retrieve these with your web browser, or via curl on the command line. Once a package is on the target system, it can often be installed with a single command.
To install and start the SAFE Network Vault, do the following:
curl -O http://yum.maidsafe.net/repos/maidsafe.yum.gpg.key
sudo rpm --import maidsafe.yum.gpg.key
sudo curl -o /etc/yum.repos.d/maidsafe.repo http://yum.maidsafe.net/repos/maidsafe.repo
sudo yum update
sudo yum install safe_vault
To install and start the SAFE Network Vault, do the following:
wget -O - http://apt.maidsafe.net/repos/maidsafe.apt.gpg.key|sudo apt-key add -
sudo wget -O /etc/apt/sources.list.d/maidsafe.list http://apt.maidsafe.net/repos/maidsafe.list
sudo apt-get update
sudo apt-get install safe-vault
I think it will be simpler than that: run a short command to update your repo list, and then install / update directly from the MaidSafe repos.
Some will prefer to download and install separately for improved security, but most will want the convenience, so I expect MaidSafe will provide that.
There will be a bump in the (sub)version of safe_vault before testnet4.
I was expecting that bump in crust not the vaults. How do you figure?
Crust is a dependency of safe_vault, and the changes to crust are major (therefore breaking), so I would expect a version bump to ripple upwards to safe_vault, because of its adherence to semantic versioning.
Previous tests always seem to be accompanied by a new version of safe_vault. Even the current developer network, which only had an accompanying launcher release, had a silent version upgrade of the vault because something (almost certainly a new vault binary) was hammering community1 until we switched ports. Now, they can get away with having a breaking binary without a change to the version number for an internal (to the company) network of vaults, but for a community test such as testnet4 they have to bump the version number to make the incompatibility clear.
There is a huge logjam of pull requests waiting in crust. Inside each of the four there’s a whole bunch of them. Roughly half of them have passed their continuous integration tests. Is this what is going into testnet4 and will it be ready by tomorrow’s weekly update?
We are moving so quickly (the devs try to keep out of all this as they need focus) that we know only within a few hours when an update is going out and what it will contain. When it’s decided we do a bunch of test again and ready binaries and deployer stuff as well as start the new testnet and ready the dev update. It’s all very fast as we work in the open and it’s posted here as soon as we hit the release so several folks all on slack ready to press various buttons a once 
Makes it all fun but furious.
Crust still has a couple of things to finish (nat_traversal / igd) and routing will have a major update coming with size of messages and priorities altered to better work with smaller nodes. So it’s all steam ahead there, we will see what tomorrow as ever brings though. A lot of balls in the air right now, may not be wise to rush this one.
… well with this info and the Decentralised Web Summit that kicks off Wednesday at Internet Archive (where Paige is representing MS) and the run of events recently… my take and feeling on this is yes, we’re going to get some a little special tomorrow ,) just my idea! And we won’t expect any fireworks or champagne corks, just the kick off of a measured and accumulative sharing of news and updates- that start the feeding those network effecta we all want to see take hold. It could be a fun week ,)
definitely no need to rush, that would not be i n character 
and any sign of that and you’d have us all nervous ! a solid testnet 4 is worth the wait …
I’m glad I only arrived on the scene 2 ½ months ago. I could not have stood up to years of this anticipation, I’d be a nervous wreck by now. (or not… maybe I would have achieved a yogic state like the guys that lay on a bed of sharp nails).
I am pretty sure at least two community members left having achieved enlightenment after little more than a year on this forum, although those of us that remain here 
will be more than happy to see SAFEnetwork roll out across the planet
