OK.

On the wiki page change the bugzilla search to 
https://issues.apache.org/ooo/buglist.cgi?namedcmd=Resolved341ReleaseBlocker

No login required.


On Jan 14, 2013, at 1:24 PM, Rob Weir wrote:

> On Mon, Jan 14, 2013 at 4:18 PM, Pedro Giffuni <p...@apache.org> wrote:
>> Hmm...  could be used for spamming.
>> 
>> Maybe it's policy after all.
>> 
> 
> There are some saved queries and reports that are quite expensive,
> computationally.  Cross-tabulations, etc., and they take several
> seconds for me to run them.  So perhaps they want to avoid a DoS
> attack based on a trivial wget of an expensive query URL?
> 
> -Rob
> 
>> cheers,
>> 
>> Pedro.
>> 
>> 
>>> ________________________________
>>> Da: janI <j...@apache.org>
>>> A: dev@openoffice.apache.org; Pedro Giffuni <p...@apache.org>
>>> Inviato: Lunedì 14 Gennaio 2013 16:10
>>> Oggetto: Re: Bug list in release notes: why bugzilla account needed?
>>> 
>>> 
>>> Easy solution.
>>> 
>>> make an account "anonymous" with a easy password, and publish that...nearly 
>>> as good as not needing to login.
>>> 
>>> rgds
>>> Jan I.
>>> 
>>> 
>>> On 14 January 2013 21:57, Pedro Giffuni <p...@apache.org> wrote:
>>> 
>>> 
>>>> 
>>>> Hi Hagar;
>>>> 
>>>> It's not a policy, it's simply the way bugzilla works.
>>>> 
>>>> A developer (hi hdu@ :) recently wrote a nice script that crosschecks 
>>>> bugzilla
>>>> issues with commits so the situation will improve greatly in the near 
>>>> future.
>>>> 
>>>> Pedro.
>>>> 
>>>> 
>>>> 
>>>>> ________________________________
>>>>> Da: Hagar Delest <hagar.del...@laposte.net>
>>>>> A: dev@openoffice.apache.org
>>>>> Inviato: Lunedì 14 Gennaio 2013 15:42
>>>>> Oggetto: Bug list in release notes: why bugzilla account needed?
>>>> 
>>>>> 
>>>>> Here is a message on the forum about the necessity to have a login to 
>>>>> view the list of the bug fixes:
>>>>> http://forum.openoffice.org/en/forum/viewtopic.php?f=50&t=58749
>>>>> 
>>>>> Indeed, why is it mandatory to have an account to view the bug list?
>>>>> This is not user-friendly.
>>>>> 
>>>>> Can the policy be changed?
>>>>> 
>>>>> Hagar
>>>>> 
>>>>> 
>>>>> 
>>> 
>>> 
>>> 

Reply via email to