I normally look for major changesets (usually done by bonefish, axeld, mmlr) and avoid using any revision from these onwards for about 2 weeks. Also, look for tickets that follow a certain changeset as this may indicate new bugs. Major changes have a greater chance of creating bugs and instability.
2) download & use it in virtual machine. I use raw images + Qemu but I think you can do it with ISO. This allows you to see any major bugs but without intensive testing you may miss something like the issue going on now. That's why you must do 1) above too.
Doing both 1 & 2 above should help you avoid any buggy nightly.
Also, good to have 2 or 3 Haiku partitions. This way you can test out nightlies and install Alpha1 or go back to stable nightly if you find one to be buggy. If you end up with revision that causes data corruption then you could lose your personal files!
Comments
Re: r35274
They were rolled back to this version because newer nightlies were unstable. I believe that one should be good but I have not tested it out.
Best approach is:
1) check:
http://dev.haiku-os.org/timeline
I normally look for major changesets (usually done by bonefish, axeld, mmlr) and avoid using any revision from these onwards for about 2 weeks. Also, look for tickets that follow a certain changeset as this may indicate new bugs. Major changes have a greater chance of creating bugs and instability.
2) download & use it in virtual machine. I use raw images + Qemu but I think you can do it with ISO. This allows you to see any major bugs but without intensive testing you may miss something like the issue going on now. That's why you must do 1) above too.
Doing both 1 & 2 above should help you avoid any buggy nightly.
Re: r35274
Also, good to have 2 or 3 Haiku partitions. This way you can test out nightlies and install Alpha1 or go back to stable nightly if you find one to be buggy. If you end up with revision that causes data corruption then you could lose your personal files!