On Mon, Aug 18, 2008 at 2:50 PM, jerry gay <[EMAIL PROTECTED]> wrote: > On Mon, Aug 18, 2008 at 11:41 AM, Will Coleda <[EMAIL PROTECTED]> wrote: >> On Mon, Aug 18, 2008 at 2:29 PM, Michael Peters <[EMAIL PROTECTED]> wrote: >>> Will Coleda wrote: >>> >>>> The eventual goal of this cleanup is to get these tests running via >>>> smolder to give core developers more feedback on their commits. The >>>> aborted test in this file can be TODOd if we can't fix the root cause >>>> before release. >>> >>> To this end, how would we like this to be done. I've been thinking about >>> creating a separate project for Rakudo and then having it's full test suite, >>> spec test and spec_test_regression all going as separate tags so they can be >>> viewed separately. >> >> Rakudo would, at the moment, need its own version anyway, since you >> can't run rakudo via the unified harness. >> >>> I could create a separate project for each built-in language (might be too >>> many) or just have a misc-languages project. But it might be helpful to have >>> each "big" language (Rakudo, pipp, cardinal) have their own projects so that >>> they have their own RSS feeds. >> >> I am of two minds: >> >> - the tcl developer in me wants a feed for my language so I can easily track >> it. >> - the parrot developer wants an aggregated feed that shows all the >> languages so I can easily see if I broke something. >> >> Can we start with the fine-grained version and provide an aggregated >> version? We can decide on the aggregated version later, if necessary. >> (just languages? just some of them? all of them -and- core parrot?) >> > yes, please. this is what rss aggregation is for. before parrot's > general availability release, we will be moving many if not most of > the languages out of the parrot repository. this will make > languages-smolder (or a similar parrot make target) less relevant, and > rss aggregation more important. > > anyone know of an aggregated feed generator, so one can build a > personalized feed of feeds and subscribe to that? we can host it at > parrot.org once we have that infrastructure set up. > ~jerry >
We are running one now: http://planet.parrotcode.org/ -- Will "Coke" Coleda
