Justin Erenkrantz wrote:
On 4/24/06, Colm MacCarthaigh <[EMAIL PROTECTED]> wrote:
Tbh, I'm -0.5 on this. It's complex enough as it is trying to get
releases out, and 1.3 hasn't even tagged yet.
My concern is that issuing three announcements in the span of one week
is *very* confusing to our users. Either 2.0 and 1.3 get bundled with
the 2.2 announcement, or we shouldn't announce those releases at all.
I don't think this is *as confusing* as the week we announce, say, just 2.0.
They at least will see them all. Five weeks from now, when only an announce
from 2.0 is pushed out, that will be more confusing.
What I'd like to propose is 1) wait for the unified announce on Wed night,
2) cease pushing out any 1.3 or 2.0 specific product announcements.
Vote and promote a release for 1.3 or 2.0 into dist/httpd and update the 2.2
announce file at that time (without broadcast). When the next mainstream
release (hopefully very shortly after) is ready to roll, the user will be
notified that updated 1.3 and 2.0 legacy releases are available.
