From: Mike A. H. <mh...@ww...> - 2003-07-22 05:11:00
|
On Mon, 21 Jul 2003, Stephen J Baker wrote: >>>I'd like to fix the menu problem before freeglut gets into any >>>distro's. >> >> I need to put it in rawhide very very soon if it is going to get >> into our next release. > >Can you give us a definite cut-off date? Not a definite one, but it's possible to happen in approximately 2 weeks, that would very strongly help. >Whilst I don't personally have the time to go in and change how the >menu's work, it's possible that others do - and given the incentive, >it's possible someone will pull a fix off in time. Right. >> However, I will honour any upstream >> project's request to not put a given release into the distro if >> requested. > >That's good news! > >We should discuss whether we'd like 2.0.0 to be distributed in >RedHad despite the menu issue. It's not cut-and-dried. "Red Hat". ;o) I'd like if at all possible to get 2.0.0 into rawhide (or rolling development) even if there are a few bugs, which can hopefully be addressed over the next month or two, etc. >> Is this bug something planned to be fixed for 2.0.0? > >No - we intended to get it in 2.0.1. It's not exactly a simple >matter. Ah. Worst case then, is that I could put freeglut in before the cutoff date, if that is acceptable with you guys, and then pull it out later if it turns out to be too unstable or if the bugs present are considered too much of showstoppers. I can always remove something after the cut off date, but I can't necessarily add something. Technically our cut off date has already expired, but I've got a bit of leaway with the glut issue. >> I wanted to get 2.0.0 in our next release at least, otherwise >> we're in a bit of a bind - but that's our problem of course. ;o) > >Well, give us a firm cut-off date and we'll see what we can do. Just my comments above. I don't want to pressure anyone to work on something, just to meet Red Hat deadlines either. That wouldn't be fair or right. But if it is possible to release 2.0.0 within 2 weeks, that would be great even if some bugs are present. If they can get fixed after that sometime, before our ship date, I might be able to pull them in anyway likely. We just announced our Red Hat Linux Project: http://rhl.redhat.com which was something I wished I could have mentioned last week, but couldn't quite yet. ;o) Our new project and it's objectives, etc. will allow me a bit more flexibility for decisions like this also. My ultimate personal goals with respect to freeglut are, in order: 1) To try to help the freeglut project to get it more widely tested, and to help the freeglut project to completely replace glut in all respects. 2) To help the freeglut project to get integrated into all major OSS operating system distributions, and advocate it over GLUT 3) Lastly, to solve the Red Hat GLUT problem so we have a better glut solution for users, customers, and the general community. I consider 1 & 2 more important in the grand scheme of things, and #3 is my own personal headache to deal with. ;o) Any effort the project or others can do to help me resolve #3 though is also greatly appreciated too. ;o) >> If 2.0.0 comes out soon, I'd like to include it, but I can always >> update it prior to our final release, assuming the menu bug gets >> fixed during that timeframe. I've got a freeglut snapshot from >> January or so in rawhide now, but it's unlikely anyone has used >> it yet. It probably wont get usedu until our libglut is >> freeglut. > >Understood. I'll be gone for 2 weeks, but when I get back, I'll see where things are at, and see what I can do on my end at the time. Have fun guys! TTYL -- Mike A. Harris |