From: Syd Polk <spolk@redhat.com>
To: Berek <berek@usa.net>
Cc: sourcenav@sources.redhat.com
Subject: Re: Source navigator roadmap, features list, etc.?
Date: Tue, 26 Sep 2000 10:37:00 -0000 [thread overview]
Message-ID: <39D0DF9F.EB78FB38@redhat.com> (raw)
In-Reply-To: <002401c027df$68c47670$7113a8c0@concord.com>
The future is going to be dictated largely by the community. If a lot of people
in the community want something in, we will make it a priority for development.
Syd Polk
Engineering Manager
Berek wrote:
>
> I agree completely. I love SN, but it does have a lot of rough edges in the
> UI, and it's buggy. I, too, have a lot of suggestions and bug reports and
> would like to know what the future of SN is going to be
>
> ----- Original Message -----
> From: "Timothee Besset" <timo@qeradiant.com>
> To: <sourcenav@sources.redhat.com>
> Sent: Tuesday, September 26, 2000 01:00
> Subject: Source navigator roadmap, features list, etc.?
>
> > Is this list the only way to send feature suggestions and bug reports?
> > What are the actual plans of RedHat with source navigator, is it going
> > to evolve a lot more? Because I would have a truckload of improvement
> > suggestions and feature requests. It would be nice if there was a public
> > space somewhere that described who is doing what, maintaining what on
> > this project.
> >
> > I had to move from an MSDev environment to development under linux, and
> > Source Navigator does some things better than MSDev, but it also has
> > some big drawbacks.
> >
> > regards
> >
> > TTimo
> >
> >
next prev parent reply other threads:[~2000-09-26 10:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-25 22:04 Timothee Besset
2000-09-26 9:23 ` Syd Polk
2000-09-26 10:30 ` Berek
2000-09-26 10:37 ` Syd Polk [this message]
2000-09-27 21:41 ` Ben Elliston
2000-10-03 9:44 ` Mo DeJong
[not found] <William>
[not found] ` <Gacquer's>
[not found] ` <message>
[not found] ` <of>
[not found] ` <"Wed,>
[not found] ` <27>
[not found] ` <Sep>
[not found] ` <2000>
[not found] ` <10:12:49>
[not found] ` <+0200>
2000-09-27 1:12 ` William Gacquer
2000-09-27 22:16 ` Bruce Stephens
2000-09-28 9:15 ` Berek
2000-09-28 13:26 ` Syd Polk
2000-09-28 13:22 ` Syd Polk
2000-10-03 16:02 ` Mo DeJong
2000-10-04 10:25 ` Syd Polk
2000-09-28 0:23 dave.banham
2000-09-28 13:25 ` Syd Polk
2000-09-28 17:28 ` Ben Elliston
2000-09-29 6:06 ` Bruce Stephens
2000-09-29 0:26 dave.banham
2000-09-29 11:32 ` Syd Polk
2000-10-04 0:53 leonp
2000-10-04 2:42 ` Timothy M. Shead
2000-10-05 0:52 dave.banham
2000-10-05 1:16 William Gacquer
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=39D0DF9F.EB78FB38@redhat.com \
--to=spolk@redhat.com \
--cc=berek@usa.net \
--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).