public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Denis Vakatov <vakatov@ncbi.nlm.nih.gov>
Cc: insight@sourceware.cygnus.com
Subject: Re: Insight sub-releases?..
Date: Sun, 30 Jan 2000 20:54:00 -0000	[thread overview]
Message-ID: <38951543.5272798D@cygnus.com> (raw)
In-Reply-To: <3885256C.75B5A193@ncbi.nlm.nih.gov>

Denis Vakatov wrote:
> 
> Hi,
> 
> As the Insight releases are that far away from each other, and CVS
> snapshots can be buggy --
> 
> why dont you consider to issue sub-releases (lets say, once a month or
> two) as soon as the next
> relatively stable version is achieved?

Unfortunatly, doing ``mini'' releases will require resources (namely
someones time).  If someone has the time to build/test snapshots and
make them available then please do this.  One developer is already
making occasional cygwin insight builds available.

Within the insight group the focus is more on eliminating the problem of
snaphots that are ``far away from each other''.

	enjoy,
		Andrew

      reply	other threads:[~2000-01-30 20:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-18 18:53 Denis Vakatov
2000-01-30 20:54 ` Andrew Cagney [this message]

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=38951543.5272798D@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=insight@sourceware.cygnus.com \
    --cc=vakatov@ncbi.nlm.nih.gov \
    /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).