On 29/11/2011 16:21, Christian Lohmaier wrote:
> Once again, this time also to bugzilla-ad...@apache.org - the problem
> remains, no working xmlrpc.
If you create an INFRA Jira ticket against the Bugzilla component this
won't get forgotten.
Mark
>
> On Tue, Nov 8, 2011 at 12:42 PM, Christian Lo
On 29/10/2011 20:39, TJ Frazier wrote:
> Hi, Mark, et al.,
>
> Please note the very strange date on this BZ message, which just came
> in. I would have expected today's date.
It is a known bug in Bugzilla [1] that should get fixed when we next
upgrade.
> There may be another small problem with t
On 14/10/2011 18:34, Dave Fisher wrote:
> Hi Mark,
>
> Thanks. I believe that the podling PPMC needs to make sure there are people
> who are able to be sysadmins.
Agreed. A quick glance at the lists below suggests that quite a few
additional admins are required.
Option 1:
Identify a few folks t
On 14/10/2011 17:15, Mark Thomas wrote:
> Folks,
>
> The infrastructure team has noticed that Bugzilla updates from the OOo
> instance are not being sent to any ASF mailing lists. AS part of the "if
> it didn't happen on the mailing list it didn't happen" t
Folks,
The infrastructure team has noticed that Bugzilla updates from the OOo
instance are not being sent to any ASF mailing lists. AS part of the "if
it didn't happen on the mailing list it didn't happen" this needs to be
rectified quickly.
The infrastructure team will therefore be adding the oo
Over the weekend, the ASF infra team noticed some e-mail from the ooo BZ
instance was bouncing. Specifically, e-mail to
iss...@www.openoffice.org. There also are 142 other
iss...@xxx.openoffice.org accounts.
The delivery failure may be a temporary issue but it highlights a two
tasks for the ooo po
Enjoy.
Any problems, please create an infrastructure Jira issue against the
Bugzilla component.
Mark
Just skimming through this thread in the archives.
I am not subscribed so ooo-dev so please don't assume I have read any of
the threads here. If there are issues, ask questions on the
infrastructure mailing list, comment on the existing Jira ticket for the
ooo-bz migration or create a new Jira tic
On 29/08/2011 15:48, Rob Weir wrote:
> On Fri, Aug 26, 2011 at 6:57 PM, Mark Thomas wrote:
>> As per [1], all user passwords (except those for ASF infra users with
>> system admin privs) have been reset to:
>>
>> password
>>
>> Assuming no show stopper issu
As per [1], all user passwords (except those for ASF infra users with
system admin privs) have been reset to:
password
Assuming no show stopper issues are reported on [1] before 23.59 UTC
Monday 29 August 2011 then ASF infra will work with Oracle to make the
existing bugzilla instance read only a
All,
The OOo Bugzilla data export provided to the ASF infrastructure team has
been imported into a test instance[1] for your review.
Please review the import and report any *show stopper* issues to the
infrastructure team via the Jira ticket created for this import. [2]
Assuming no show stopper
On 31/07/2011 23:46, TerryE wrote:
> On 31/07/11 23:09, Mark Thomas wrote:
>
>
>> I would imagine that these services would be hosted on project managed
>> virtual machines of some form and whoever manages them now would
>> continue to manage them. The central infra te
On 31/07/2011 21:59, Dennis E. Hamilton wrote:
> On ooo-dev, we continue to ponder how we can support the existing
> OpenOffice.org web site and the subdomains thereof with minimal friction and
> maximum preservation of the accumulated material. Here is a thumbnail of
> what the objectives are:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/07/2011 14:48, Rob Weir wrote:
> Bringing the threads together on the public list so we can (hopefully)
> quickly discuss.
>
> As I understand it now, the OpenOffice.org currently directs visitors
> to report vulnerability reports to securityt..
On 05/07/2011 18:07, Rob Weir wrote:
> On Tue, Jul 5, 2011 at 12:43 PM, Pedro F. Giffuni
> wrote:
>>
>> --- On Tue, 7/5/11, Rob Weir wrote:
>> ...
>>
>>>
>>> I'd like to explore the technical feasibility of migrating
>>> to JIRA.
>>>
>>
>> +1
>>
>>> I see this page here describing the migration
15 matches
Mail list logo