Dear Helasz,
our plan is indeed to release time based, like a major series per year -
just release what is done and works in the given schedule.
However, for 7.0 mostly the changing mirror infrastructure (e.g. the
downfall
of some University servers) stalled the release process and in the
meantime trunk already developed much further.
In generally trunk works quite superb for many of us (at least we use
it for production anyway) - however, mostly daily busy-ness so far
prevented a binary release set.
Contributions and such feedback are always welcome,
René
On 13.01.2009, at 10:06, [email protected] wrote:
Happy New Year to All,
First of all I would like to acknowledge the great work of the T2
team has
done last year! Congratulations for your assidous voluntary work!
I am just wondering whether release schedules might be reviewed.
I am happy with trunk, however would it not be worth of dealing with
the
definite release of version 7.0 (solving udev issues) in the near
future?
I guess the packge updates take themselves a lot of time, but shifting
some of these updates would not cause much trouble I think.
Also version 8.0 release plan has several ambitious aims. I like that,
especially topics regarding the sophisticated dependecy handling.
However
I guess this schedule might need an update as well. The system is
aleady
robust enough, I would not mind if release plan would be shifted.
Best regards,
helasz
--
René Rebe - ExactCODE GmbH - Europe, Germany, Berlin
http://exactcode.de | http://t2-project.org | http://rene.rebe.name
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2
