all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
* Starting the Emacs 27 release cycle
@ 2019-12-23 16:05 Eli Zaretskii
  2019-12-23 16:17 ` Alan Mackenzie
                   ` (4 more replies)
  0 siblings, 5 replies; 10+ messages in thread
From: Eli Zaretskii @ 2019-12-23 16:05 UTC (permalink / raw)
  To: emacs-devel

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



^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: Starting the Emacs 27 release cycle
  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
                   ` (3 subsequent siblings)
  4 siblings, 0 replies; 10+ messages in thread
From: Alan Mackenzie @ 2019-12-23 16:17 UTC (permalink / raw)
  To: Eli Zaretskii; +Cc: emacs-devel

Hello, Eli.

On Mon, Dec 23, 2019 at 18:05:19 +0200, 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.

Thanks!

> 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

-- 
Alan Mackenzie (Nuremberg, Germany).



^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: Starting the Emacs 27 release cycle
  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
                   ` (2 subsequent siblings)
  4 siblings, 0 replies; 10+ messages in thread
From: Pankaj Jangid @ 2019-12-23 17:26 UTC (permalink / raw)
  To: Eli Zaretskii; +Cc: emacs-devel

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

Thanks a lot everyone. Thanks Eli. _/\_




^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: Starting the Emacs 27 release cycle
  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-31 11:59 ` Windows Snapshots Updated was " phillip.lord
  4 siblings, 0 replies; 10+ messages in thread
From: Eli Zaretskii @ 2019-12-23 20:05 UTC (permalink / raw)
  To: emacs-devel

> Date: Mon, 23 Dec 2019 18:05:19 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> 
> 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.

I see that people continue fixing bugs on master, disregarding what I
said above.  Please fix bugs on the release branch instead.  In
particular, documentation bugs should always be fixed on the release
branch as long as it is active.

Thanks.



^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: Starting the Emacs 27 release cycle
  2019-12-23 16:05 Starting the Emacs 27 release cycle Eli Zaretskii
                   ` (2 preceding siblings ...)
  2019-12-23 20:05 ` Eli Zaretskii
@ 2019-12-29 20:17 ` Robert Pluim
  2019-12-29 20:22   ` Eli Zaretskii
  2019-12-31 11:59 ` Windows Snapshots Updated was " phillip.lord
  4 siblings, 1 reply; 10+ messages in thread
From: Robert Pluim @ 2019-12-29 20:17 UTC (permalink / raw)
  To: Eli Zaretskii; +Cc: emacs-devel

>>>>> On Mon, 23 Dec 2019 18:05:19 +0200, Eli Zaretskii <eliz@gnu.org> said:

    Eli> I've created the emacs-27 release branch, and bumped Emacs version on
    Eli> master to 28.0.50.  A pretest of Emacs 27.1 will follow some time
    Eli> soon, I hope.

    Eli> Please from now on push safe bugfixes and documentation fixes to the
    Eli> release branch; all the other development should happen on master.
    Eli> When in doubt whether a bugfix is safe enough, please ask.

    Eli> CONTRIBUTE has more about working with master and the release branch,
    Eli> please review those practices.

    Eli> Please also checkout and build the release branch and use the version
    Eli> there to find potential bugs sooner rather than later.

Eli, unless you prefer otherwise, my pending changes for setting the
thread name and for allowing specifying the source address for UDP
connections will go to master, not emacs-27.

Iʼve just pushed the XFT colour font changes and the macos -nw crash
changes to the emacs-27 branch.

Robert



^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: Starting the Emacs 27 release cycle
  2019-12-29 20:17 ` Robert Pluim
@ 2019-12-29 20:22   ` Eli Zaretskii
  2019-12-29 21:25     ` Robert Pluim
  0 siblings, 1 reply; 10+ messages in thread
From: Eli Zaretskii @ 2019-12-29 20:22 UTC (permalink / raw)
  To: Robert Pluim; +Cc: emacs-devel

> From: Robert Pluim <rpluim@gmail.com>
> Cc: emacs-devel@gnu.org
> Date: Sun, 29 Dec 2019 21:17:31 +0100
> 
> Eli, unless you prefer otherwise, my pending changes for setting the
> thread name and for allowing specifying the source address for UDP
> connections will go to master, not emacs-27.

Thread name changes should go to emacs-27, as the Windows part is
already there (since before the branching).  The other one... I guess
it isn't too important, and could wait?  WDYT?

> Iʼve just pushed the XFT colour font changes and the macos -nw crash
> changes to the emacs-27 branch.

Thanks.



^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: Starting the Emacs 27 release cycle
  2019-12-29 20:22   ` Eli Zaretskii
@ 2019-12-29 21:25     ` Robert Pluim
  0 siblings, 0 replies; 10+ messages in thread
From: Robert Pluim @ 2019-12-29 21:25 UTC (permalink / raw)
  To: Eli Zaretskii; +Cc: emacs-devel

>>>>> On Sun, 29 Dec 2019 22:22:24 +0200, Eli Zaretskii <eliz@gnu.org> said:

    >> From: Robert Pluim <rpluim@gmail.com>
    >> Cc: emacs-devel@gnu.org
    >> Date: Sun, 29 Dec 2019 21:17:31 +0100
    >> 
    >> Eli, unless you prefer otherwise, my pending changes for setting the
    >> thread name and for allowing specifying the source address for UDP
    >> connections will go to master, not emacs-27.

    Eli> Thread name changes should go to emacs-27, as the Windows part is
    Eli> already there (since before the branching).  The other one... I guess
    Eli> it isn't too important, and could wait?  WDYT?

OK, Iʼll push those sometime this week to emacs-27 and master respectively.

Thanks

Robert



^ permalink raw reply	[flat|nested] 10+ messages in thread

* Windows Snapshots Updated was Re: Starting the Emacs 27 release cycle
  2019-12-23 16:05 Starting the Emacs 27 release cycle Eli Zaretskii
                   ` (3 preceding siblings ...)
  2019-12-29 20:17 ` Robert Pluim
@ 2019-12-31 11:59 ` phillip.lord
  2019-12-31 16:51   ` Drew Adams
  4 siblings, 1 reply; 10+ messages in thread
From: phillip.lord @ 2019-12-31 11:59 UTC (permalink / raw)
  To: Eli Zaretskii; +Cc: Emacs-devel, emacs-devel

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/




^ permalink raw reply	[flat|nested] 10+ messages in thread

* RE: Windows Snapshots Updated was Re: Starting the Emacs 27 release cycle
  2019-12-31 11:59 ` Windows Snapshots Updated was " phillip.lord
@ 2019-12-31 16:51   ` Drew Adams
  2019-12-31 17:05     ` Drew Adams
  0 siblings, 1 reply; 10+ messages in thread
From: Drew Adams @ 2019-12-31 16:51 UTC (permalink / raw)
  To: phillip.lord, Eli Zaretskii; +Cc: Emacs-devel, emacs-devel

> 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://urldefense.proofpoint.com/v2/url?u=https-
> 3A__alpha.gnu.org_gnu_emacs_pretest_windows_&d=DwICAg&c=RoP1YumCXCgaWHv
> lZYR8PZh8Bv7qIrMUB65eapI_JnE&r=kI3P6ljGv6CTHIKju0jqInF6AOwMCYRDQUmqX22r
> J98&m=wvCqS3-bhI5D1cBt1G0fH-
> G9UD8k1KxLl3UTYGcILnQ&s=cfo_l2ZVRssEkpy8XWOsA5cHzoxjbMng1X7UExb-k5o&e=

Thanks for this, Phillip.

There are 10 links there for the same build date.
And 10 other links for .sigs. And all are listed
together, with similar names.

Please consider adding a brief description/legend,
so it's easy to know what's what and which's which.

A description in your announcement mail (this one)
would help.  But also a description on that web
page would help.

Thanks.



^ permalink raw reply	[flat|nested] 10+ messages in thread

* RE: Windows Snapshots Updated was Re: Starting the Emacs 27 release cycle
  2019-12-31 16:51   ` Drew Adams
@ 2019-12-31 17:05     ` Drew Adams
  0 siblings, 0 replies; 10+ messages in thread
From: Drew Adams @ 2019-12-31 17:05 UTC (permalink / raw)
  To: phillip.lord, Eli Zaretskii; +Cc: Emacs-devel, emacs-devel

> There are 10 links there for the same build date.
                               ^^^^^^^^^^^^^^^^^^^
(Correction: They're not all from the same build
date, judging by the file-name differences.  They
all have the same upload date.)



^ permalink raw reply	[flat|nested] 10+ messages in thread

end of thread, other threads:[~2019-12-31 17:05 UTC | newest]

Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 ` Windows Snapshots Updated was " phillip.lord
2019-12-31 16:51   ` Drew Adams
2019-12-31 17:05     ` Drew Adams

Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.