Skip to Content.
Sympa Menu

sm-discuss - Re: [SM-Discuss] Version reporting

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: Dufflebunk <dufflebunk AT dufflebunk.homeip.net>
  • To: Geoffrey Derber <Geoffrey.Derber AT Trinity.edu>
  • Cc: sm-discuss <sm-discuss AT lists.ibiblio.org>
  • Cc: spencero AT mail.utexas.edu
  • Subject: Re: [SM-Discuss] Version reporting
  • Date: 05 Mar 2003 02:05:32 -0500

A agree with Geoffery on this. Using bugzilla is best. Simple automated
reporting might not be enough if, for example, more than one spell has
to be updated to get another to work, an automated report wouldn't have
that (or else reports would become quite large).
I'm not saying it would be impossible, but it would be quite a task.
OTOH, someone could write a short script that automates this bug report
to bugzilla for new versions.
Ideas like this have been tossed around a bit (like reporting failures
too). The main thing though is that maintainers (maintainers, please
correct me if you prefer a multitude of places containing overlapping
reports) need a single easy consistent interface to bugs, upgrades, etc.
So, if anyone has an itch to do any of that, I'd suggest letting it
interface in some way with the bugzilla. No idea how this would be done
though.

On Wed, 2003-03-05 at 01:31, Geoffrey Derber wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Spencer Ogden wrote:
> | I think this may have come up before, but I thought I would throw it out
> | there anyway. Would it be possible to have some sort of reporting to a
> | central location of successful compiles? Here is what I am thinking...
> |
> | I don't have CVS access, and I'm not sure I want it, but I do maintain
> | custom versions of a few spells which either aren't in the grimoire or
> the
> | grimoire versions are old. So I am thinking it would be nice to have an
> | easy way to let maintainers know the latest version of a spell which is
> | successfully working. Maybe upon a successful compile, if it is an
> | upgrade, a central list is checked. This list contains spell names with
> | versions. If the version just compiled locally is greater, then update
> the
> | list and optionally mail the spell used to the maintatiner. This would
> | allow me to modify a spell locally, and if it successful, easily notify
> | the maintainer that an upgrade is availible. And with the central list
> the
> | maintainer would only get notified once. I would see this as an opt-in
> | system which could be turned on if wanted.
> |
> | Stupid idea?
> |
> | Spencer
> | _______________________________________________
> | SM-Discuss mailing list
> | SM-Discuss AT lists.ibiblio.org
> | http://lists.ibiblio.org/mailman/listinfo/sm-discuss
> |
> I've just been going to bugzilla and making a short bug:
>
> summary: <spell> <version>
> description:
> <spell> is now version <version>
>
> seems to work okay
>
> Geoff
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.1 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQE+ZZmqHBxk9YxVu58RAnxcAKCNbx0mlO768KHETN18RyojhjRWiQCg3KOK
> 0K+Ca3AO2wxRN3igki3qE+A=
> =CQ9D
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> SM-Discuss mailing list
> SM-Discuss AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/sm-discuss




Archive powered by MHonArc 2.6.24.

Top of Page