Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Releases
Date: 30 Dec 2000 22:15:35 +0100	[thread overview]
Message-ID: <m3pui9a9vs.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <vaf8zoxd6it.fsf@lucy.cs.uni-dortmund.de>

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> Create a patch of the differences between 5.8.7 and 5.9 and delete
> from this patch everything which deletes features, such as the s/mime
> stuff and so on.  Then, apply this patch to 5.8.7, giving 5.8.8.
> 
> What do you think about this?

Oy vey.  Sounds like work.   :-)

> Another thought is: right now, it seems that people haven't really
> added features to ognus like crazy.  So maybe the current ognus looks
> more like a bugfix release of 5.8?  So one idea would be to rechristen
> ognus as 5.8 and release that as 5.8.8.  But that would mean a lot of
> fiddling with the release/branch structure.  Hm.

Well, there's lots of GPG (and stuff) in ognus now, which probably
counts as new features...  

> Yet ANOTHER thought: release 5.8.7 again, only this time with
> mail-source-delete-incoming set to the right value :-)

That's definitely an idea.  :-)

> Are there serious bugs in 5.8.7?  I vaguely remember that I have
> told people to fetch a 5.8.8 snapshot quite a number of times, but I
> don't remember the details.  Gack.  I wish I did.  But there must
> have been a reason for me to do so.  Hm.

There were lotsa problems with 5.8.6, but (so far in my reading of
gnu.emacs.gnus), there doesn't seem to be any major problems with
5.8.7 (except `mail-source-delete-incoming').

> > And there was some talk about not doing any alpha releases any more,
> > but just keep that in cvs...
> 
> Hm.  That's an idea.  Hm.  I think it would be nice to keep the
> snapshots, though.  Maybe there are people out there for whom CVS is a
> real hassle but who would still like access to the development
> sources.  Maybe if you keep a week's worth of daily snapshots?

One reason for not doing alpha releases is that (as we saw during
Pterodactyl), more people used the alpha releases than probably should 
have.  I mean, they're supposed to be very unstable.

One reason for doing alpha releases is that it's very nice to have
names for development.  One can easily say "This problem cropped up
when I upgraded from ognus-0.45 for ognus-0.49", while it's a bit more 
difficult saying "I had a cvs version, and then I did "cvs up" a
couple of days ago, and this problem cropped up"...

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen



  reply	other threads:[~2000-12-30 21:15 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-30 18:58 Releases Lars Magne Ingebrigtsen
2000-12-30 19:37 ` Releases ShengHuo ZHU
2000-12-30 21:09   ` Releases Lars Magne Ingebrigtsen
2000-12-30 21:59     ` Releases ShengHuo ZHU
2000-12-30 22:22       ` Releases Lars Magne Ingebrigtsen
2001-01-04  3:54         ` Releases ShengHuo ZHU
2001-01-04  5:22           ` Releases Lars Magne Ingebrigtsen
2001-01-04 11:48             ` Releases Karl Kleinpaste
2001-01-04 14:33               ` Releases Lars Magne Ingebrigtsen
2001-01-04 16:33               ` Releases Stainless Steel Rat
2000-12-30 21:40   ` Releases Randal L. Schwartz
2000-12-30 22:25     ` Releases Lars Magne Ingebrigtsen
2001-01-02 13:04     ` Releases Charles Sebold
2000-12-30 19:59 ` Releases Kai Großjohann
2000-12-30 21:15   ` Lars Magne Ingebrigtsen [this message]
2000-12-30 21:50     ` Releases ShengHuo ZHU
2000-12-30 22:24       ` Releases Lars Magne Ingebrigtsen
2000-12-30 21:43   ` Releases Randal L. Schwartz
2000-12-31 17:10     ` Releases ShengHuo ZHU
2001-01-01 10:37       ` Releases Anders Odberg
2001-01-01 16:59         ` Releases Randal L. Schwartz
2001-01-04  5:11           ` Releases ShengHuo ZHU
2001-01-04 19:17             ` Releases Randal L. Schwartz

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=m3pui9a9vs.fsf@quimbies.gnus.org \
    --to=larsi@gnus.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.
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).