You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by Rafal Krzewski <Ra...@e-point.pl> on 2001/04/02 23:19:56 UTC
[Proposal] Release plans? (was: ECS Usage Survey)
Magnus ?or Torfason wrote:
> Go ahead and deprecate the ECS classes, but I would very much like to see
> the release of Turbine support them (deprecated or not). The support could
> be dropped in Release 2, or whatever the next release after that would be
> called.
First, a little bit of background. The company I work for used Turbine
for
9 months now. It was used as a basis of our website/portal software code
named "u235". You can see it in action on http://www.pfm.pl and
http://www.wbksa.pl
(both sites are in Polish, have fun :-)). Some time ago it was decited
that we
will use Turbine for developing the second generation of our intranet
software
called OneWeb (http://www.oneweb.pl also in Polish)
I'm sure that everyone agrees that this is a good idea. You need good
foundation
to build good software. The only problem, as you may have guessed, is
that this
foundation shifts, changes and evolves all the time. Of course all this
change
is for the better, but this makes the life a tiny bit harder for the
developers.
We need a release of Turbine to build our software upon it. We want to
make
this happen, and we budget and people to work hard on it.
The current sketch of the plane would look like that:
+-"2.2"--------------->
|
----"2.1-unreleased"---+--------------+-----------"HEAD"---->
|
+-"2.1"------------------------------>
May 1 June 1
1) We want a "stable" branch of the codebase to appear fairly quickly.
2) The rationale for creating the 2.1 branch is supporting the existing
application base
and downstream projects (Hi, Jetspeeders!) during the crafting of a
"real" release.
3) Before the 2.1 branch is created, code base should go throug at least
two weeks of
'cool down' period when only bugfixes are checked in.
3) During the following two months, we would like refactor the certain
core parts of Turbine
(I'll post our proposal of changes during the next two weeks, and
we'll discuss it)
4) The 2.2 branch should happen at the time when Turbine codebase meets
the requirements
we had set forth in OneWebNG papers. Why? Because e-point will
actively support this branch.
A person will be paid for follow the development of codebase trunk,
and backport any bugfixes
that will affect the branch, gather bug reports for users and fix
anything that will not require
breaking existing code.
5) The estimated duration of our active support to this branch would be
at least six months,
We expect that next major release of Turbine will happen during that
time. 2.2 branch will
should also become really solid by then, given all the testing and
feature freeze.
6) We should decide if TDK should be built on 'most recent stable' or
'HEAD'
7) We should create a comprehensive summary of all threads of
development that are going on now,
decide it we should continue with them or put them on hold and make
list of features that we
want to be present in '2.1' and '2.2' branches.
I understand that people will have strong opinions on the matters
presented above, but we
need to get the ball rolling. Turbine needs a release to gain wider
audience.
Please send your opintions, and proposals for feature lists for 2.1 and
2.2
Rafal
PS. I know that the timelines given above will be hard to keep... We
have our timelines
and it is our problem, if this release plan fails, we'll make our
snapshot on July 1
and live with it. Still we'll do our best to make the release happen,
because this will
benefit both us and the community.
--
Rafal Krzewski
Senior Internet Developer
mailto:Rafal.Krzewski@e-point.pl
+48 22 8534830 http://e-point.pl
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org