From: Toby C. <tco...@di...> - 2005-11-26 20:42:34
|
Hi All, I just thought I would start a discussion re what needs done before a release of player 2. Also it would probably be useful to just set a date and work to that otherwise it may just carry along as is for another 6 months :) So what is in our todo list? obviously documentation updates are still there, Other than that Ive been using player cvs on all our robots for a while now and havent been having any major issues, I think the stability is not quite on par with player 1.6 but getting close. Three issues/comments that I would like resolved/thought about: - Player CVS wont build on a clean install with --disable-alldrivers some drivers are required for the library to build, and there are a couple of dependencies that arent in autoconf. I havent had time to track these down - Can we change the header install paths to be include/player/* instead of having so many seperate folders? - I dont think we have resolved the p2os driver command conflict between usage for the arm device and usage for the position device. Im sure there are other things...is there a webpage we could collate these and then swiftly deal to them so we can get a release out? even if it is a 'unstable' release. Toby |
From: Geoffrey B. <g....@au...> - 2005-11-26 21:13:24
|
I can think of a couple to add to the list: - Python bindings don't work correctly. - Message buffers overflow a lot when they probably shouldn't. Geoff Toby Collett wrote: > Hi All, > I just thought I would start a discussion re what needs done before a > release of player 2. Also it would probably be useful to just set a date > and work to that otherwise it may just carry along as is for another 6 > months :) > > So what is in our todo list? obviously documentation updates are still > there, Other than that Ive been using player cvs on all our robots for a > while now and havent been having any major issues, I think the stability > is not quite on par with player 1.6 but getting close. > > Three issues/comments that I would like resolved/thought about: > - Player CVS wont build on a clean install with --disable-alldrivers > some drivers are required for the library to build, and there are a > couple of dependencies that arent in autoconf. I havent had time to > track these down > > - Can we change the header install paths to be include/player/* instead > of having so many seperate folders? > > - I dont think we have resolved the p2os driver command conflict between > usage for the arm device and usage for the position device. > > > Im sure there are other things...is there a webpage we could collate > these and then swiftly deal to them so we can get a release out? even if > it is a 'unstable' release. > > Toby > -- Robotics research group, University of Auckland http://www.ece.auckland.ac.nz/~gbig005/ |
From: Brian G. <br...@ge...> - 2005-12-14 01:57:50
|
hi everybody, It's been a long time coming, and I think it's about time to get Player 2.0 ready for the masses. I've added a new category for keeping track of our 2.0 TODO list in the Feature Requests tracker. To see the list: http://sourceforge.net/tracker/?atid=433167&group_id=42445 and select "Player 2.0 TODO" from the Category drop-down. The idea is that we can keep track of our TODO list here, closing tickets as they're taken care of. Feel free to add new ones, being as specific as possible. And feel free to fix things and close tickets. If you want permission to modify a ticket, let me know. I've added the items mentioned on the developers' list, plus a couple of things that I want done. I've also added a ticket for each driver that is currently disabled by default in CVS, on the assumption that the driver needs to be updated to the new API. Now, I know this assumption is not correct for all drivers. If you have updated a driver and it is working, please enable it by default in acinclude.m4 (ask me to do it if you don't have write permission there). Alternatively, if you think a driver should be deprecated rather than updated, say so in a comment to the appropriate ticket. In addition to this new list, we need to run through the accumulated bugs and patches, fixing and incorporating wherever we can. In terms of a release date, let's set a target of January 31st, with possible pre-releases before then. brian. |
From: Reed H. <re...@ac...> - 2005-11-28 14:47:22
|
Toby Collett wrote: > - I dont think we have resolved the p2os driver command conflict between > usage for the arm device and usage for the position device. I'm not familiar with this problem, can you summarize? Reed |
From: Geoffrey B. <g....@au...> - 2005-11-28 19:52:32
|
Not much to summarise. See these messages in the archives: http://sourceforge.net/mailarchive/forum.php?thread_id=8865836&forum_id=7507 Geoff Reed Hedges wrote: > Toby Collett wrote: > >> - I dont think we have resolved the p2os driver command conflict between >> usage for the arm device and usage for the position device. > > > I'm not familiar with this problem, can you summarize? > > > Reed > -- Robotics research group, University of Auckland http://www.ece.auckland.ac.nz/~gbig005/ |
From: Brian G. <br...@ge...> - 2005-12-03 00:12:36
|
On Nov 27, 2005, at 5:41 AM, Toby Collett wrote: > > I just thought I would start a discussion re what needs done before a > release of player 2. Also it would probably be useful to just set a > date > and work to that otherwise it may just carry along as is for another 6 > months :) Sorry for my lack of response. I'm traveling at the moment. I'll get back to everybody with my TODO list and then we should, as Toby suggests, settle on a target release date. brian. |