Another reason was, that we wanted to give the work from the Google
Summer of Code the possibility to be included into 1.6. In the last
weeks we had some very productive discussions on the mailinglist about
new features and changes to existing ones. In the end however, we are
already very much behind the original schedule planned when 1.5 was
released. We had/have several fixed feature lists, which were supposed
to be the featureset for 1.6 and which then were weakened by discussions
on the list or people proposing additional features that they would send
in code for. We had a similar situation in Mambo times and also some
time during 1.5 development and its called feature creep. This delays
release and overall development, which is why we looked at that
featurelist again and updated it. The main features of 1.6 have always
been ACL and finishing some of the stuff that has been laying around
since 1.5 (mainly making all extensions MVC).
The list had of course some more entries, like the nested categories
feature and the new core output. But in the end we tried to stay true to
those features that were in the first feature list for 1.6. This
especially means that we are not going to make big changes to
com_content and that we are not going to add in more completely new
components. As has been mentioned elsewhere before, 1.7 will feature a
complete overhaul of com_content where we properly can fit in
taxonomy/tags, multi-language content, versioning and all other features
that were discussed on the list. This provides these features the time
to properly mature and 1.6 can ship earlier. :-)
We have updated the feature list for 1.6 here:
http://docs.joomla.org/Joomla!_1.6_Development_Status
Now what does that mean for the 1.6 Beta 1 release? Some final decisions
have to be made on the ACL system, which should be made by all of us
until today in one week. After that, these decisions have to be
implemented into the trunk, as well as as many of the other features on
the list. This said, we are aiming for the Beta 1 release in two to
three weeks from today. We are depending on your help on this to make
this happen!
Hopefully this clears up some of the questionmarks about the current
development of 1.6. So lets get this baby rolling. :-)
Hannes for the 1.6 Release Team