From: Ian Roxborough <irox@redhat.com>
To: Reid Thompson <jreidthompson@yahoo.com>
Cc: sourcenav@sources.redhat.com
Subject: SN Status update [Was: where can I find current src]
Date: Tue, 25 Sep 2001 09:34:00 -0000 [thread overview]
Message-ID: <3BB0B50C.4B2B6F36@redhat.com> (raw)
In-Reply-To: <20010925132125.7911.qmail@web9607.mail.yahoo.com>
Reid Thompson wrote:
> can someone point me to a site/url that has current
> development src or binary development releases? Or
> is April the latest code?
Short story:- There is no development release.
Long story:- I managed to find time to do some bug
fixes (mainly annoying GUI problems) over the summer, and
would like to do another release some time over the next
few months. All work on Source-Navigator is voluntary, that
means I don't get paid for this. Also currently I'm the
only person/maintainer actively working on Source-Navigator.
Please don't relate any Source-Navigator development I do to
Red Hat (as some people point out, they don't care right now).
Red Hat is kind enough to provide the host sources.redhat.com
and bandwidth for Source-Navigator project (amongst many other
projects).
Some things I'm planning to do:
1) Put all the Source-Navigator (And Tcl/Tk/Itcl/Tix/etc.) code in
CVS on sources.redhat.com.
2) Beg for help, otherwise we will not see another Source-Navigator
release. I'm not joking, I can make source tar ball snapshots
easily enough, but I can't do a SN5.1 release without help
(testing being the main area I'd like help in). I don't have a
lot of time for this and I don't expect other people to contribute
more time than I will, even with help a doing a release will take
a while. More on this once I get SN into CVS.
3) Giving people CVS write access? would any body want it or use it?
4) Been a while since we had any T-shirts....
This is all one step at a time (and probably over a lot of time),
anyway nothing will happen unless I do step 1.
Thanks to all who have answered emails, reported, bugs, said nice
things, sent in patches, looked at code, downloaded SN, etc..
you have helped get us this far. :-)
Anyway, I'm letting you people know what is up in Source-Navigator
land, I'm not complaining about anything, I'm not whining at
people for not helping me. I enjoy working on SN, I just don't
have the time or the people I'd like to do work on it.
Thanks,
Ian.
next prev parent reply other threads:[~2001-09-25 9:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-25 6:21 where can I find current src Reid Thompson
2001-09-25 9:34 ` Ian Roxborough [this message]
2001-09-25 10:27 ` SN Status update [Was: where can I find current src] Berek Half-hand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3BB0B50C.4B2B6F36@redhat.com \
--to=irox@redhat.com \
--cc=jreidthompson@yahoo.com \
--cc=sourcenav@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).