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 / 2400
2399  |  2401
Subject: 
Re: Proposals, Bug Fixes, etc and tracking them with SourceForge
Newsgroups: 
lugnet.robotics.rcx.legos
Date: 
Mon, 25 Mar 2002 18:52:51 GMT
Highlighted: 
(details)
Viewed: 
1769 times
  

Here's my first cut at more detail.  Thanks to a couple of you for providing
some hint of your desired direction and for making my day by your showing of
interest.  I've more to add but you can get a feel for what I've been thinking
to date.  See:  http://legos.sourceforge.net/rlswork

This release is a product of all of our efforts so please tell me if you agree
or disagree with what I'm saying in the doc.

More tomorrow, *yawn*...

Regards,
Stephen

Stephen,

My SourceForge id is emanlove. And a few comments ...

- Although you say the idea of a distribution shape is minor, it might be
useful to start off using this so that we can be consistant from the
beginning.  And it sounds like a good idea.

- To help clarify the version labeling what type of structure are you
using/like to see.  You mention 0.2.5.x where x is the incremental test
release and I like this but I am unclear what the other . versions are.  For
example do we have

    major release.minor release.bug fix/patch.incremental test

or is it

    major realease.minor release.incremental cvs.incremental test

or something else? And what tools are the using gcc to bump up the
incremental build or using cvs to bump up a incremental check-in?

- All files, especially Makefiles, should have some sort of version
labeling in it.  I think this is important so that we can discuss and report
issues or bugs within any part of the code with clarity and not confussion.

- For windows release I have been using the cygwin (version b20) without
much issues.  These instructions used a tarball so there should be no
difference in the files, only in the instructions.  The two issues I would
bring up are

   1. Depending on how one sets up the path the dos commands might take
precednence of the cygwin tools.  This can be fixed by explicitly stating
the path for the cygwin tools as outline in my post "Attention cygwin and
windows users" Friday, March 08, 2002 4:05 PM.

   2. I would add some more information about unix drive systems (ie the
need for /home, /usr, and /tmp directories) and the mount command

- I have also reviewed pasts posts dating back to Jan 1, 2001.  For windows
users there have beeen a few comments. In particular a Max Bowsher added
some useful information (mostly during the time frame of July 2001) for
which I see two bits of information useful to be added to the next release.

   1. The remote patch needs to be fixed for windows users as outlined in
his post "Fix for remote patch" Saturday, July 21, 2001 1:12 PM.

   2. He also notes a makefile bug where the defien _win32 is missing.  See
"Makefile bug in legOS 0.2.5 for win32" Tuesday, July 10, 2001 4:48 PM.

These are about all that I see at this point.  And once again I don't have a
LEGO MindStorm yet so I can only see compilation errors and not
implementation errors.

Ed



Message is in Reply To:
  Re: Proposals, Bug Fixes, etc and tracking them with SourceForge
 
(...) Here's my first cut at more detail. Thanks to a couple of you for providing some hint of your desired direction and for making my day by your showing of interest. I've more to add but you can get a feel for what I've been thinking to date. (...) (23 years ago, 23-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