Issue 52 - cvs mailing lists do not work
Summary: cvs mailing lists do not work
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Mailing lists (show other issues)
Version: current
Hardware: Sun Solaris
: P3 Trivial (vote)
Target Milestone: ---
Assignee: Unknown
QA Contact: issues@www
URL:
Keywords:
: 51 (view as issue list)
Depends on:
Blocks:
 
Reported: 2000-10-25 10:37 UTC by sander_traveling
Modified: 2003-12-06 14:52 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description sander_traveling 2000-10-25 10:37:34 UTC
the cvs mailing lists are not working or exteremly lagged.

How to repeat:
	a) make a change in you local checked out sources
	b) commit the change
	c) try waiting for the commit message to show up on the lists
Comment 1 sander_traveling 2000-10-25 10:40:53 UTC
*** Issue 51 has been marked as a duplicate of this issue. ***
Comment 2 Unknown 2000-10-25 20:30:22 UTC
Sander -- are you by any chance looking at the CVS mailing lists via the
web archive? 

If you are noting delay in the cvs web archives, it may be due to our caching
proxy server, which we're using to handle the extraordinarily large "spikes" in
web-hits we're seeing each time a major press/zdnet/slashdot article about 
oo.org comes out. The caching proxy formerly automatically updated the cache
of the website it keeps every six hours, but we have changed that time to
1 hour after we got a number of bug reports related to this issue:

http://www.openoffice.org/issues/show_bug.cgi?id=54
http://www.openoffice.org/issues/show_bug.cgi?id=53

If you want to see the latest and most up-to-date mail list archives, you
can hit "shift-reload" in your browser and that will force the cache to update
for the particular URL you're visiting. If that URL happens to be the mhonarc
archive index page of a CVS mailing list, then it will update. Alternately,
you can wait up to an hour and then re-visit or re-load and the last hours 
updates should be visible.

If you are noting delays in the actual mailing lists, please be specific as
to which exact lists, and perhaps attach an example of the delayed mail message
(complete w/ headers). I have not noted any delays in actual  CVS mail lists,
and even if there are no delays withing openoffice.org, delays and asynchrony
may arise from a number of other areas:
	(1) if lots of people are doing commits or there's a flurry of messages
	on discuss, your commit messages may go into a queue and will get 	        
delivered when it's their "turn".
	(2) there may be a host of delays in SMTP delivery between oo.org
	and sander.vesik@ireland.sun.com over which we have no control.

Sending an example of a complete message, complete with "delivered" headers
and all the "noise" above the subject line, will help us determine the problem.

Since your initial report was not specific enough to provide me with 
further information, and i cannot further see any problems with the cvs
mail delivery, I'm going to resolve this issue as "worksforme"

If you have further problems, please reopen the issue with a detailed
description of the specific mail lists, urls, etc you are having problems with.
(you can use the URL field above to refer to a mailing list, e.g.
"mailto:cvs@<project>.oo.org" 
Comment 3 michael.bemmer 2003-03-13 09:46:06 UTC
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for
details. First step in IssueZilla is unfortunately to set them to verified.
Comment 4 michael.bemmer 2003-03-13 10:20:57 UTC
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details. 
Comment 5 michael.bemmer 2003-03-13 10:29:17 UTC
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details.