.stvi imports with 6.013 not sticking

[GKusnick]

Originally Posted by Patilan

Can't you just realease a build with what you've fixed already?

There's no "just" about it. Doing a release, even a beta release, requires internal testing and validation, documentation, packaging, updating the website and bug report forms, etc. Doing all that takes time away from actually fixing bugs, so it makes sense not to do it too often.

Since there are known workarounds for this particular bug, I don't see that it's all that urgent to get a fixed released ASAP.

[marchold]

Originally Posted by nyplayer

This surely could not have been missed in beta testing geez. This is so annoying. Setup all the clients reboot and all the changes are gone. All my clents are keyboardless and headless. Not easy to a (Ctrl+Shift+F12)

I have the exact same setup, There is an easy solution. I installed ultra vnc server on the SageTV keyboardless box and the client on my keyboard(laptop) machine. This works great. Once connected the video does not display on the "vnc clinet" but you use your keyboard to control it. If you exit full screen mode you can see the Sage UI on both screens. Press Ctrl-Shift-F12 or whatever.

[gplasky]

Originally Posted by marchold

I have the exact same setup, There is an easy solution. I installed ultra vnc server on the SageTV keyboardless box and the client on my keyboard(laptop) machine. This works great. Once connected the video does not display on the "vnc clinet" but you use your keyboard to control it. If you exit full screen mode you can see the Sage UI on both screens. Press Ctrl-Shift-F12 or whatever.

You could also just make the change on the one with the keyboard and copy the STV out to the rest. No sense in making it tougher than it really is until the fix it.

Gerry

[Patilan]

Originally Posted by GKusnick

There's no "just" about it. Doing a release, even a beta release, requires internal testing and validation, documentation, packaging, updating the website and bug report forms, etc. Doing all that takes time away from actually fixing bugs, so it makes sense not to do it too often.

Since there are known workarounds for this particular bug, I don't see that it's all that urgent to get a fixed released ASAP.

Dear GKusnick,

Are you in any way in the position to speak on behalf of Sage? Because if you are not, then please think before speaking. I am very well aware of the workarounds for this particular bug, and that was not what I was talking about. I don't think I need to bring here 30 links from different threads to illustrate my point.

FYI, I've done my share of programming in my life time. And believe it or not -- especially when we are working on betas -- many times we would even do daily builds. So don't give me that bull about validation, documentation, packaging, and stuff. It is a beta that we are talking about. And besides, they charged us $30 a piece to be their beta testers, they could at least keep us closer to the current developments.

My original post was more about venting, rather than a desire to start a useless argument. So I'll leave it at that.

Yours,
Patilan

---
edit: typos.

[GKusnick]

Originally Posted by Patilan

I am very well aware of the workarounds for this particular bug, and that was not what I was talking about.

Sorry, I assumed that since you posted on this bug-specific thread, you must have been talking about this bug. A natural mistake.

I do not speak for SageTV LLC but I am entitled to express my opinion on how beta releases are scheduled, just as you're entitled to express yours.

And the $30 upgrade charge has nothing to do with being a beta tester; in fact, for people upgrading after the beta, it will be $40.