Posts: 2
Joined: Jul 2006
Reputation:
0
Lol fixed it. Key Words are a bit tricky. It couldn't find threads with "2.0.0" in them, but it found ones with "yeah" in them. Oh well.
Thanks Gamester17, I'll give it a try.
Posts: 3
Joined: Aug 2006
Reputation:
0
Hi. Just wondering if you guys could give a rough estimate on when you hope to get XBMC 2 out. In no way am I pushing or nagging by asking this.
It would be awsome if it could be atleast by the end of the year.
Posts: 1,544
Joined: Jan 2005
Reputation:
0
Yup... nobody with more than 10 posts would ask a question like that.
Posts: 1,544
Joined: Jan 2005
Reputation:
0
The reason I said that is anybody with anykind of background in XBMCs forums would know you NEVER ask them that. It'll be done when its done and that will be when they feel its done and not a minute before.
No offense but I dont see the needs of a single person "holding off a release" that they are just going to throw up and not support without adding a pricetag (Yes I refer to your charging for services and support). They do this for the most part because they enjoy the work and the challenge not because they are trying to make a buck.
Perhaps offensive, Ive tried your AID and to be quite honest, your releases should be more current based on your own improvement and not dependant of software around you, **I edited and decided to stop before I went into one of my rambles**.
Posts: 294
Joined: Feb 2006
Reputation:
2
plugh
Senior Member
Posts: 294
I'm a bit hesitant to post this, and I hope it will be taken constructively.
I'm trying to figure out what the definition of 'feature freeze' is?
Since the 6-25 t3ch build a number of interesting enhancements have been made - the uPNP stuff, the profile stuff, the renderer stuff, coreavc, dvr-ms, python libraries, I could go on...
I've also noted a significant increase in 'problems' with releases since 6-25; in fact, when I've tried these newer releases, for one reason or another I end up going back to the 6-25 build.
The devo's had made tremendous progress since this 'feature freeze and bug-bash' started; as a user I'm making the observation that the 6-25 build is very stable (with a few exceptions) and has a feature set consistent with what we had back in March when it started.
So in the context of the 'feature freeze', the 6-25 build, with the addition of a few critical fixes (like the xlink kai crash fix, some smb fixes, the updates for the imdb changes) seems nearly "perfect" - as in perhaps it could form the base of a new 'stable release'...
Whether that would be "2.0" or "1.9" or whatever, it just seems like that build would be a good place to put a stake into the ground, applying only necessary bug-fixes and create a 'release candidate' build.
The other "neat stuff" that's been done lately would be part of a future 'stable release' (which I would look forward to, once all the 'new' things were shook out).
Anyway, I hope this post will be taken in a positive light. I know the fun and excitement of adding new, neat, things, but having been a software project manager in the past, I also know that you need to find that right point where you say to the team "this build is the basis for the next release" and only do necessary bug fixes to that build for the final release. IMO the 6-25 build is it.
Posts: 2,288
Joined: Nov 2005
Reputation:
5
what exactly are you talking about in the way of "problems"?
Posts: 5,008
Joined: Sep 2003
Reputation:
30
pike
Team Kodi Admin
Posts: 5,008
Then you're not helping AT ALL. You only piss me of basically.
If you say there are issues, but won't specify them, that's WHINING.
One can debate whether or not we SHOULD have frozen earlier, but it won't change the current situation. We have current CVS to work with and make 2.0 worthy. I can assure you it's getting close to a 2.0.0 release.
And if you refuse to specify which issues you found "after '6-25' build", you will just have to live with them. I don't want to hear any whining about them, unless you report them.
Posts: 294
Joined: Feb 2006
Reputation:
2
plugh
Senior Member
Posts: 294
I am astonished at the reactions. Neither of my two posts 'complained' or 'whined' about ANYTHING. And as far as 'helping', well, one recent example was my work with Elupus to track down a problem with the new smbclient port. (That fix appeared in the 6-25 build, BTW)
The point of my post wasn't about 'issues' - I've already stated that problems I've encountered post 6-25 (for example the subtitle sticking thing introduced in the 7-25 build was fixed in the next build) are being / have been addressed.
Pike, I'm not trying to debate or be critical of any 'should have dones'; I assume your cvs system will allow you to create a fork based upon the state of the system when the 6-25 build was done, and that you could use that fork as the basis of a release candidate (adding in any critical fixes from the main thread) - but that is, I will admit, an assumption based solely on my experience with other code management systems. As a user, I wanted to provide feedback that said "hey that 6-25 build, with a few tweaks would be a really good candidate for the stable release announced in this thread". You may disagree (and apparently you do) that it doesn't meet the goals set out in this thread.
It was not my intent to anger anyone; I'm outta here...
Posts: 3,746
Joined: May 2004
Reputation:
20
Livin
Posting Freak
Posts: 3,746
One thing you will come to see is that most open-source and free software is always WIP. You need to treat it as such and forget about "releases".
Just use the build(s) you are happy with if you have issues with something.
I upgrade my build almost weekly, depending on the fixes and features added... and rarely have any issues (see any bugs). I use it almost daily to watch videos and listen to music.
Take it for what it is, great free software.
If you have a suggestion on how to make the software better, fantastic but otherwise leave the devs alone to fix and enchance the app they can run the project how they want.
I'm not an expert but I play one at work.