You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Antonio Gallardo <ag...@agssa.net> on 2006/03/28 18:02:13 UTC
Make bugzilla for cocoon read only. (was: Re: DO NOT REPLY [Bug 39127]
New: - [link] DIYTrade.com ...)
Dear infra,
Is posible to close bugzilla for cocoon? We now use JIRA.
Many thanks in advance.
Best Regards,
Antonio Gallardo.
bugzilla@apache.org escribió:
> DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
> RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
> <http://issues.apache.org/bugzilla/show_bug.cgi?id=39127>.
> ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
> INSERTED IN THE BUG DATABASE.
>
> http://issues.apache.org/bugzilla/show_bug.cgi?id=39127
>
> Summary: [link] DIYTrade.com -B2B directory with over 300,000
> suppliers. Help global buyers sourcing easily.
> Product: Cocoon 1
> Version: 1.8.3-dev
> Platform: Other
> URL: http://www.diytrade.com
> OS/Version: Linux
> Status: NEW
> Severity: normal
> Priority: P2
> Component: Documentation
> AssignedTo: dev@cocoon.apache.org
> ReportedBy: jeffrey@diysite.com
>
>
> Please put our link in your live site list.
> URL of the website: www.diytrade.com
> Title of the website: DIYTrade.com
> Cocoon version used: 2.1.7
>
> Short summary: B2B directory with over 300,000 suppliers. Help global buyers
> sourcing easily.
>
> How can we verify this site is actually built with Cocoon?
> Open the link http://www.diytrade.com/diyep/dir/showversion
> it will show the exception message, it is a cocoon
> org.apache.cocoon.ResourceNotFoundException.
>
>
> The following questions are optional:
>
> - How much time did it take to build the site from design to publication?
> more than 1 years
> - How much traffic does the site handle?
> around 15 Mb
>
> - What made you choose Cocoon to build the site?
> XML and XSLT capability , sitemap pipline mathed our requirment
>
> - What other information do you want to disclose (e.g. how does it work, how
> did
> you build it, what parts of Cocoon did you use)?
>
> The DIYTrade B2B marketplace is build upon cocoon.
> XML and XSL function provided a poweverful and clear serperation between design
> the programming.
> We plan to provide different web site delivery by different Generator
> It is the third products we build upond cocoon platform, 1.diysite.com 2.
> ebigchina.com 3.diytrade.com
> - Can you provide a contact email address if people want further information?
> Jeffrey Yuen
> R&D Manager
> jeffrey@diysite.com
>
>
Re: Make bugzilla for cocoon read only.
Posted by Antonio Gallardo <an...@apache.org>.
I cross checked and now is disabled:
http://issues.apache.org/bugzilla/enter_bug.cgi?product=Cocoon+1
http://issues.apache.org/bugzilla/enter_bug.cgi?product=Cocoon+2
Thanks for your support!
Best Regards,
Antonio Gallardo.
Yoav Shapira escribió:
> Hi,
> I just set Cocoon 1 to "closed for bug entry" status. Cocoon 2 was
> already set that way. I also verified that the "New Issue" dialog in
> Bugzilla doesn't allow either Cocoon 1 or Cocoon 2 as the product for
> a new issue. All set?
>
> Yoav
>
> On 3/28/06, Sander Temme <sa...@temme.net> wrote:
>
>> On Tue, March 28, 2006 8:30 am, Antonio Gallardo said:
>>
>>
>>> I am not aware about the internal configuration in the ASF. I see we
>>> currently use bugzilla 2.18.5. In our company, we use bugzilla 2.20.1.
>>> in the "product" form there is a checkbox called: "Closed for bug entry:
>>> ". Bugzilla 2.20.1 has also other benefits as RSS feeds and so on. The
>>> upgrade is pretty straight forward.
>>>
>>> WDYT?
>>>
>> It's on my list, but not very high. We are on the latest release of 2.18,
>> which has closed a couple of security holes. I would like to take a more
>> detailed look at 2.20 before we upgrade, since it has some features that
>> we may start using.
>>
>> The current Bugzilla installation already has the 'closed for bug entry'
>> checkbox, and whenever a project moves to JIRA, I check that box. It could
>> bew that this went forgotten for Cocoon, but I have no way to check right
>> now. I'm in China this week and did not bring the laptop that has all my
>> ASF stuff on it. Perhaps another Bugzilla Admin can have a look.
>>
>> The 'closed for bug entry' prevents users from creating new bugs, but I
>> don't think it prevents users from manipulating or commenting on existing
>> bugs. If this is what you are concerned about, I currently don't have a
>> solution.
>>
>> S.
>>
>> --
>> Sander Temme sander@temme.net
>> Webmail -- no signatures
>>
>>
>>
>>
>
>
> --
> Yoav Shapira
> Nimalex LLC
> 1 Mifflin Place, Suite 310
> Cambridge, MA, USA
> yoavs@computer.org / www.yoavshapira.com
>
Re: Make bugzilla for cocoon read only.
Posted by Yoav Shapira <yo...@apache.org>.
Hi,
I just set Cocoon 1 to "closed for bug entry" status. Cocoon 2 was
already set that way. I also verified that the "New Issue" dialog in
Bugzilla doesn't allow either Cocoon 1 or Cocoon 2 as the product for
a new issue. All set?
Yoav
On 3/28/06, Sander Temme <sa...@temme.net> wrote:
>
> On Tue, March 28, 2006 8:30 am, Antonio Gallardo said:
>
> > I am not aware about the internal configuration in the ASF. I see we
> > currently use bugzilla 2.18.5. In our company, we use bugzilla 2.20.1.
> > in the "product" form there is a checkbox called: "Closed for bug entry:
> > ". Bugzilla 2.20.1 has also other benefits as RSS feeds and so on. The
> > upgrade is pretty straight forward.
> >
> > WDYT?
>
> It's on my list, but not very high. We are on the latest release of 2.18,
> which has closed a couple of security holes. I would like to take a more
> detailed look at 2.20 before we upgrade, since it has some features that
> we may start using.
>
> The current Bugzilla installation already has the 'closed for bug entry'
> checkbox, and whenever a project moves to JIRA, I check that box. It could
> bew that this went forgotten for Cocoon, but I have no way to check right
> now. I'm in China this week and did not bring the laptop that has all my
> ASF stuff on it. Perhaps another Bugzilla Admin can have a look.
>
> The 'closed for bug entry' prevents users from creating new bugs, but I
> don't think it prevents users from manipulating or commenting on existing
> bugs. If this is what you are concerned about, I currently don't have a
> solution.
>
> S.
>
> --
> Sander Temme sander@temme.net
> Webmail -- no signatures
>
>
>
--
Yoav Shapira
Nimalex LLC
1 Mifflin Place, Suite 310
Cambridge, MA, USA
yoavs@computer.org / www.yoavshapira.com
Re: Make bugzilla for cocoon read only.
Posted by Sander Temme <sa...@temme.net>.
On Tue, March 28, 2006 8:30 am, Antonio Gallardo said:
> I am not aware about the internal configuration in the ASF. I see we
> currently use bugzilla 2.18.5. In our company, we use bugzilla 2.20.1.
> in the "product" form there is a checkbox called: "Closed for bug entry:
> ". Bugzilla 2.20.1 has also other benefits as RSS feeds and so on. The
> upgrade is pretty straight forward.
>
> WDYT?
It's on my list, but not very high. We are on the latest release of 2.18,
which has closed a couple of security holes. I would like to take a more
detailed look at 2.20 before we upgrade, since it has some features that
we may start using.
The current Bugzilla installation already has the 'closed for bug entry'
checkbox, and whenever a project moves to JIRA, I check that box. It could
bew that this went forgotten for Cocoon, but I have no way to check right
now. I'm in China this week and did not bring the laptop that has all my
ASF stuff on it. Perhaps another Bugzilla Admin can have a look.
The 'closed for bug entry' prevents users from creating new bugs, but I
don't think it prevents users from manipulating or commenting on existing
bugs. If this is what you are concerned about, I currently don't have a
solution.
S.
--
Sander Temme sander@temme.net
Webmail -- no signatures
Re: Make bugzilla for cocoon read only.
Posted by Antonio Gallardo <an...@apache.org>.
Upayavira escribió:
> Antonio Gallardo wrote:
>
>> Dear infra,
>>
>> Is posible to close bugzilla for cocoon? We now use JIRA.
>>
>
> Apparently not. It would have been otherwise.
>
I am not aware about the internal configuration in the ASF. I see we
currently use bugzilla 2.18.5. In our company, we use bugzilla 2.20.1.
in the "product" form there is a checkbox called: "Closed for bug entry:
". Bugzilla 2.20.1 has also other benefits as RSS feeds and so on. The
upgrade is pretty straight forward.
WDYT?
Best Regards,
Antonio Gallardo.
Re: Make bugzilla for cocoon read only.
Posted by Upayavira <uv...@odoko.co.uk>.
Antonio Gallardo wrote:
> Dear infra,
>
> Is posible to close bugzilla for cocoon? We now use JIRA.
Apparently not. It would have been otherwise.
Upayavira