[TYPO3-dam-devel] status / progress - releaseplan

[Peter Kühn]

Hi yall!

at first: sorry for being quiet for a while :(
there was tons of work during the last weeks as every year before 
Christmas (i sent you an email off list on 7th of December to inform you 
about that, but it seems like it didn't reach you - we had some trouble 
with our mail server that time).

anyway: Christmastime is here, it gets quiet over the trees and i´ll 
make use of it to work on the dam again.

still my personal major goal is to restructure the extensions as 
suggested. (the first sv_ is already on my HD ;)

additionally ill dig deeper into http://bugs.typo3.org/view.php?id=5681 
to scratch michiels itch.

 > I'm all for a 'done when it's done' attitude.
dont think so... "software is never done - only released" ;)

 > Of course . . . if Peter still wants to make one . . .
 > that would be nice!
well - its pain in the ass but ill do...

cya l8er
pekue


Michiel Roos schrieb:
> Hi Georg,
> 
> Well . . . it's x-mess now . . . and it's not done yet (the dam I mean). 
> It's pretty quiet on the list too. I have done some updating of the 
> bugtacker and have closed one bug: http://bugs.typo3.org/view.php?id=5547
> 
> The one that makes DAM unusable for me now is the one with jumpUrl 
> javascript being rendered twice in the head 
> (http://bugs.typo3.org/view.php?id=5681).
> 
> I'm all for a 'done when it's done' attitude. I would like to set a 
> solid release date but am unable to predict upfront how many time I have 
> to work on the dam. I am also unable to predict how many time our peers 
> have to +1 fixed bugs or do other stuff (like work on the manual as was 
> proposed).
> 
> I'll gladly use a new years intention to finish the damn release and I 
> honestly think we are pretty close. There are a lot of dam related bugs 
> also in the tracker. It only just now occurred to me that I should react 
> to them with a message: 'please contact the dev of this extension to 
> help sort this out'. Will do so in a sec.
> 
> Although I really like the periodical reports Peter has been cooking up 
> lately, but I don't think that keeping on making those will save us. I 
> know all of this rfc stuff is new for most of us . . . but prepare 
> yourself for more rfc's as this project gets more exposure in the near 
> future (like after a release).
> 
> I feel it is the responsibility of the  RFC poster to keep track of how 
> many +1's he/she has already gotten. If he/she has not yet gotten 
> enough, he/she should make some noise. Furthermore it is the 
> responsibility of all of us to try and work on closing all of these bugs 
> asap, so if a RFC comes out . . . . please test and deny or approve the 
> fix proposed in the RFC.
> 
> The bugtracker show us exactly what bugs are still open an which ones 
> have been closed.
> 
> So jump right in! :-)
> 
> Of course . . . if Peter still wants to make one . . . that would be nice!
> 
> And now I need to fill some dades with blue cheese ;-)
> 
> Kindest regards, take it easy,
> 
> 
> Michiel Roos
>> Michiel,
>>
>> I know you got me right from the start and seeing everybody being 
>> extremely busy (with other stuff), let me suggest the following:
>>
>> - we announce a re-scheduled releaseplan with first RC/beta (was was 
>> planned) being released End January 08, and targetting End March 08 
>> (right before t3-board?) as final release-date (with already planned 
>> intermediary steps);
>>    = me feels we should show up with this announcement before x-mess! 
>> (as a little motivation for
>>
>> - we should use at least one of our christmas-whishes / 
>> new-years-intentions for "finish that DAMn release".
>>
>> - Michiel, ASA you'd find time, please issue another "Periodical 
>> Report", so we might jump in (wherever possible) and fill in the 
>> needed gaps.
>>
>> - we all spend time with and enjoy our families & friends meanwhile or 
>> in-between
>>
>> deal ?
>>
>> anyway, all the best to you / your families
>> n'joy the days,
>> regards georg
>> _______________________________________________
>> TYPO3-team-dam mailing list
>> TYPO3-team-dam at lists.netfielders.de
>> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-dam
>>