expunge last edited by
Is there any chance we can do a weekly snapshot that is a testing snapshot? By testing I mean it has all the bugs that have been discovered in the past week fixed, but no new code added, so it can be expected to be more stable than the daily snapshots? I think we're working with a moving target here with the daily snapshots because I never know if my 2.0 box is going to run or not after I upgrade. As much as it has been said that 2.0 is not for any production environment, I am using it in some limited production settings just because it provides features that 1.2 cannot. I realize that there aren't going to be stable snapshots of an alpha release, but something that has the fixes to current without new bugs being created would be great for testing.
Just a thought…
Accounts last edited by
I think a better option for be to be able to roll back to your last firmware via the console or web ui. Snapshots have killed me a few times. One got me just today went back to build from the 9th dec.
The weekend snapshots seem to kill me more than anything.
nocer last edited by
I second that, and would love to see if there's anything that "pre-tested" snaps around but the snapshot is only a snapshot by its nature, neither more or less you both know well.
I never know if my 2.0 box is going to run or not after I upgrade.
Neither do I.
Snapshots have killed me a few times. One got me just today went back to build from the 9th dec.
I was killed 100+ times already with sorta FUN ;D but I wish the developers would hear your option highly be requested for an enhancement.
databeestje last edited by
Weekends often see the most active developers. And snapshots are just that, nothing more nothing less. At some point the team will call a release that should work to a certain degree which we would mark as being good enough for testing uses.
Until then I suggest keeping a copy of a known good 2.0 snapshot so you can somewhat revert.
sullrich last edited by
Yes, keep a copy handy of the last known good snapshot and always backup config.xml.
The snapshot server is basically building images 24*7 but we are working on ways to overhaul this into a much more manageable system.
nocer last edited by
Indeed databeestje and sullrich, I already done that since I moved onto 2.0-AA rail. That's the way play with snaps and I can survive.
I just got kiiled by 20081223-0735.tgz :D :D :D
cmb last edited by
Is there any chance we can do a weekly snapshot that is a testing snapshot? By testing I mean it has all the bugs that have been discovered in the past week fixed, but no new code added, so it can be expected to be more stable than the daily snapshots?
There will be improvements in our revision control to ensure significant new features are better tested before getting pulled in to limit regressions, now that we should be switched to git within the next week or so. But to do exactly this simply isn't reasonable nor will we accommodate it. This is alpha software - if you're using it, expect things to change rapidly at times, and potentially break when major changes are pulled in. Don't use it if you can't deal with that. To properly do what you ask would be a significant amount of work, because multiple source branches would have to be maintained.
The entire purpose of having 2.0 available right now is so people can test the code as it is in CVS in RELENG_1, it's not to concern ourselves with not breaking things in a few snapshots here and there. If you're using 2.0 right now, you're volunteering to break your network, and we've told everyone nothing but that since the first day it was available.
idelta last edited by
No distractions. Make your great work. We will help, as can in terms of testing. As long as necessary. Personally, I look very much hope at 2.0. Sorry for GOOGLE english. ;)