all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dave Abrahams <dave@boostpro.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: cyd@gnu.org, emacs-devel@gnu.org
Subject: Re: Periodical releases
Date: Thu, 05 Jan 2012 08:41:02 -0500	[thread overview]
Message-ID: <m2lipmxo5t.fsf@boostpro.com> (raw)
In-Reply-To: <E1RinKN-0007xG-6L@fencepost.gnu.org> (Eli Zaretskii's message of "Thu, 05 Jan 2012 08:25:55 -0500")


on Thu Jan 05 2012, Eli Zaretskii <eliz-AT-gnu.org> wrote:

>> From: Dave Abrahams <dave@boostpro.com>
>> Date: Wed, 04 Jan 2012 22:36:24 -0500
>> Cc: emacs-devel@gnu.org
>> 
>> For what it's worth, Boost has no full-time people, and it releases four
>> times yearly.
>
> How tightly are the various libraries in Boost connected?  I.e., if
> one of them is broken, how many others will become broken as result?

Some are extremely loose and some have direct dependencies.  But one
thing we have had practically since the beginning is a fairly complete
set of regression tests.  Without that, I don't see how our pace of
releases would be possible.

> The "People" page of the Boost site shows 48 developers.  How
> intensely does each one of them work on Boost?  

I think Ohloh has the best information on this:
http://www.ohloh.net/p/boost

> For that matter, how many hours do you personally spend on Boost
> weekly, if I may ask?

I haven't had much time to do programming for Boost in the past few
years.  I'm not sure what the relevance is, though...

> I would be surprised if Emacs had more than 10 to 15 active
> maintainers at any given time.  I don't know how many hours others
> spend, but I can only devote about maybe 5 hours or less each week.

Arguably, the more people contributing code, the harder the job of
managing stable releases gets :-)

-- 
Dave Abrahams
BoostPro Computing
http://www.boostpro.com



  reply	other threads:[~2012-01-05 13:41 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-31 12:00 Periodical releases Carsten Mattner
2012-01-01 22:41 ` Stefan Monnier
2012-01-02 10:40   ` Carsten Mattner
2012-01-02 11:36     ` Eli Zaretskii
2012-01-02 12:57       ` Carsten Mattner
2012-01-02 17:31         ` Eli Zaretskii
2012-01-02 19:05         ` Drew Adams
2012-01-02 19:54           ` chad
2012-01-02 21:36             ` Carsten Mattner
2012-01-02 20:29           ` Eric Schulte
2012-01-02 21:31             ` Carsten Mattner
2012-01-02 20:41           ` Lluís
2012-01-02 21:23           ` Carsten Mattner
2012-01-02 22:14             ` Drew Adams
2012-01-02 22:27               ` Carsten Mattner
2012-01-05  2:34           ` Dave Abrahams
2012-01-05  2:58             ` Chong Yidong
2012-01-05  3:36               ` Dave Abrahams
2012-01-05  4:23                 ` Óscar Fuentes
2012-01-05 13:25                 ` Eli Zaretskii
2012-01-05 13:41                   ` Dave Abrahams [this message]
2012-01-05  9:31               ` Bastien
2012-01-05 10:11                 ` Leo
2012-01-05 11:31                   ` Carsten Mattner
2012-01-05 12:56                   ` Jambunathan K
2012-01-05 14:00                     ` Leo
2012-01-05 14:30                       ` Jambunathan K
2012-01-05 11:28                 ` Carsten Mattner
2012-01-05 14:18                   ` Eric Schulte
2012-01-05 11:33                 ` Carsten Mattner
2012-01-05  5:43             ` Eli Zaretskii
2012-01-05 12:20               ` Dave Abrahams
2012-01-05 15:34             ` Drew Adams
2012-01-03 22:23     ` Stefan Monnier
2012-01-03 18:18 ` What's in a feature? (was: Periodical releases) Bastien
2012-01-04  3:24   ` Stephen J. Turnbull
2012-01-04 10:03     ` What's in a feature? Bastien
2012-01-04 12:43       ` Juanma Barranquero

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=m2lipmxo5t.fsf@boostpro.com \
    --to=dave@boostpro.com \
    --cc=cyd@gnu.org \
    --cc=eliz@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 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.