To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.robotics.rcx.legosOpen lugnet.robotics.rcx.legos in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / RCX / legOS / 2404
2403  |  2405
Subject: 
Re: Proposals, Bug Fixes, etc and tracking them with SourceForge
Newsgroups: 
lugnet.robotics.rcx.legos
Date: 
Tue, 26 Mar 2002 00:20:00 GMT
Viewed: 
1833 times
  
I'd say prepare them and file them as patches as you did with
mux1 (against a fresh 0.2.5).  This will give us time to listen
for comments.  And it gives time for others to play with and review
your changes.  From a work-effort perspective, if we are to merge
any patches having a couple more is not significantly more work
(if your work is like your last, concise and functional.:)


Sounds good to me, I'll fix them up and put them in as patches.  As far as
keeping things small they will be able to be excluded at compile time, much
like everything else in LegOS.  It is probably also a good idea to have all 3rd
party sensors compiled out by default.

On another note I think we should start taking advantage of the tracking tools
offered by sourceforge.  This should help us keep track of what needs to be
done.  I've already opened a couple of support issues for feature requests.

mark



Message is in Reply To:
  Re: Proposals, Bug Fixes, etc and tracking them with SourceForge
 
(...) Thanks for reading it. (...) I'll need time to play with this. It seems to me this is not the first time this has been mentioned in this news group. Has anybody thought of using the downloader as a means for setting the RCX id? Seems to me it (...) (23 years ago, 25-Mar-02, to lugnet.robotics.rcx.legos)

22 Messages in This Thread:










Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR