manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Karl Wright <>
Subject Re: "Book release"
Date Fri, 13 May 2011 13:54:16 GMT
Before we even consider a 0.3 release, though, we need to shepherd the
0.2 release through the incubator.  The vote has been open on the
general@incubator.a.o list for some 10 days now, with one +1 vote.  We
need two more.  The incubator folks say they are looking for our
mentors to vote on the incubator list.  So please consider doing so!


On Wed, May 4, 2011 at 11:29 AM, Karl Wright <> wrote:
> I have no problem with a ManifoldCF 0.3-incubating release, and I
> agree that technically a book release has nothing to do with a
> software release.  But community building is a critical part of making
> a project successful, so it's clearly more linked that one would
> idealistically expect. ;-)
> Karl
> On Wed, May 4, 2011 at 10:40 AM, Grant Ingersoll <> wrote:
>> While I understand the dilemma you are in for the book very much, the two are independent
events (such is the life of an author).  My personal feeling is MCF is not a 1.0 release
yet and that we should just continue on w/ the next release being 0.3.  Moreover, a 1.0 release
typically means, in my opinion, some important things for a project:  1. maturity in the
development community, 2. That we are committing to those APIs for the 1.x line and will make
backward compatible changes.   Are we ready to do that?   My instinct also says a 1.0 release
is something that should be done by a graduated project and not an incubating one b/c it's
generally a policy that incubating projects don't do much PR, etc. and a 1.0 release should
be a big deal.  (I'm not sure what the ASF policy is on that stuff)
>> -Grant
>> On May 2, 2011, at 8:59 AM, Karl Wright wrote:
>>> Once the 0.2-incubating release goes out the door, I'd like to propose
>>> that the next release be considered a ManifoldCF in Action "book
>>> release".  Basically this will mean that we need a release that is
>>> consistent with the examples and explanations in the book, before the
>>> book actually is done.  0.2-incubating does not work for this purpose
>>> because half-a-dozen issues pertaining to the book were detected and
>>> corrected since that release was frozen.  There are still some open
>>> issues that should be addressed before the book release too is frozen.
>>> I'd like people's thoughts on (a) the wisdom of this strategy, and (b)
>>> what release number we should use for it.  My personal feeling is that
>>> it would be great if it was a 1.0-incubating release, but I'm
>>> comfortable with anything really.
>>> Karl

View raw message