public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Mo DeJong <supermo@bayarea.net>
To: sourcenav@sources.redhat.com
Subject: Re: SourceNav release ...
Date: Sun, 06 Jan 2002 03:48:00 -0000	[thread overview]
Message-ID: <20020105195420.47a9e61c.supermo@bayarea.net> (raw)
In-Reply-To: <F39E5E57288ED311914C00508B5593D70346A2E7@es01-tlv.bmc.com>

On Sun, 6 Jan 2002 02:25:59 -0600 
"Simonovsky, Pavel" <Pavel_Simonovsky@bmc.com> wrote:

> 		So - you mean , that in fact SN is dead , and there is no
> any development team behind it? It is very important info - I suggested this
> tool to 2-3 teems in our company ... I have to warn them - that it dose no
> worth a waste of time...

Well, that might be a bit too strong. I don't speak for Red Hat, but as a former member of the development team I feel safe in stating that they are no longer allocating resources to SN. Basically, it comes down to $$. If you have paying customers then you can pay the engineers and managers. This might just be my impression, but it seemed that being able to download the code for free gave people the impression that they should not have to chip in for any new development. Also, the dot crunch did not help.

I know for a fact that Ian has been doing some great work on his own time to get the development version that uses Tcl/Tk 8.3 available via CVS. It is quite an improvement over the 5.0 release. That said, what is lacking is time and resources to put out a 5.1 release. What is the solution? I am not sure. I would like to hear ideas from people on this list. I would think the right solution would provide a stable 5.1 release, but also provide a plan for 5.2 and future releases.

cheers
Mo DeJong

  reply	other threads:[~2002-01-06 11:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-06  0:26 Simonovsky, Pavel
2002-01-06  3:48 ` Mo DeJong [this message]
2002-01-06  6:36   ` Ralf Corsepius
2002-01-07 12:04     ` Khamis Abuelkomboz
2002-01-07 13:11       ` Timothy M. Shead
2002-01-18 18:13         ` Mo DeJong
2002-01-07 13:22     ` Ian Roxborough
2002-01-07 13:34       ` Patches...[was: Re: SourceNav release ... ] Ian Roxborough
2002-01-10  4:34       ` SourceNav release Eray Ozkural (exa)
2002-01-11 14:34         ` Mo DeJong
2002-01-18 14:52           ` Eray Ozkural (exa)
2002-01-18 15:33             ` Mo DeJong
2002-01-18 15:58               ` Ian Roxborough
2002-01-24 10:14                 ` Eray Ozkural (exa)
2002-01-19  9:03               ` Eray Ozkural (exa)
2002-01-19  8:59             ` Khamis Abuelkomboz
  -- strict thread matches above, loose matches on Subject: below --
2002-01-04  2:56 Roman Levenstein
2002-01-04 15:48 ` Khamis Abuelkomboz
2002-01-03 14:30 klmcw yahoo
2002-01-03 15:08 ` Khamis Abuelkomboz

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=20020105195420.47a9e61c.supermo@bayarea.net \
    --to=supermo@bayarea.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).