[Typo3-dev] TYPO3 version 4.0.0?

[Daniel Hinderink [TYPO3]]

> On Wed, 2004-04-21 at 09:32, Daniel Hinderink [TYPO3] wrote:
>> Good morning and welcome ot this fine thread :-)
> 
> "ot" or "to"? :-)
> 
>> So the idea of "official extensions" further down in this mail is very
>> natural to me. Also see the "Quality Development"-thread from last november
>> 14.th, which fits nicely with such a plan. I'd love to make progress on
>> this!
> 
> You have my full support!
> 
> 
>> 
>> I have nothing to say, but that i 100% support you on this. I find it
>> logical, a safe and realistic strategy and i believe to a certain extent,
>> that is already what we are doing.
>> That also means we have 2 pressing things on the agenda:
>> A. getting the extension review process up and running
> 
> It hurts my heart as well. And naturally I think "...then I will do
> it!". Does that sound like a good idea? No, it doesn't. So, the question
> is; what is really holding the concept of extension review back?

A. no push: there is no reason to get reviewed, if your extension shows up
anyway i the EM just like the reviewed ones
B. no pull: there is no attration to getting reviewed, since it is not
visible enough

Both would be solved with the projects/production division in the TER.

C. no time: the people who assigned to doing that, have been busy with other
things. May be the review process is too much work and we should have two
competing scales: 1. User ratings for all non-reviewed projects, 2. The
official reviews for the top ranks and the "official" ones.
 
>> B. making a more sophisticated EM and TER reflecting the hierarchy, which is
>> determined by the quality of reviewed extensions.
> 
> I would love to.
> Last night before I feel asleep I thought "yeah, daniel is right. Lets
> just look at it from above and publish 3.6.0 at some point when we all
> feel it is stable, then go and celebrate in Amsterdam 2 weeks from now".
> Now, the ironic thing is that this might sound like if you kind of
> suggest as "vital-for-3.6.0" feature which is some modifications to
> EM/TER all the while you are downplaying the urgency of other things.

No, I don't aim to cram this into some early release. I just wanted to point
out that it is one consquence of going for the official ext concept
(henceforth abreviated as OEC, a feast for economics buffs :-)

On implementation, my limited idea of the classes concerned with the EM and
the TER suggests, that making this multi-level improvement means to put some
more selector-menues in, with appropriate SQL-queries like SELECT * FROM
extkey WHERE review IS 1; but of course i did not really check how many
conditions there already are, so I leave it up to you to asses the
complexity and time-frame.

In fact if you did it now, we would have a problem with the book, so i
rather opt for doing it in a while :-) or doing it until friday :-)

> Was that your intension? I totally agree that TER/EM/KS is top-priority
> on my list but there ARE also other things which to me seems just as
> important to fix for a 3.6.0 release

Agreed.

> 
> (BTW: I have already implemented the setting of a version-span for
> extensions so you can specify that "this extensions works with
> 3.6.0RC2+" and people will not be able to download versions through EM
> which are not compatible with their combination of TYPO3/PHP versions.
> This has been a major problem generating lots of frustration).

Aaah, the secret feature police is watching you!
 
>>> 
>>> 4.0.0 - 4.1.0 - 4.2.0 (since the jump to v. 4 IS justified in my
>>> opinion).
>> 
>> I think it is close, but let's ask Karsten how far he got?
> 
> Yes, we don't have to settle this now.
> 
> I also wanted to say that in this case your opinion (representing the
> marketing compartment of TYPO3) regarding version numbers has a heigh
> weight. I don't have any important agenda to push through, just wanted
> to get some opinions. If you really insist on staying with "3.6.0" it's
> equally fine with me.

I want to make 4. A success and when i think of how much 3.3 to 3.5 brought
to TYPO3, we need some punch to make 4 look like a big improvement. DBAL and
may be DAM could do that for us (eaaaaaasily), but they have to deliver real
world functionality.
 
(cut out the road to Mandalay)


> Sounds fine.
> 
> So a conclusion could be:
> - We stay with 3.6.0 until we can reasonable promote the "dbal"
> extension to work with Oracle / Postgresql. Then we jump right up to
> 4.0.0

Good enough for me.

> - From then we increment according to progress based on a pattern like
> the one you defined above (not considering its details now).

Yeees,

> - Lets organize some conscious selection of extensions which are to be
> "official extensions"

See my last mail in the "Publish your reviews"-thread of Dec. 18.th 03. On
the now diseased metadev-list.

> - Lets understand the "project descriptions" as means of getting new
> "Official extensions" done in a structured way according to market
> needs.

And to foster technical discussion and a competition of ideas.
 
>>> And that might feed a comment from you on my idea of "Official
>>> extensions"?
>> 
>> I think we already have it, it just doesn't have that label.
>> 
>> Brave new world here we come,
> 
> You're the king, champ!
> (seeing Daniel standing with his arms stretched to the side in the front
> of a large trans-atlantic steamer...)

As long as i don't have to listen to that dreadful soundtrack and get a
better female co-star than Kate Winslet, I will stand whereever it helps.
Right now i am sitting with René and Werner to finish the book, so even
standing with Kate is an improvement for me :-)
 
> have a nice day!

And you,

Daniel

> 
> 
> 
> - kasper
> 
> 
> _______________________________________________
> Typo3-dev mailing list
> Typo3-dev at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev
> 

-- 

Daniel Hinderink
TYPO3 - get.content.right
Innovation, Marketing, PR
http://www.typo3.com

-- 
Fashion is a form of ugliness so intolerable that we have to alter it every
six months.
Oscar Wilde