I love the OMSC, but all you did last days is very irritable. You can not write text like this:
“Today’s developments
February 28, 2015
Hi everyone
We’ve made a lot of changes since Alpha 4, and today we’ll be announcing a relase candidate.” (Updates tab on link)
and then creating a theory about “placeholders” and do clossing all topics with users questions about RC.
What is the sense of place holders? There is no sense to announce something that we do not know when it will be, telling when it will be…
This is very strange Public Relations for your Company, doing bad climate and unfortunately it is still continued…
This is not a company, it’s volunteers working on free software in their own time. Could you please inform me how not giving a firm date (and thus ensuring the software is of good quality) has caused harm to you?
We have had internal release candidate builds on our Downloads server which users have been trying
S
Where did the OP say he was caused any harm?
He didn’t, but he has inferred that not having a firm date has had some kind of dramatic effect on him. There have been internal RCs for days (which are publicly downloadable I might add), but we just want to make sure we get it right, because you can sure as hell bet that if the release was buggy people would be the first to complain.
Well, to start with, dont delete the threads.
Thats not very a professional approach.
And just put a sticky thread in the forum saying the RC is still being testet and as soon you have something more solid you will let us know.
I dont think anyone is complaining about all the hard work you guys put into this.
People just want information, even if its not what they want to hear.
Kind regards
Sqnk
1 Like
Well, of course I will not die if there will be not the RC tomorrow 
But I have seen many projects (open projects - let mi add) and never met such situations.
Just strange for me (and probably not only for me) and thats why I wrote.
In my humble opinion would be better not to write such things than writing something what could make people confused.
P.S.
Still keep fingers for you and your hard work!
P.P.S
Wheres is the link to that candidate build?
http://download.osmc.tv/installers/diskimages/
Looking forward to the “final” (or almost) build, Sam, just the way I think all the other impatient users feel right now, that’s all there is to it. And I also think that it would be interesting if you let us know which are the modules / areas you’ve had the most hassle with (sort of a technical update) - is the list here (Issues · osmc/osmc · GitHub) updated?
No threads have been deleted at all.
Yes, we could do that, but that takes time away from actually working on the product. I think this is something a lot of users don’t realise. We can talk about how the work is going all day but then we’re not actually getting anything done? The GitHub issues page is not reflective of the work being done: most of those issues aren’t really valid or applicable.
See download.osmc.tv
Agreed, which is why we will never be giving any release dates in the future. We did try and make it clear the date was a placeholder. We put the Thunderclap up as we wanted some social reach and to get support. It’s a shame that one user even called it false advertising.
S
Oh noes! You didnt get that thing you wanted on the day that it was said it might or might not be available!
Does that just about sum up your thread?
One would think ADULTS would be able to endure a trivial disappointment. Now, to be fair, most GROWN PEOPLE did comprehend what the date was, and are not complaining that the clearly stated placeholder date was aspirational.
Saying that Sam is not treating users seriously is offensive. And you should bloody well apologise.
In the end it all comes down to understanding both sides and, most important, understanding we all want you to carry on your great work we know you can deliver, as everybody will benefit from a successful and bugfree osmc final build.
By the way: do you plan in the near future to also provide the build filesystem (or a how to) we are used to from raspbmc? it was great being able to build xbmc/kodi on our own and test various stuff without waiting for an actual release.
Thanks again for everything!
Watching Sam build out osmc and transitioning from raspbmc has made me realize a few things about him. The only thing he really cares about is making an awesome product for you guys no matter what it takes. PR and deadlines doesn’t matter that much to him if the product is not good enough.
This is what I call a “good problem” to have if you can even call it a problem.
And again. This is open source so Sam doesn’t owe you anything. Not even replying to threads like this. But he does, which takes more time out of his schedule to build osmc.
@exxperto: I don’t know if those are the build filesystem, I was curious if we were going to get something similar to OSMC
The only link I can find on osmc page is https://osmc.tv/download/images/. And there is no builds. Is it possible to someone who doesn’t know your link to find it sufring official site? Because only in this situation we can call it “publicly downloadable”.
Fully agree with this and I fully understand and Support Sam’s approach. The only misleading thing I can see was the thunderclap, promising something that was never meant to be promised - I think that’s a lessons which had to be learned the hard way.
I still appreciate the outstanding quality of what this team is producing here and this tells me again and again to relax and wait just a little bit longer.
Go on, do your thing, learn your lessons but never stop because of temporarily rough weather.
I know that it is open projects.
Sorry, maybe I am wrong, but as I can see Mr. Sam is going to make a buisiness with Vero product. So, people interested in this product are looking here and there - PR should be important. Today every word you write in internet is important.
Hold on a minute…
Is this a thread about free software (that is being developed by a small group of caffeine addicts for free, who work for 30+ hours without sleep to ensure that when the general public get hold it there will be as few problems as possible) is taking a while to reach a state that would be considered “stable” and “working” ?
I will quote my post from 4days ago
If Sam, and the other devs, rush it and release what could be a buggy mess then you would be in here complaining about it.
So Sam takes his time to ensure that everything works, and everything is stable etc etc and you complain about it not being released on time…
So, what do you want,
A potential buggy mess or something that works?
Get a grip guys, show a little bit of appreciation and understanding of the time and effort that all the devs put into this project along with the sacrifices they make.
3 Likes
“Yes, we could do that, but that takes time away from actually working on the product. I think this is something a lot of users don’t realise. We can talk about how the work is going all day but then we’re not actually getting anything done?”
This is sooo true, especially when working with limited resources.
Remember folks - Good/Fast/Cheap, pick two.
Cheers,
Ian
Both sides are right, and I think it can also be said both sides are wrong.
OSMC team is working hard.
Users are VERY appreciative, though anxious and a little impatient.
However, I think the point is that users wouldn’t be so anxious and impatient if something hadn’t been announced for the 28th, then pushed to the 5th and then being told on the 4th that there is no release for the 5th.
As users, we want a good product and that is absolutely what Sam intends to deliver.
Maybe going forward: build out the updates, make sure everything compiles correctly, complete basic internal testing and only then announce that a new release will be available a week later? That way the team can have time to run through more thorough testing and the users can have a date in mind that is more than just a ‘placeholder’.
1 Like
It wasn’t pushed to the 5th.
If people had actually read the update they would have seen :-
February 28, 2015
Hi everyone
We’ve made a lot of changes since Alpha 4, and today we’ll be announcing a release candidate.
It’s a few days early to call things ‘final’, so I’ve decided to test the waters, as well as provide a smooth upgrade path from here on to future builds of OSMC.
I have adjusted this date as a placeholder for now.
I’ll keep you posted, and thanks for your support
Sam
1 Like