Well, let's say it takes Tinnus 2 minutes to answer each post asking how long it will take... let's guess on the low side that there have been 200 posts asking that question... that's 400 minutes off the bat, which is 6.25 hours.
Now, let's say that Tinnus can only work on this project in his spare time. Since he's a full-time student, let's say he has 6 hours of classes per day, with 20 minutes of studying for each hour of class (on the low side).
Let's say he sleeps for 8 hours per day.
We're now at 8 hours per day free time.
Let's add in time for eating (3 hours per day), and 2 hours per day for miscellaneous (showering, bathroom, talking to friends, doing laundry, shopping for food, etc.).
This leaves 3 hours per day to spend on free time (as I said, this is very generous).
Let's say that he wants to spend half his free time working on software programming... and he's working on LJP RC3 AND LJR....
So, let's give his LJP time around 1.75 hours per day.
Above, we've already eaten up 6.25 hours responding to posts asking when it will be done; that means before even looking at the code, it will take him around 4 days to get to the point where he can start coding.
Considering that the problems he's trying to fix do not simply involve coding time, but debugging time on a particularly sneaky bug, remember that for each hour coding around 10 are needed for testing and debugging... I'd give him 2 hours of coding left, which means 20 hours of debugging.
This gives us a total of 22 hours left on the actual project, which in real time works out to around 12 days.
So, if nobody else asks him when it will be done, you can count on a minimum timeframe of just over two weeks. This is if everything works perfectly, there aren't any mishaps (like him needing to reinstall Windows XP, which can add days to the forecast) and he doesn't want to do anything to actually relax during his days.
As far as maximum estimate, it's possible that he will never find all the bugs, and so will never finish RC3.
The resulting answer is that he will have to wait 2 weeks to eternity... plus time answering whatever questions get asked after the one you just asked
(note... all numbers pulled out of my imagination, and of course, people don't actually work in time blocks like that -- it's a good way of project forecasting however. Who knows? He might actually have it released before I finish typing this post!)
That leaves 24 - 12 - 8 = 4h for everything else, including eating and such. So I'll only be able to code on weekends, or in the case that i study less. 
