site repository & bug reporting script

I’ve added a new section to the repository, site-src, for things which
are not part of VASSAL, but are part of the support infrastructure around
it. The sole file there right now is report-bug.php, which accepts bug reports
from VASSAL and forwards them on to our bug tracker. This replaces the
HTTP POST code which was in VASSAL.tools.BugDialog:

vassalengine.svn.sourceforge.net … rt-bug.php

Once we’d like to start using our own bug tracker, all we need to do is
change this script to direct bug reports there instead.

Rodney, have a look at this. There’s not much to it—more than half of
the code here is devoted to building the outgoing POST, so you should
be able to grok it without much trouble. Let me know what you want to do
(i.e., if this is ok, and if so what URL it will be reachable at, so I
can update BugDialog to look there).

Cool. I’ll tweak as necessary and post on the web site. The URL will be http://www.vassalengine.org/util/report-bug.php

I changed the title of the bug to include the exception class name and line number where it was thrown. I’d like to change the POST to include the VASSAL version (if it doesn’t already) and store reported bugs in a database table so that we only have one instance with a given title per version. That’ll also allow us to ignore bug reports from older versions of the software when we like.

rk

Post generated using Mail2Forum (mail2forum.com)

Thus spake “Rodney Kinney”:

Be sure to commit back what you change.

If you have time, it would be good you could also start committing the
other scripts which are part of the site.

It does already in the uckelman-work branch.

I don’t follow. What would the table look like?

I was expecting that we’d query a version checking script first, in order
to determine what to display in the bug dialog (either: “Your VASSAL is
too old, try a newer one”, or the regular bug dialog). In the world where
users give detailed bug reports and I can fly through the air under my own
power, I’d like to save people the frustration of typing out a description
and then having it be discarded.


J.


Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)

On Fri, October 3, 2008 10:02 am, Joel Uckelman wrote:

You need to run an update on your DNA. The power-of-flight patches were
merged to the trunk months ago ;)


Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)

In re: version checking prior to bug reporting. I was thinking about what our
options are today and came up with these:

(1) Put a text file on the web site containing a list of versions from which
we want bug reports. When a bug occurs, have VASSAL pull that file and grep
for its version.

(2) Put a script on the web site which accepts a version number as part of
a HTTP GET, and returns a 0 or 1 indicating whether we want bug reports.

Discussion: (1) is simple, requires no scripting, and puts all of the
processing on the client. (2) would let us define arbitrary conditions for
accepting bug reports.

What I expect would normally be the case is that bug reporting would be
upwards closed: That is, there would be some least version from which we’d
want bug reports, and also from any version thereafter. (E.g., right now
that floor would be 3.1.0-beta3.) If that’s so, then we could get by with
having a text file containing a single version number, against which VASSAL
can do a comparison before sending a bug report.

Thoughts?

Might as well do (2). It’s a cleaner API, still very simple to code on the server side and it lets us control the behavior of out-of-date versions, which is really what this is all about.

That said, this is definitely of secondary importance compared to bug-reporting script itself.

rk

Post generated using Mail2Forum (mail2forum.com)

Thus spake “Rodney Kinney”:

This is done.

Both scripts are here:

vassalengine.svn.sourceforge.net … runk/util/

along with two text files, ‘current-release’ and ‘current-beta’, which
the update checker I’m writing wants to read to find the version numbers
of the current release and current beta.


J.


Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)