unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: phillip.lord@russet.org.uk
To: Eli Zaretskii <eliz@gnu.org>
Cc: Emacs-devel
	<emacs-devel-bounces+phillip.lord=russet.org.uk@gnu.org>,
	emacs-devel@gnu.org
Subject: Windows Snapshots Updated was Re: Starting the Emacs 27 release cycle
Date: Tue, 31 Dec 2019 11:59:34 +0000	[thread overview]
Message-ID: <423dfe10b184723db1b513cf0fd60c4a@russet.org.uk> (raw)
In-Reply-To: <83zhfjvxhc.fsf@gnu.org>

On 2019-12-23 16:05, Eli Zaretskii wrote:
> I've created the emacs-27 release branch, and bumped Emacs version on
> master to 28.0.50.  A pretest of Emacs 27.1 will follow some time
> soon, I hope.
> 
> Please from now on push safe bugfixes and documentation fixes to the
> release branch; all the other development should happen on master.
> When in doubt whether a bugfix is safe enough, please ask.
> 
> CONTRIBUTE has more about working with master and the release branch,
> please review those practices.
> 
> Please also checkout and build the release branch and use the version
> there to find potential bugs sooner rather than later.
> 
> TIA


I have made some updated snapshots for Windows, both for Emacs-27 and 
Emacs-28.

I'll freeze the msys dependencies for Emacs-27 once the first pre-test 
comes out, after which they will remain frozen for the whole Emacs-27 
release cycle, so testing is welcome for the 27 branch especially.

https://alpha.gnu.org/gnu/emacs/pretest/windows/




  parent reply	other threads:[~2019-12-31 11:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-23 16:05 Starting the Emacs 27 release cycle Eli Zaretskii
2019-12-23 16:17 ` Alan Mackenzie
2019-12-23 17:26 ` Pankaj Jangid
2019-12-23 20:05 ` Eli Zaretskii
2019-12-29 20:17 ` Robert Pluim
2019-12-29 20:22   ` Eli Zaretskii
2019-12-29 21:25     ` Robert Pluim
2019-12-31 11:59 ` phillip.lord [this message]
2019-12-31 16:51   ` Windows Snapshots Updated was " Drew Adams
2019-12-31 17:05     ` Drew Adams

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=423dfe10b184723db1b513cf0fd60c4a@russet.org.uk \
    --to=phillip.lord@russet.org.uk \
    --cc=eliz@gnu.org \
    --cc=emacs-devel-bounces+phillip.lord=russet.org.uk@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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.savannah.gnu.org/cgit/emacs.git

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).