[ANN] Cog issue tracker

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[ANN] Cog issue tracker

Igor Stasenko
Hello everyone.

Without much debate we just created it at [1]. Now there is a separate
place for filing issues for Cog VM.
I think Cog deserves separate issue tracker, because currently all
reports and problems are mainly buried in vm-dev mailing list,
and it is hard to tell what is status of one or another issue, which
we lately discovered. And such approach definitely won't scale.
So, it was a main reason for making this move.

Lets help Eliot (and others who involved in development) make
activities to be more organized and visible.

I'd like to stress that there is nothing inside code.google in
particular, which could make its issue tracker serve our needs well.
It will work well only if we, as community, organize ourselves and pay
attention to collect and put important information there,
make it easily accessible, structured and so on..



[1] http://code.google.com/p/cog/



--
Best regards,
Igor Stasenko AKA sig.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [ANN] Cog issue tracker

Tudor Girba
+1

Just to clarify: The issue tracker was created after a discussion with Elliot this week, in which he asked us to help him create a Google Code for issues related to Cog so that people can participate.

Cheers,
Doru


On 11 Mar 2011, at 00:46, Igor Stasenko wrote:

> Hello everyone.
>
> Without much debate we just created it at [1]. Now there is a separate
> place for filing issues for Cog VM.
> I think Cog deserves separate issue tracker, because currently all
> reports and problems are mainly buried in vm-dev mailing list,
> and it is hard to tell what is status of one or another issue, which
> we lately discovered. And such approach definitely won't scale.
> So, it was a main reason for making this move.
>
> Lets help Eliot (and others who involved in development) make
> activities to be more organized and visible.
>
> I'd like to stress that there is nothing inside code.google in
> particular, which could make its issue tracker serve our needs well.
> It will work well only if we, as community, organize ourselves and pay
> attention to collect and put important information there,
> make it easily accessible, structured and so on..
>
>
>
> [1] http://code.google.com/p/cog/
>
>
>
> --
> Best regards,
> Igor Stasenko AKA sig.
>

--
www.tudorgirba.com

"Every thing should have the right to be different."




Loading...