unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
* Status of trunk
@ 2014-07-23  4:01 Bill Wohler
  2014-07-23  4:42 ` Glenn Morris
  0 siblings, 1 reply; 6+ messages in thread
From: Bill Wohler @ 2014-07-23  4:01 UTC (permalink / raw)
  To: emacs-devel

I apologize for missing the memo, but judging from the logs in the
emacs-24 and trunk branches, I'm guessing that the current policy is
that emacs-24 is used for 24.4 fixes, which are later merged to trunk by
Glenn, and that trunk is open for business.

Am I warm?

Also, we have a couple of MH-E bugs on SourceForge related to
compatibility with new nmh releases (1.5 and more recently 1.6). Would
these qualify for checking in on the emacs-24 branch?

Are we still targeting a winter release?

-- 
Bill Wohler <wohler@newt.com> aka <Bill.Wohler@nasa.gov>
http://www.newt.com/wohler/
GnuPG ID:610BD9AD




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

* Re: Status of trunk
  2014-07-23  4:01 Status of trunk Bill Wohler
@ 2014-07-23  4:42 ` Glenn Morris
  2014-07-23  4:53   ` Bill Wohler
  2014-08-09 17:11   ` Stefan Monnier
  0 siblings, 2 replies; 6+ messages in thread
From: Glenn Morris @ 2014-07-23  4:42 UTC (permalink / raw)
  To: Bill Wohler; +Cc: emacs-devel

Bill Wohler wrote:

> I'm guessing that the current policy is that emacs-24 is used for 24.4
> fixes,

Yes.

>  which are later merged to trunk by Glenn,

(By anyone who feels like it, but often no-one seems to feel like it.)

> and that trunk is open for business.

Yes.

> Also, we have a couple of MH-E bugs on SourceForge related to
> compatibility with new nmh releases (1.5 and more recently 1.6). Would
> these qualify for checking in on the emacs-24 branch?

Not up to me, but showing the diff (it is not huge) would help to answer that.

Technically speaking, no; ref:
http://lists.gnu.org/archive/html/emacs-devel/2014-05/msg00309.html

but if the changes are simple, probably yes. (But again, not up to me.)

> Are we still targeting a winter release?

Ha. There is no "target" AFAIK.

(Some people expressed a desire for more frequent releases, and I think
the phrase "every 6 months" was mentioned. The 24.4 feature freeze began
7 months ago...

There's no visible progress with any of the outstanding important bugs,
and no-one doing any serious documentation improvements.
Bug reports show that many people are using trunk rather than emacs-24.

So in summary I don't know when the release will be.
I hope it is a bit sooner than winter.)



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

* Re: Status of trunk
  2014-07-23  4:42 ` Glenn Morris
@ 2014-07-23  4:53   ` Bill Wohler
  2014-07-23  4:58     ` Glenn Morris
  2014-08-09 17:11   ` Stefan Monnier
  1 sibling, 1 reply; 6+ messages in thread
From: Bill Wohler @ 2014-07-23  4:53 UTC (permalink / raw)
  To: Glenn Morris; +Cc: emacs-devel

Glenn Morris <rgm@gnu.org> wrote:

> Bill Wohler wrote:
> 
> > I'm guessing that the current policy is that emacs-24 is used for 24.4
> > fixes,
> 
> Yes.
> 
> >  which are later merged to trunk by Glenn,
> 
> (By anyone who feels like it, but often no-one seems to feel like it.)
> 
> > and that trunk is open for business.
> 
> Yes.
>
> > Also, we have a couple of MH-E bugs on SourceForge related to
> > compatibility with new nmh releases (1.5 and more recently 1.6). Would
> > these qualify for checking in on the emacs-24 branch?
> 
> Not up to me, but showing the diff (it is not huge) would help to answer that.
> 
> Technically speaking, no; ref:
> http://lists.gnu.org/archive/html/emacs-devel/2014-05/msg00309.html
> 
> but if the changes are simple, probably yes. (But again, not up to me.)

Thanks, Glenn!

In that case, perhaps checking changes into trunk, submitting the patch
for review, and merging it into emacs-24 if accepted (so you don't need
to get involved :-) might be a good policy in the short term. Would you
agree?

> > Are we still targeting a winter release?
> 
> Ha. There is no "target" AFAIK.
> 
> (Some people expressed a desire for more frequent releases, and I think
> the phrase "every 6 months" was mentioned. The 24.4 feature freeze began
> 7 months ago...
> 
> There's no visible progress with any of the outstanding important bugs,
> and no-one doing any serious documentation improvements.
> Bug reports show that many people are using trunk rather than emacs-24.
> 
> So in summary I don't know when the release will be.
> I hope it is a bit sooner than winter.)

-- 
Bill Wohler <wohler@newt.com> aka <Bill.Wohler@nasa.gov>
http://www.newt.com/wohler/
GnuPG ID:610BD9AD



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

* Re: Status of trunk
  2014-07-23  4:53   ` Bill Wohler
@ 2014-07-23  4:58     ` Glenn Morris
  2014-07-23  5:45       ` Bill Wohler
  0 siblings, 1 reply; 6+ messages in thread
From: Glenn Morris @ 2014-07-23  4:58 UTC (permalink / raw)
  To: emacs-devel

Bill Wohler wrote:

> In that case, perhaps checking changes into trunk, submitting the patch
> for review, and merging it into emacs-24 if accepted (so you don't need
> to get involved :-) might be a good policy in the short term. Would you
> agree?

I appreciate the sentiment, but that's not a good way to do it.
It is better to make the changes in emacs-24 in the first place,
if that is where they are to go.

Just send the patch here and wait for Stefan (who currently has limited
email access) to ok/not ok it.



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

* Re: Status of trunk
  2014-07-23  4:58     ` Glenn Morris
@ 2014-07-23  5:45       ` Bill Wohler
  0 siblings, 0 replies; 6+ messages in thread
From: Bill Wohler @ 2014-07-23  5:45 UTC (permalink / raw)
  To: emacs-devel

Glenn Morris <rgm@gnu.org> writes:

> Bill Wohler wrote:
>
>> In that case, perhaps checking changes into trunk, submitting the patch
>> for review, and merging it into emacs-24 if accepted (so you don't need
>> to get involved :-) might be a good policy in the short term. Would you
>> agree?
>
> I appreciate the sentiment, but that's not a good way to do it.
> It is better to make the changes in emacs-24 in the first place,
> if that is where they are to go.
>
> Just send the patch here and wait for Stefan (who currently has limited
> email access) to ok/not ok it.

Yeah, I got *that* memo that Stefan is on walkabout. Will do, thanks!

-- 
Bill Wohler <wohler@newt.com> aka <Bill.Wohler@nasa.gov>
http://www.newt.com/wohler/
GnuPG ID:610BD9AD




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

* Re: Status of trunk
  2014-07-23  4:42 ` Glenn Morris
  2014-07-23  4:53   ` Bill Wohler
@ 2014-08-09 17:11   ` Stefan Monnier
  1 sibling, 0 replies; 6+ messages in thread
From: Stefan Monnier @ 2014-08-09 17:11 UTC (permalink / raw)
  To: Glenn Morris; +Cc: Bill Wohler, emacs-devel

> So in summary I don't know when the release will be.

Damn, and here I was, counting on you!

> I hope it is a bit sooner than winter.)

So do I.


        Stefan



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

end of thread, other threads:[~2014-08-09 17:11 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-07-23  4:01 Status of trunk Bill Wohler
2014-07-23  4:42 ` Glenn Morris
2014-07-23  4:53   ` Bill Wohler
2014-07-23  4:58     ` Glenn Morris
2014-07-23  5:45       ` Bill Wohler
2014-08-09 17:11   ` Stefan Monnier

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