Bug Reports for 1.6 Release Candidates

Bug Reports for 1.6 Release Candidates

[Evan Prodromou]

While I'm on the subject of release critical bugs: I think that the
1.6 release candidate builds need to be better advertised on the Guile
Web site. After all, this is probably the most important thing
happening with Guile right now, and it should be the most prominently
featured piece of info there.

The news of the 1.5.x releases should be on the index page, with a
prominent link to the how-to-report-a-bug page, and a link to the
current unresolved bugs list. I don't think the BUGS file, or an
HTML-munged version of such, is available anywhere on the site.

~ESP

-- 
Evan Prodromou
evan@glug.org

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel

Re: Bug Reports for 1.6 Release Candidates

[Evan Prodromou]

>>>>> "EP" == Evan Prodromou <evan@glug.org> writes:

    EP> The news of the 1.5.x releases should be on the index page,
    EP> with a prominent link to the how-to-report-a-bug page, and a
    EP> link to the current unresolved bugs list. I don't think the
    EP> BUGS file, or an HTML-munged version of such, is available
    EP> anywhere on the site.

Just for the hell of it, I ripped out a POS BUGS-parsing script this
afternoon:

        http://evan.prodromou.san-francisco.ca.us/BUGS2html.scm

I'm sure anyone with more experience in Guile text processing could
make it much better, but it does the job and I'm not going to sweat it
too much.

Output is here:

        http://evan.prodromou.san-francisco.ca.us/bugs_index.html

...and although it's not pretty, it's a start.

~ESP

-- 
Evan Prodromou
evan@glug.org

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel

Re: Bug Reports for 1.6 Release Candidates

[Thien-Thi Nguyen]

   From: Evan Prodromou <evan@glug.org>
   Date: Sat, 16 Mar 2002 21:05:22 -0600

   http://evan.prodromou.san-francisco.ca.us/BUGS2html.scm

cool.  output for guile-core and guile-core-1.6 should be appearing
shortly under "details" heading under: http://www.glug.org/snap/ .
perhaps guile-core-1.4 will get a BUGS file in the near future.
(a link to the (slightly modified) source is forthcoming.)

thi

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel

Re: Bug Reports for 1.6 Release Candidates

[Evan Prodromou]

>>>>> "TN" == Thien-Thi Nguyen <ttn@giblet.glug.org> writes:

    TN> (a link to the (slightly modified) source is forthcoming.)

Yay. That source is a mess.

Also, the BUGS file as it stands doesn't have a criticality rating
(wishlist, normal, release-critical, whatever) nor a version number
that the bug was identified in (1.4, 1.5.x, 1.7.x, etc.), nor a
version number that the bug _should_ be fixed in (1.5.x, 1.7.x).

This, I think, is important if Marius is going to be able to make his
calls about what bugs are release critical and what bugs aren't.

~ESP

-- 
Evan Prodromou
evan@glug.org

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel

Re: Bug Reports for 1.6 Release Candidates

[Rob Browning]

Evan Prodromou <evan@glug.org> writes:

> Also, the BUGS file as it stands doesn't have a criticality rating
> (wishlist, normal, release-critical, whatever) nor a version number
> that the bug was identified in (1.4, 1.5.x, 1.7.x, etc.), nor a
> version number that the bug _should_ be fixed in (1.5.x, 1.7.x).

Agreed, and it might be nice to have some other way to keep the info
for a bug that applies across more than one tree in one location (see
my reply to your other thread) if we can manage to do it with a
solution that doesn't just over-complicate things.  Though bug
tracking seems to me like *exactly* the kind of thing for which you
want a relational DB.

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C  64AE 78FE E5FE F0CB A0AD

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel

Re: Bug Reports for 1.6 Release Candidates

[Evan Prodromou]

>>>>> "RB" == Rob Browning <rlb@defaultvalue.org> writes:

    RB> Though bug tracking seems to me like *exactly* the kind of
    RB> thing for which you want a relational DB.

Absolutely, absolutely. That said, I think if we (actually, it's not
*me* making the decisions, so I dunno what I'm talking about with this
we stuff, and we have yet to hear from Marius on the issue) get hung
up on having Only The Best Tracking System, we'll lose sight of the
fact that we're trying to get out a release, get it out with minimum
embarassing buggage, and get it out sooner rather than later.

I'd recommend keeping the BUGS file for now, and maybe switching over
to a more civilized bug-tracker after the 1.6 release.

~ESP

-- 
Evan Prodromou
evan@glug.org

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel

Re: Bug Reports for 1.6 Release Candidates

[Rob Browning]

Evan Prodromou <evan@glug.org> writes:

> I'd recommend keeping the BUGS file for now, and maybe switching
> over to a more civilized bug-tracker after the 1.6 release.

ABSOLUTELY.

Just wanted to make sure no one thought I was talking about short-term
changes here :> For 1.6, the BUGS and TODO files will do quite nicely.
I was just musing about things we might want to do later, and I don't
know that we'd ever do some of the fancier stuff.

I do think that we should probably use the TODO file to list the BUGS
that are release critical in the per-release section(s).  Ideally
looking at the TODO should give you a complete overview of what has to
be done.

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C  64AE 78FE E5FE F0CB A0AD

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel

Re: Bug Reports for 1.6 Release Candidates

[Thien-Thi Nguyen]

   From: Evan Prodromou <evan@glug.org>
   Date: Sat, 16 Mar 2002 12:50:59 -0600

   While I'm on the subject of release critical bugs: I think that the
   1.6 release candidate builds need to be better advertised on the
   Guile Web site. After all, this is probably the most important thing
   happening with Guile right now, and it should be the most prominently
   featured piece of info there.

guile main page primarily has "about" info, w/ links to a news page.
anyone object to moving news stuff to the main page and moving "about"
stuff elsewhere?

thi

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel

Re: Bug Reports for 1.6 Release Candidates

[Rob Browning]

Thien-Thi Nguyen <ttn@giblet.glug.org> writes:

> guile main page primarily has "about" info, w/ links to a news page.
> anyone object to moving news stuff to the main page and moving
> "about" stuff elsewhere?

I actually wondered about that myself when went to look at the page
the other day -- I think that's a good idea, though perhaps we should
have an "about summary" followed by a news log.

                       title stuff

            brief summary of guile (i.e. abstract)

     News:

        2002-03-13 ...

        2002-02-25 ...

        2002-02-01 ...

as a suggestion...

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C  64AE 78FE E5FE F0CB A0AD

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel