Hi all,

It seems we will finally be ready with Chamilo 1.8.8 tomorrow 3/5.
Apparently (made a quick check*) this version includes more than 250
tasks (249 on the public support site + many small private development
projects) which were closed between the 31st of July 2010 and now
(around 9 months afterwards). That's also more than 2200 commits*
(which, granted, doesn't mean anything but maybe that can give us a
little admiration for the non-already-chamilo-developers out there).

I know there's a majority of 2.0 developers here, but we always welcome
feedback from any source, positive or negative.

You can test Chamilo 1.8.8 on http://chamilodev.beeznest.com with
account admin/admin.

If nothing stops us (major issue or security flaw), we will release it
during the night and announce it in the early hours of the morning on
Wednesday 4/5.

As a side note, tomorrow will also be the day where we execute the first
cleanup of the Chamilo campus. Apparently there are over 2700 courses
that haven't been used in the last 6 months. With the non-optimal
content duplication we have in 1.8 and the default course content
amounting to 9.2M per course, this gives around 30GB of space used just
for trash trials. The free campus is using around 120GB of disk space
right now (and is pretty much starting to be a pain to manage on that
server, which hasn't been designed for such a space-hungry usage).

Regards,

Yannick


PS: Measuring the number of tasks 1.8.8: always set your tasks into a
specific version, on support.chamilo.org, even if it happens at the
moment of closing the task. Then use support.chamilo.org, roadmap tab,
and look at the different versions (alpha, beta, RC, stable) and sum up
the numbers

PS2: Measuring the number of commits between two releases (to be
improved): always tag your versions. Mercurial gives a commit number to
each tag. Look at the difference between tags of two stable versions.


_______________________________________________
Dev mailing list
Dev@lists.chamilo.org
http://lists.chamilo.org/listinfo/dev

Reply via email to