On Sat, Feb 7, 2009 at 3:13 PM, Kevin Kofler <kevin.kofler@xxxxxxxxx> wrote: > Scott Williams wrote: >> only security patches with no intent to update functionality or add >> hardware support for older versions. Updates would likely come in >> light monthly spurts, similar to EPEL's release cycle. > > Huh? Security updates pushed out only once a month? That doesn't sound like > a good plan at all! For users who care about security, that is certainly not going to be optimal. However, he did qualify that with "likely" and "similar to EPEL" But from a bootstrapping a project that might be reasonable starting point based on initial contributor interest. If there is not enough contributor interests to roll security updates faster than that... its by far better to set expectations accordingly at the beginning..and then as the project picks up steam, if it picks up steam, raise the expectation bar based on what the contributors can do. There is a fine line between setting expectations low enough to be achievable in the near term and setting long term goals that will require resources growth to achieve. If users don't like the timescales, then they won't use it. What matters most is that they don't over promise on what the repository will provide. -jef -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
