What makes it hard isn't getting the issue inf, the hard part is flagging issues that are moved to SEC since currently nothing is publicly sent or flagged when an issue is moved to SEC. I'm trying to lobby to get that changed so that the standard move notice is enabled for moves to SEC but until then the "as they are seen" approach is the only way short of scripting a bot to check every SL issue ID up to the latest number in each category and flag anything that returns a string matching the permission denied notice that you get when trying to browse an SEC issue.
-Gordon On Mon, Feb 23, 2009 at 11:15 AM, Jason Giglio <[email protected]>wrote: > Gordon Wendt wrote: > > I just wanted to bring people's attention to a new project that I have > > begun work on that I think is relative to development in SL and to this > > list. I have begun to create a repository of publicly available > > information from the jira-notify list and the RSS feeds of the content > > of issues that have been later "disappeared" into SEC. Since issues > > originally created into SEC aren't publicly reported unless the reporter > > or a Linden discloses them (both unlikely) it doesn't contain any > > "privately" reported data only an aggragate version of publicly > > available logs. > > > > I believe SLJirastats never purges issues that go away, so you can > always get the old info from there. >
_______________________________________________ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/SLDev Please read the policies before posting to keep unmoderated posting privileges
