"Colin Chalmers" <[EMAIL PROTECTED]> writes:
>I also think you mentioned a preference for releasing more often, what would
>be the time frame for 2.3? 3 months?
I discussed with Martin off-mailing list (as we have the same mother
tongue, it is sometimes simpler to discuss things in german. :-) ) to
maybe put out a bugfix-release to our current releases (which is 2.2)
all four to eight weeks but without a fixed time frame. We haven't
agreed on a real time window (and a naming scheme :-) ) yet, because
we might want to discuss it here.
I'd personally go for 2.2p1, 2.2p2, 2.2p3 do make clear that these
releases are really bug fixed Turbine 2.2 versions but Martin did tell
me that he prefers 2.2.1, 2.2.2, 2.2.3 and so on. As he does the
releases, it is his call, I think.
These releases should aim for maximum compatibility for 2.2 as we want
to try to (re-)build an active user base starting with this release.
2.3 might introduce some user space visible changes (see my other
mail) so at least I don't intend it as a direct replacement for
Turbine 2.2 (just like 2.2 wasn't a direct replacement for 2.1).
I'd personally consider the following short time release map:
earliest latest release
mid Jan'03 end Jan'03 turbine-2.2.1 - first bugfix release of T2.2
Mar'03 mid Mar'03 turbine-2.2.2 - second bugfix release of T2.2
Feb'03 mid Feb'03 turbine-2.3-alpha1 first alpha release of
next turbine version
Mar'03 mid Mar'03 turbine-2.3-beta1 first beta release of
next turbine version
Apr'03 mid Apr'03 turbine-2.3 next turbine release
and at least one, possible two more releases of turbine-2.2.x after that.
Yes, I do want to speed up development here.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH [EMAIL PROTECTED]
Am Schwabachgrund 22 Fon.: 09131 / 50654-0 [EMAIL PROTECTED]
D-91054 Buckenhof Fax.: 09131 / 50654-20
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
