Hi!
I don't know how and where to report about bugs in Ruby 1.9.n. Does
there an official way exist?
Wolfgang Nádasi-Donner
···
--
Posted via http://www.ruby-forum.com/.
Hi,
I was curious about where to ruby bugs are submitted recently too.
After looking around a bit, I was able to find this
http://rubyforge.org/projects/ruby/ .
Joe
···
On Dec 28, 2007 5:13 AM, Wolfgang Nádasi-Donner <ed.odanow@wonado.de> wrote:
Hi!
I don't know how and where to report about bugs in Ruby 1.9.n. Does
there an official way exist?Wolfgang Nádasi-Donner
--
Posted via http://www.ruby-forum.com/\.
Joe wrote:
Hi,
I was curious about where to ruby bugs are submitted recently too.
After looking around a bit, I was able to find this
http://rubyforge.org/projects/ruby/ .Joe
Interesting, but is it the place recommended by Mats and the kernel
team?
Wolfgang Nádasi-Donner
···
--
Posted via http://www.ruby-forum.com/\.
Ruby Core says either put them on there or email the ruby-core mailing list.
Fred
···
On 28 Dec 2007, at 21:02, Wolfgang Nádasi-Donner wrote:
Joe wrote:
Hi,
I was curious about where to ruby bugs are submitted recently too.
After looking around a bit, I was able to find this
http://rubyforge.org/projects/ruby/ .Joe
Interesting, but is it the place recommended by Mats and the kernel
team?
Hi,
···
In message "Re: How and Where to report bugs in Ruby 1.9.n?" on Sat, 29 Dec 2007 06:51:55 +0900, Frederick Cheung <frederick.cheung@gmail.com> writes:
I was curious about where to ruby bugs are submitted recently too.
After looking around a bit, I was able to find this
http://rubyforge.org/projects/ruby/ .
Interesting, but is it the place recommended by Mats and the kernel
team?http://www.ruby-lang.org/en/community/ruby-core/ says either put them
on there or email the ruby-core mailing list.
Yes. We are (vaguely) planning on making BTS for the core team, but
until then, rubyforge bug tracker and ruby-core list works.
matz.
If the core team is willing to spec out what they need out of their BTS, I might be willing to build it. I have a need to build one for another project, so, if our needs are similar, I would certainly try and support your wishes as well.
James Edward Gray II
···
On Dec 28, 2007, at 6:08 PM, Yukihiro Matsumoto wrote:
Hi,
In message "Re: How and Where to report bugs in Ruby 1.9.n?" > on Sat, 29 Dec 2007 06:51:55 +0900, Frederick Cheung <frederick.cheung@gmail.com > > writes:
>>> I was curious about where to ruby bugs are submitted recently too.
>>> After looking around a bit, I was able to find this
>>> http://rubyforge.org/projects/ruby/ .>> Interesting, but is it the place recommended by Mats and the kernel
>> team?
>
>Ruby Core says either put them
>on there or email the ruby-core mailing list.Yes. We are (vaguely) planning on making BTS for the core team, but
until then, rubyforge bug tracker and ruby-core list works.
Why not use an existing one?
Bugzilla [http://www.bugzilla.org/\] has worked well for mozilla, and
other projects.
I personally like trac [http://trac.edgewall.org/\] more though.
There is a huge list of them here:
Many I haven't heard of. There are a good number of free/open source
ones. Might be worth a look before writing one.
Joe
···
On Dec 28, 2007 8:10 PM, James Gray <james@grayproductions.net> wrote:
On Dec 28, 2007, at 6:08 PM, Yukihiro Matsumoto wrote:
> Hi,
>
> In message "Re: How and Where to report bugs in Ruby 1.9.n?" > > on Sat, 29 Dec 2007 06:51:55 +0900, Frederick Cheung <frederick.cheung@gmail.com > > > writes:
>
> >>> I was curious about where to ruby bugs are submitted recently too.
> >>> After looking around a bit, I was able to find this
> >>> http://rubyforge.org/projects/ruby/ .
>
> >> Interesting, but is it the place recommended by Mats and the kernel
> >> team?
> >
> >Ruby Core says either put them
> >on there or email the ruby-core mailing list.
>
> Yes. We are (vaguely) planning on making BTS for the core team, but
> until then, rubyforge bug tracker and ruby-core list works.If the core team is willing to spec out what they need out of their
BTS, I might be willing to build it. I have a need to build one for
another project, so, if our needs are similar, I would certainly try
and support your wishes as well.James Edward Gray II
Hi,
If the core team is willing to spec out what they need out of their
BTS, I might be willing to build it. I have a need to build one for
another project, so, if our needs are similar, I would certainly try
and support your wishes as well.
Here's the my requirements expressed in [ruby-dev:32794]:
* written in Ruby
* can be worked with Subversion (namely our repository)
* can correspond with mailing lists, such as easy communication with
submitters, and more
* can manage tickets (or issues)
* can stock information (e.g. as Wiki pages)
* has good spam tolerance
* can be fully customized
Some suggested RedMine, Retrospectiva and Lighthouse. I am no yet
sure whether any of them satisfies the requirements. Any opinion or
info welcome.
matz.
···
In message "Re: How and Where to report bugs in Ruby 1.9.n?" on Sat, 29 Dec 2007 10:10:20 +0900, James Gray <james@grayproductions.net> writes:
What about Mingle? It's JRuby, but it's *still* Ruby 
(I'm playing with it for work; I'm sure that ThoughtWorks would *love*
to work with the Ruby community on this, though.)
-austin
···
On Dec 31, 2007 10:08 AM, Yukihiro Matsumoto <matz@ruby-lang.org> wrote:
In message "Re: How and Where to report bugs in Ruby 1.9.n?" > on Sat, 29 Dec 2007 10:10:20 +0900, James Gray <james@grayproductions.net> writes:
>If the core team is willing to spec out what they need out of their
>BTS, I might be willing to build it. I have a need to build one for
>another project, so, if our needs are similar, I would certainly try
>and support your wishes as well.Here's the my requirements expressed in [ruby-dev:32794]:
* written in Ruby
* can be worked with Subversion (namely our repository)
* can correspond with mailing lists, such as easy communication with
submitters, and more
* can manage tickets (or issues)
* can stock information (e.g. as Wiki pages)
* has good spam tolerance
* can be fully customized
--
Austin Ziegler * halostatue@gmail.com * http://www.halostatue.ca/
* austin@halostatue.ca * You are in a maze of twisty little passages, all alike. // halo • statue
* austin@zieglers.ca
Hi,
>If the core team is willing to spec out what they need out of their
>BTS, I might be willing to build it. I have a need to build one for
>another project, so, if our needs are similar, I would certainly try
>and support your wishes as well.Here's the my requirements expressed in [ruby-dev:32794]:
* written in Ruby
* can be worked with Subversion (namely our repository)
* can correspond with mailing lists, such as easy communication with
submitters, and more
* can manage tickets (or issues)
* can stock information (e.g. as Wiki pages)
* has good spam tolerance
* can be fully customized
OK, so you definitely want Trac, except in Ruby.
My needs are more basic. I don't have to hook into a Subversion repository and I really only need good ticket support. I do want to be able to administer my solution from my email though.
I understand why the above makes sense for you needs though.
Some suggested RedMine, Retrospectiva and Lighthouse. I am no yet
sure whether any of them satisfies the requirements. Any opinion or
info welcome.
I wasn't aware of RedMine, so thanks for bringing it to my attention. It does seem to satisfy most of your criteria. I think you would be the one hooking it into mailing lists and customization seems to just be writing Rails plugins, but it's still sounds pretty close to what you want.
Retrospectiva didn't feel as far along to me. It has something called a "mail queue," but I had trouble finding any information on what that actually is. It does seem to be an active project though and it meets many of your requirements.
I've looked at Lighthouse quite a bit. It's a nice option and you should at least watch the videos on their site. In the end, I decided against it because, while it is somewhat customizable, I didn't feel like I would be able to rewrite any part of it I wasn't completely satisfied with.
Those are my takes on the options you mentioned. Thanks for laying out what you are after and I'm sorry I wasn't more help in getting you there.
James Edward Gray II
···
On Dec 31, 2007, at 9:08 AM, Yukihiro Matsumoto wrote:
In message "Re: How and Where to report bugs in Ruby 1.9.n?" > on Sat, 29 Dec 2007 10:10:20 +0900, James Gray <james@grayproductions.net > > writes: