zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: Zsh Workers <zsh-workers@sunsite.dk>
Subject: Re: Status of 4.1.x branch?
Date: Fri, 14 Nov 2003 13:13:04 +0000	[thread overview]
Message-ID: <25893.1068815584@csr.com> (raw)
In-Reply-To: "Oliver Kiddle"'s message of "Fri, 14 Nov 2003 13:57:48 +0100." <22640.1068814668@gmcs3.local>

Oliver Kiddle wrote:
> I've gone through the patches I listed in 18976 and applied those which
> were relevant.

Thanks.

> So that leaves changes since 18976. You might want to check users/6493,

The first one ought to be applicable.  I asked for something more
configurable for the second bit but didn't get it.

> some of 19168

We should probably fix the ztrtfime problem

> 19167

Fixes BRACE_CCL with NULLs, should be simple enough

> and perhaps 19105.

Confusion about job control and terminal output.  Hmm... the fix was
short enough but the overall effect wasn't totally obvious.  Still,
nobody's complained.

> Would be good to get a 4.0.8 out and be done with the 4.0 branch. I'm
> not going to do any more searching through Changelogs but there probably
> isn't much left that I've missed anyway.

I would plan to make 4.0.8 and 4.1.2 more or less at the same time,
announcing that the former is expected to be the last release on that
line, and the latter is expected to turn into 4.2.0 with some more
testing.  It was reasonably painless last time.  I don't think either
desperately needs test versions releasing.

After that, 4.1 can turn into pre-release versions of 4.2.

After that, we can stick with 4.2 until we really need to branch.  This
is partly because Oliver keeps getting me on the subject, but actually
he's right that there's no real need to keep a completely separate
development branch at the moment.

If we need to do something quite involved, it would be worth considering
doing it on a private branch rather than create a completely new
development branch --- there just aren't enough of us working on zsh to
make it efficient.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK                          Tel: +44 (0)1223 692070


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************


  reply	other threads:[~2003-11-14 13:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-11 21:30 Danek Duvall
2003-11-12  1:38 ` Mads Martin Joergensen
2003-11-12 10:32 ` Peter Stephenson
2003-11-14 12:57   ` Oliver Kiddle
2003-11-14 13:13     ` Peter Stephenson [this message]
2003-11-19 10:07 ` Ollivier Robert

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=25893.1068815584@csr.com \
    --to=pws@csr.com \
    --cc=zsh-workers@sunsite.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).