Re: [Peerguardian-devel] sourceforge.net bug and feature request tracker

[jre-phoenix <jre...@us...>]

Finally done. I've closed 228 reports. They will be reopened if the
originator replies to them.
So from now on we can use these trackers.

In other news, although I'm generally quite busy, I managed to find
some time in the past days. The main issues that I knew of are sorted
out now. So I think I'll make a release of pgld and pglcmd in the next
days.

Greets
jre

On Mon, Dec 7, 2009 at 7:35 PM, Cade Robinson <cad...@gm...> wrote:
> That sounds great to me.
> Let 'er rip! :)
>
> On Mon, 2009-12-07 at 19:07 +0100, jre-phoenix wrote:
>
> Hi all
>
> I´d like to actually use the sourceforge trackers (bug reports and
> feature requests). They can be a great help to manage a project: We
> developers can see which tasks have to be done, and who actually is
> working on them. Of course we can also write our own bug reports and
> feature requests, if we know that something is a more complicated
> tasks and takes some time - so we can also use them as TODO list. The
> users on the other side can skip over them, in order to see whether
> their problem is unique, or if perhaps a solution already exists.
>
> But currently these trackers are just spammed up. So I'd like to
> prepare some responses, apply them to all open artifacts, and mass
> close them.
>
> For the future I would prepare canned responses (similar to the
> responses shown below), which can be easily adapted to standard
> requests, which are not of any informational use for the project. Then
> we can work and concentrate on the important parts, and even use this
> for internal project communication, or as reminders.
>
> My suggestion therefore:
>
>
> Bug tracker and Feature requests:
> Close all with this response:
> ---
> In an effort to make this tracker usable again, this report is closed.
>
> If this report relates to the PeerGuardian Windows application, you
> may try Peerblock instead: http://www.peerblock.com.
>
> If this report relates to an IP that is blocked or not blocked: The
> blocklists are maintained by http://www.bluetack.co.uk and
> http://tbg.iblocklist.com. Neither
>
> If this report is about failed blocklist downloads. Check out
> http://iblocklist.com, this site offers reliable downloads of all
> blocklists.
> ---
>
>
> Support Requests
> Close all with this canned response (and probably disable this tracker):
> ---
> Support for PeerGuardian is available at the phoenixlabs forum:
> http://forums.phoenixlabs.org/
>
> If this report relates to the PeerGuardian Windows application, you
> may try Peerblock instead: http://www.peerblock.com.
>
> If this report relates to an IP that is blocked or not blocked: The
> blocklists are maintained by http://www.bluetack.co.uk and
> http://tbg.iblocklist.com.
>
> If this report is about failed blocklist downloads. Check out
> http://iblocklist.com
> , this site offers reliable downloads of all
> blocklists.
> ---
>
>
> Any suggestions welcome! Otherwise I´ll do all that in about a week.
> jre
>
> ------------------------------------------------------------------------------
> Join us December 9, 2009 for the Red Hat Virtual Experience,
> a free event focused on virtualization and cloud computing.
> Attend in-depth sessions from your desk. Your couch. Anywhere.
> http://p.sf.net/sfu/redhat-sfdev2dev
> _______________________________________________
> Peerguardian-devel mailing list
> Pee...@li...
> https://lists.sourceforge.net/lists/listinfo/peerguardian-devel
>