On Mon, 2013-07-08 at 14:37 -0400, John Arthorne wrote: > [...] we currently think the 1+2 rhythm currently works well for the > Platform project, [...]
Being an occasional contributor, I can't disagree more. There is a yearly gap between providing a patch and getting it released. It means that some projects (like CDT) will ship without a fix for an annoying issue (and at least one Fedora will be shipped with a bug). For me it is a wasted time, because the patch could have been verified in the field (if commiters hadn't had time). And corrected if necessary. With CBI, it is easy to do an in-house build on demand. This is an opportunity (inhouse bugfixes may be contributed back) and a threat(it is easier respin builds than contribute a fix) at the same time. Not to mention that waiting a year to get a patch released is *extremely* demotivating. It is almost a show stopper. Eclipse needs contributors. I consider "frequent releases" to be a prerequisite to "being open for contributors". -- Krzysztof Daniel <kdan...@redhat.com> Red Hat _______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
