-
Hi, For the last while we've had two places where we track issues with listen. One on the openplans trac instance and another on the the product page at plone.org. All issues have now been reviewed and consolidated here: http://trac.openplans.org/listen/ This will be the single point for listen issue tracking going forward. Thanks, Chris
- Thread Outline:
-
-
Re: listen issues consolidated
by
ra
- Re: listen issues consolidated by Raphael Ritz <r.ritz@...>
-
Re: listen issues consolidated
by
ra
-
Chris Abraham wrote: > Hi, > For the last while we've had two places where we track issues with > listen. One on the openplans trac instance and another on the the > product page at plone.org. All issues have now been reviewed and > consolidated here: > > http://trac.openplans.org/listen/ > > This will be the single point for listen issue tracking going forward. some of you may be a bit confused... hopefully i can add a bit more context... there has actually only ever been a single listen issue tracker, which is the Poi instance on plone.org, at the following URL: http://plone.org/products/listen/issues however, since OpenPlans developers have done a considerable amount of work on listen in the context of getting it to work correctly on openplans.org, there have also been a number of listen-related bugs entered in the OpenPlans trac site. you can see those here: http://trac.openplans.org/openplans/report/24 some of the issues in TOPP's trac site belong there, because they're related to the code that integrates listen with OpenPlans. however, some of the issues were actually core listen issues; these issues didn't really belong in the OpenPlans tracker, since they're general listen issues. for a while, some of us at TOPP have had it on our to-do list to go through and move the general listen issues into the listen issue tracker, so that folks who are following listen development would be able to see all of the issues in one place. now, to further complicate things, there has also been some interest within TOPP to give listen a slightly better dev infrastructure than is currently provided with the listen product area on plone.org. in particular, we want to provide listen with its own trac instance, with the nice issue tracking and svn browsing that trac provides. to that end, we've set up a new trac instance, specifically for listen, at the following URL: http://trac.openplans.org/listen/ this is hosted by TOPP, but it is meant to be a community resource. anyone can open tickets, and anyone can become a supporter and claim and/or resolve tickets. all of the open issues from the plone.org Poi tracker AND the misplaced core listen tickets that were in the OpenPlans trac have been consolidated into this new site. it was our intent to get this information out to all of you BEFORE we actually did this migration, just so everyone knew what was going on, and to give folks a chance to speak up if they had any comments on the plan. unfortunately, our internal communication broke down a bit, and that didn't happen. apologies for the ex-post-facto information. hopefully, however, this won't cause too much heartache. i've gone ahead and closed the Poi tracker so it won't accept any new tickets, and i've added an issue tracker URL on the plone.org/products/listen page which points to the new trac instance. unfortunately, while i can see these changes when i'm logged in to plone.org, it hasn't yet shown up for me when i view the page as an anonymous user. i think this is just caching latency, hopefully these changes will show up soon. thanks, and sorry for any confusion, -r
-
Rob Miller wrote: [..] > i've gone ahead and closed the Poi tracker so it won't accept any new > tickets, and i've added an issue tracker URL on the > plone.org/products/listen page which points to the new trac instance. > unfortunately, while i can see these changes when i'm logged in to > plone.org, it hasn't yet shown up for me when i view the page as an > anonymous user. i think this is just caching latency, hopefully these > changes will show up soon. > > thanks, and sorry for any confusion, > No problem here with the change. Just to clarify one thing: the listen code base itself will stay in the collective or are there plans to move that as well one day? And finally: when I go to http://plone.org/products/listen (as anonymous) I currently see *2* tracker links the old and the new one. But when following the link to the old one it is immediately obvious that this one is deprecated and where to turn to instead. Raphael
-
Raphael Ritz wrote: > Rob Miller wrote: > > [..] > >> i've gone ahead and closed the Poi tracker so it won't accept any new >> tickets, and i've added an issue tracker URL on the >> plone.org/products/listen page which points to the new trac instance. >> unfortunately, while i can see these changes when i'm logged in to >> plone.org, it hasn't yet shown up for me when i view the page as an >> anonymous user. i think this is just caching latency, hopefully these >> changes will show up soon. >> >> thanks, and sorry for any confusion, >> > > No problem here with the change. > > Just to clarify one thing: the listen code base > itself will stay in the collective or are there > plans to move that as well one day? there are no plans to move the listen code base; i think the collective is the best place for it, personally, since folks who are likely to contribute are likely to already have commit access there. this means, of course, that we'll need to use a trac plug-in to get the svn browsing to work w/ a remote svn repository, but we're already doing a bunch of trac customization work, so i think this shouldn't be too difficult. > And finally: when I go to > > http://plone.org/products/listen > > (as anonymous) I currently see *2* tracker links > the old and the new one. > But when following the link to the old one it is > immediately obvious that this one is deprecated > and where to turn to instead. yes, this unfortunately seems to be a limitation of PloneSoftwareCenter. when there is a Poi instance in the project area, it is listed as an issue tracker, and when a tracker URL is explicitly entered, it is also listed as an issue tracker. eventually it will probably be a good idea to remove the Poi tracker altogether, to remove this duplication, but i think that's a bit premature right now. -r
-
-
text.html (text/html) 1.2 kB