At least get a release 0.1 dry-run with code as-is out ASAP to flush out
release process issues. This would help to send out a message to the rest of
the world that MCF is an available product rather than purely
development/incubation.
Then come up with a list of issues that people strongly feel need to be
resolved before a true, squeaky-clean 1.0 release. Maybe that is the
original list of tasks, including better testing, but some review/decisions
are probably needed. That will be the ultimate target.
Then decide on a "close enough" subset of issues that would constitute what
people consider a "solid beta" and target that as a release 0.5 and focus on
that as the near-term target (after getting 0.1 out ASAP.) I personally do
not have any major issues on the top of my head that I would hold out as
"blockers" for a 0.5.
Or, get 0.1 out and then move on to a 0.2, etc. on a monthly/bi-monthly
basis as progress is made.
In short, get MCF as-is 0.1 out ASAP, have a very short list for MCF 0.5 to
get it out reasonably soon, and then revisit what 1.0 really means versus
0.6, etc.
-- Jack Krupansky
-----Original Message-----
From: Grant Ingersoll
Sent: Tuesday, November 09, 2010 8:38 AM
To: connectors-dev@incubator.apache.org
Subject: Release?
Now that we have NTLM figured out and the Memex stuff behind us, how do
people feel about working towards a release?
-Grant
