Hi guys,
as far as I can see there are two major points in this discussion:
1. Providing updates for single components in short time frames could
bring people to an update hell, when they need to download and upgrade
some components every week.
2. The clear target of Zeta to provide components as loosely coupled as
possible would be lead ad absurdum by only providing full package upgrades.
I agree with both points somehow and for these reasons we basically ran
the double tracked release process in eZ Components:
a) Single component upgrades were only distributed through our PEAR channel
b) A full package release was shipped at defined time points, containing
all stable components
If you as a user / admin use PEAR for your Zeta installation, frequent
updates are fine, since you just need to do
$ pear upgrade-all -c ezc
and get all updates in place.
If you don't want to rely on PEAR, you basically upgraded every half year.
I don't think we should go away from this process, since it basically
solves the needs of both parties.
However, I see the argument for not having automatic releases of the
full package whenever a component is upgraded. This would lead the
argument for the full package ad absurdum.
Is that convenient for everyone?
Regards,
Toby
--
Tobias Schlitt http://schlitt.info GPG Key: 0xC462BC14
Want to hire me? Need quality assurance? http://qafoo.com
eZ Components are Zeta Components now! http://bit.ly/9S7zbn
