public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: vim 7.2 is coming
Date: Wed, 25 Jun 2008 16:42:00 -0000	[thread overview]
Message-ID: <20080625164153.GV20180@calimero.vinschen.de> (raw)
In-Reply-To: <48626EC8.6080709@users.sourceforge.net>

On Jun 25 11:14, Yaakov (Cygwin Ports) wrote:
> Corinna Vinschen wrote:
> | vim 7.2a has just been released as the first beta version for the
> | upcoming vim 7.2.  I would like to upload the Cygwin release of vim 7.2
> | as soon as it's out.  How should we coordinate the concurrent release of
> | vim and gvim?
>
> How about:
>
> 1. You build vim 7.2 and put it somewhere;
> 2. I fetch it, build gvim 7.2 and do a quick test;
> 3. I'll make a RFU for gvim 7.2;
> 4. You move both vim and gvim 7.2 into release together.

Sounds like a good plan to me.

> When do you expect 7.2 to be final?

I have no idea.  7.2a is the first beta.  But vim is otherwise very
stable so I don't expect more than another beta.  If I might venture a
guess, I'd say, (much) less than 4 weeks.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

  reply	other threads:[~2008-06-25 16:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-25  9:48 Corinna Vinschen
2008-06-25 16:13 ` Yaakov (Cygwin Ports)
2008-06-25 16:42   ` Corinna Vinschen [this message]
2008-08-05  6:20     ` Yaakov (Cygwin Ports)
2008-08-07 10:45       ` Corinna Vinschen
2008-08-10  9:55     ` Corinna Vinschen
2008-08-10 10:28       ` Reini Urban
2008-08-11  5:06       ` Yaakov (Cygwin Ports)
2008-08-11  8:25         ` Corinna Vinschen

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=20080625164153.GV20180@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin-apps@cygwin.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).