unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: ken manheimer <ken.manheimer@gmail.com>
Cc: Emacs Developers <emacs-devel@gnu.org>
Subject: Re: allout update checkin questions
Date: Thu, 19 Feb 2009 14:37:44 -0500	[thread overview]
Message-ID: <jwvhc2qrzpb.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <2cd46e7f0902191043s34a42f0eo617d7d039b97b52e@mail.gmail.com> (ken manheimer's message of "Thu, 19 Feb 2009 13:43:27 -0500")

> sorry, i was unclear.  i'm well acquainted with using CVS.

Great!

> What i'm clueless about are the emacs checkin and release protocols,
> and i have completely failed to find guidance docs.

There's nother written down.  But you asked at the right place (sorry
for not understanding at first).  Development of "future code" always
takes place on the CVS trunk.  At times, the trunk is not open for
random updates, this is the case right now for example because we're in
pretest, so only bug-fix should be installed on the trunk.  Later during
the pretest (probably not much before the actual release), we will
create a branch for the Emacs-23 release, at which point the trunk will
be open again for non-bugfix changes.

The intension of restricting the trunk to bugfixes and to try and focus
people on fixing bugs.

Note that we will likely switch over to Bzr around the time of the
release or around the time when we create the Emacs-23 release branch.


        Stefan




  parent reply	other threads:[~2009-02-19 19:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-19  1:17 allout update checkin questions ken manheimer
2009-02-19  2:58 ` Stefan Monnier
2009-02-19 18:43   ` ken manheimer
2009-02-19 18:58     ` ken manheimer
2009-02-19 21:39       ` Stefan Monnier
2009-02-19 19:37     ` Stefan Monnier [this message]
2009-02-19 18:57 ` Glenn Morris
2009-02-19 19:09   ` ken manheimer

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=jwvhc2qrzpb.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=ken.manheimer@gmail.com \
    /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).