confusing roadmap for RC2 (1 Viewer)

[sylvio2000]

Since the last 2 weeks I watch the progress of fixing bugs for Mediaportal RC1 and Tv-Server.
But I have seen that every 1 or 2 days new bugs are added to the fix-list and the percentage of already solved bugs is shrinking.

Dont take me wrong. It is fantastic that bugs are fixed, but imho there should be a limit of a maximum number of bugs for rc1.

At the moment there seems to be no end for the progress of fixing bugs

Hope you understand what I mean. Maybe someone can clear me up

 

[rtv]

The team decides for "small bugs" which are vital to be fixed for Version 1.0 if they can be done "quickly". If yes they'll be fixed for the next Release Candidate.

Keep in mind that there are also people who are not that familar with open source principles and googleish "everything is beta status". Those consider a "Release Candidate" absolutely different - more like a static version which ALREADY is the 1.0 (if all goes well).

So finally we try to find the best compromise between "RC2 has no critical issues" and "RC2 is almost final 1.0".

 

[sylvio2000]

Ok, I think I understand your philosophy

Hope it doesnt take too long until RC2. Cant wait to test the new version.

Btw: Will there be a RC3?

 

[GoldenEye]

I would doubt that - considering that ther's a bug list to be solved in version 1.0.0.1 belwo the end of the RC2 list of bugs.

G.

 

[Gixxer]

new RC3 section added to roadmap.

it would be nice to know what is the difference between RC2, RC3, 1.0.0.1... and why are bugs added to RC3 instead of RC2.

 

[sylvio2000]

Yes, I also would like to know why some bugs are added for RC3 and not for RC2. There must be some kind of priority.

Btw, I think RC2 is comming within the next days. We are already at 98%

 

[revs]

The whole alpha/beta/RC thing seems to vary between projects and companies. I see it as follows:

alpha - missing features, probably buggy, work in progress. very early stages
beta - all major features complete (although maybe not bug free or working correctly)
RC - a Release Candidate is just that. A build that is good enough to be a Release. You then get a RC2 is there is a bug found in the RC. There should not really be that many RC builds (if you do your bug testing/fixing correctly at beta stage!). The final RC is declared a "Golden Master".

There are no set rules however, and at the end of the day it doesnt matter as long as the product is as good as it can be!!

 

[sylvio2000]

Ok, I think you understand me wrong

I do know what an alpha/beta/RC ist, but I just would like to know, why there are already some bugs listed for RC3 when RC2 isnt released yet.
There must be a reason for doing this

 

[chemelli]

RC2 is coming so nothing can be assigned to this release, otherwise go in a never ending loop.
New discovered bugs are then assigned to RC3 to log them and don't forget about

Simone

 

[tourettes]

RC2 is coming so nothing can be assigned to this release, otherwise go in a never ending loop.
New discovered bugs are then assigned to RC3 to log them and don't forget about

Also some bugs are assigned to devs that dont currently have free time for development.Of cource there is no reason to delay RC2 because of that and those bugs are assigned to RC3.