https://bz.apache.org/bugzilla/show_bug.cgi?id=55841

--- Comment #7 from Luca Toscano <toscano.l...@gmail.com> ---
Hi Filipus,

following up on your last message:

>  Calling this "misleading" is to put it mildly.

Would you mind to put an example of how the email message should look like to
not be "misleading"? Do you have a proposal to make a change in the email's
format? If so please add it to this bug so we'll be able to discuss it :)

> The fact that no comment "supports the issue", as you describe it, does not 
> make a ticket invalid. A ticket is only invalid if its claim is incorrect.

I'd like to clarify this point. I am trying to clear old bugs in the huge
(~1500) buglist of httpd and for this one I thought that the absence of
traction/support, together with the fact that I didn't really shared your point
of view, was an indicator that the email content wasn't misleading. This was my
bad since I should have probably added a comment with my thoughts before
closing the bug and marking it as invalid, lesson learned for the future and my
apologies :)

> I disagree about it being the "responsibility of who downloads/update the new 
> version of httpd to check the changelog for the new minor release (not 
> relying only on the email message)." Users should be able to trust email sent 
> by the foundation.

I agree with you partially. The emails from the foundation should be trusted
but it is indeed a best practice (at least in my opinion) for a
sysadmin/maintainer to check the Changelog to have a full and precise/complete
view of what will end up in production. 

Thanks!

Luca

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
For additional commands, e-mail: docs-h...@httpd.apache.org

Reply via email to