8:19 a.m.
There are currently 200 open issues in the tracker. Of these, more
than half have no priority or severity set. We would greatly
appreciate it if volunteers would help classify these issues. You can
do as many or as few as you like.
As a small incentive, normally the "priority" attribute is property of
the Reviewers and/or the developer who takes responsibility for the
issue, but for unclassified issues I encourage you to set the priority.
Basically, to help you just register your user or get a password reset
if you've been automatically registered by one of the "pre-loaded"
issues, read the documentation at
http://tracker.xemacs.org/XEmacs/its/user_guide.html#issue-triage-guidelines
and get started!
Thanks in advance to all volunteers, and thanks to everybody for your
support of XEmacs!
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
3:06 p.m.
Am Montag, 11. Februar 2008 09:19 schrieb Stephen J. Turnbull:
There are currently 200 open issues in the tracker. Of these, more
than half have no priority or severity set. We would greatly
appreciate it if volunteers would help classify these issues. You can
do as many or as few as you like.
As a small incentive, normally the "priority" attribute is property of
the Reviewers and/or the developer who takes responsibility for the
issue, but for unclassified issues I encourage you to set the priority.
Basically, to help you just register your user or get a password reset
if you've been automatically registered by one of the "pre-loaded"
issues, read the documentation at
http://tracker.xemacs.org/XEmacs/its/user_guide.html#issue-triage-guideline
I get
Error response
Error code 404.
Message: /its/user_guide.html.
Error code explanation: 404 = Nothing matches the given URI.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
3:02 a.m.
Andreas Röhler writes:
> read the documentation at
>
> http://tracker.xemacs.org/XEmacs/its/user_guide.html#issue-triage-guideline
I get
Error code explanation: 404 = Nothing matches the given URI.
Sorry, that used to work (or maybe only in my local setup?), but now
on the public internet it needs to be
http://tracker.xemacs.org/XEmacs/its/＠＠file/user_guide.html#issue-triage-...
Regards,
Steve
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
9:08 a.m.
On 11.02.2008, at 09:19, Stephen J. Turnbull wrote:
It might be too early to complain, but I don't see a DNS entry for
tracker.xemacs.org (yet?). I get this:
[0 knauel＠midgard text] dig tracker.xemacs.org
; <<>> DiG 9.4.1-P1 <<>> tracker.xemacs.org
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 28043
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;tracker.xemacs.org. IN A
;; AUTHORITY SECTION:
xemacs.org. 10519 IN SOA gwyn.tux.org. hostmaster.xemacs.org.
2008011801 7200 1800 1209600 7200
;; Query time: 1 msec
;; SERVER: 134.2.14.4#53(134.2.14.4)
;; WHEN: Wed Feb 13 10:03:36 2008
;; MSG SIZE rcvd: 92
I've tried other name servers and always got the same result.
-Eric
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
9:20 p.m.
Eric> It might be too early to complain, but I don't see a DNS entry for
Eric> tracker.xemacs.org (yet?).
I haven't had any problems.
Skip
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
11:58 p.m.
Eric Knauel writes:
It might be too early to complain,
"Once is coincidence, twice is enemy action." Never too soon. ;-)
but I don't see a DNS entry for tracker.xemacs.org (yet?). I get
this:
It's been there since before the announcement. I have no trouble
seeing it from cvs.xemacs.org (in Denmark), uwakimon.sk.tsukuba.ac.jp
(in Japan), or c-71-204-153-214.hsd1.ca.comcast.net (in California).
I suspect you have local DNS issues, maybe a caching nameserver with
too long expiry and/or a broken firewall proxy. Or you're simply
running on Mac OS X, which sucks in this respect. I don't know what
the problem is, but Mac OS regularly times out before receiving data
from the DNS for me. Rerunning the query always works (unless I've
pulled the plug on the network :-), though.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
7:44 p.m.
"Stephen J. Turnbull" <stephen(a)xemacs.org> writes:
There are currently 200 open issues in the tracker. Of these, more
than half have no priority or severity set. We would greatly
appreciate it if volunteers would help classify these issues. You can
do as many or as few as you like.
As a small incentive, normally the "priority" attribute is property of
the Reviewers and/or the developer who takes responsibility for the
issue, but for unclassified issues I encourage you to set the priority.
Basically, to help you just register your user or get a password reset
if you've been automatically registered by one of the "pre-loaded"
issues, read the documentation at
http://tracker.xemacs.org/XEmacs/its/user_guide.html#issue-triage-guidelines
http://tracker.xemacs.org/XEmacs/its/＠＠file/user_guide.html#issue-triage-...
works for me, not the above.
Adrian
and get started!
Thanks in advance to all volunteers, and thanks to everybody for your
support of XEmacs!
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
--
Adrian Aichner
mailto:adrian＠xemacs.org
http://www.xemacs.org/
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
12:34 a.m.
>>>> Stephen wrote:
Stephen> There are currently 200 open issues in the tracker.
I hope that some is possible to close. If you are not authorized to
close an issue yourself, but you think that it is already resolved,
what should you do?
Somewhat related: Issue 149. I'm listed as Creator but I can't close
the issue. Wouldn't that be good if that was possible? I file a report
and when it is fixed I can close it? Or am I supposed to move the
issue to another state so that some other role can close it?
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
6:06 p.m.
Mats Lidell writes:
>>>>> Stephen wrote:
Stephen> There are currently 200 open issues in the tracker.
I hope that some is possible to close. If you are not authorized to
close an issue yourself, but you think that it is already resolved,
what should you do?
Somewhat related: Issue 149. I'm listed as Creator but I can't close
the issue. Wouldn't that be good if that was possible? I file a report
and when it is fixed I can close it? Or am I supposed to move the
issue to another state so that some other role can close it?
I haven't actually added any auditing yet; the only things that must
be done by a tracker admin are editing users and changing
configuration.
If you can't close it, then presumably you're not logged in. Logged
in is the only restriction on creating new issues and editing old
ones, including closing them. If you are logged in and can't edit the
issues, then we need to figure out why. For information about logging
in, see the User Guide
http://tracker.xemacs.org/XEmacs/its/＠＠file/user_guide.html
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
9:48 p.m.
>>>> Stephen wrote:
Stephen> If you are logged in and can't edit the issues, then we need
Stephen> to figure out why.
This is what I get when I try to close that issue:
Issue149 Editing
Required issue property module not supplied
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
10:21 p.m.
>>>> "Mats" == Mats Lidell
<matsl(a)xemacs.org> writes:
Mats> This is what I get when I try to close that issue:
Mats> Issue149 Editing Required issue property module not supplied
The issue needs to be assigned to a module. Look for the red-labelled
Module field, click on "(list"), then click on one or more modules that
the issue applies to. I'm guessing "core code 21.5".
mike
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
4:23 a.m.
Two questions about bug triage:
- Any user can change the Status from new to verified, yes?
- Will the package maintainers be added to the Assigned-To drop-down?
cheers,
mike
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
7:20 a.m.
mike.kupfer(a)xemacs.org writes:
Two questions about bug triage:
- Any user can change the Status from new to verified, yes?
Except for the OP ;-), yes. The OP should include a test or recipe,
or a pointer to a corroborating report (superseding it in the tracker
if appropriate).
- Will the package maintainers be added to the Assigned-To drop-down?
Well, what I had in mind was providing a feature where any registered
User could register themselves as Developer (see issue284).
The other thing I should do is add the logged-in user to that menu
(new issue296, flagged "urgent"). I think only volunteers (including
all Reviewers ex oficio) should be assigned issues by others. I want
Assigned-To to have at least minimal commitment semantics: somebody
has accepted specific responsibility for it. In the case of a
third-party assignment, it should be to somebody who will at least
take the time to unassign the issue if they don't want it. :-)
Even though package maintainers have accepted responsibility for their
packages, I don't think package maintainers need to be qualified to
*fix* bugs. They just need to know who can fix them, and how to find
those people. So I'm leery of making them Developers ex oficio.
NB: I'm going to go ahead and implement the suggestions above because
they're better than the current situation, but they're not set in
stone. Comments welcome!
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
6:15 p.m.
>>>> "ST" == Stephen J Turnbull
<stephen(a)xemacs.org> writes:
MikeK> - Will the package maintainers be added to the Assigned-To drop-down?
ST> Well, what I had in mind was providing a feature where any
ST> registered User could register themselves as Developer (see
ST> issue284).
ST> The other thing I should do is add the logged-in user to that menu
ST> (new issue296, flagged "urgent").
Yes, either of those would be sufficient, I think.
ST> I want Assigned-To to have at least minimal commitment semantics:
ST> somebody has accepted specific responsibility for it.
[...]
ST> Even though package maintainers have accepted responsibility for
ST> their packages, I don't think package maintainers need to be
ST> qualified to *fix* bugs. They just need to know who can fix them,
ST> and how to find those people.
Indeed, but I think this begs the question of what does it mean for
someone to take resposibility for a bug. It could mean responsibility
for driving a discussion with the upstream package provider and getting
the issue resolved that way. And in that sense I'd be fine with having
package maintainers assigned to issues in any of their packages.
OTOH, I expect some percentage of bugs will get filed against the wrong
module, and package maintainers might not always be qualified to
determine where the bug really resides and who ought to own it.
So on whole, I think your current plan (address issue284, issue296) is
fine.
cheers,
mike
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
11:35 p.m.
mike.kupfer(a)xemacs.org writes:
>>>>> "ST" == Stephen J Turnbull
<stephen(a)xemacs.org> writes:
ST> Even though package maintainers have accepted responsibility
for
ST> their packages, I don't think package maintainers need to be
ST> qualified to *fix* bugs. They just need to know who can fix them,
ST> and how to find those people.
Indeed, but I think this begs the question of what does it mean for
someone to take resposibility for a bug.
What I mean by that is someone who, at lest when asked, will say
whether or not code (etc) will get written, and when. A developer can
do that; that's what it means to be open source. Other contributors,
including package maintainers, may not want to commit to it.
It could mean responsibility for driving a discussion with the
upstream package provider and getting the issue resolved that way.
And in that sense I'd be fine with having package maintainers
assigned to issues in any of their packages.
I would, too. But not all maintainers are in a position to actually
drive discussion. My proposal is to leave that judgment up to the
maintainer himself.
So on whole, I think your current plan (address issue284, issue296)
is
fine.
Good. If you have any ideas, feel free to let me know.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
6:09 p.m.
Is the URL of the XEmacs Tracker itself http://tracker.xemacs.org? If
so, something's amiss because I don't get anything that looks like a
bug tracker. (I can access the User Guide without problem.)
--- Vladimir
on 02/11/2008 12:19 AM Stephen J. Turnbull said the following:
There are currently 200 open issues in the tracker. Of these, more
than half have no priority or severity set. We would greatly
appreciate it if volunteers would help classify these issues. You can
do as many or as few as you like.
As a small incentive, normally the "priority" attribute is property of
the Reviewers and/or the developer who takes responsibility for the
issue, but for unclassified issues I encourage you to set the priority.
Basically, to help you just register your user or get a password reset
if you've been automatically registered by one of the "pre-loaded"
issues, read the documentation at
http://tracker.xemacs.org/XEmacs/its/user_guide.html#issue-triage-guidelines
and get started!
Thanks in advance to all volunteers, and thanks to everybody for your
support of XEmacs!
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
--
Vladimir G. Ivanovic
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
3:23 a.m.
Vladimir G. Ivanovic writes:
Is the URL of the XEmacs Tracker itself http://tracker.xemacs.org? If
so, something's amiss because I don't get anything that looks like a
bug tracker. (I can access the User Guide without problem.)
Amazingly enough, the User Guide doesn't mention the correct URL
... fixed now. Thanks for the report.
No, the correct URL is http://tracker.xemacs.org/XEmacs/its/.
Roundup needs a non-root path. I need to do some Apache magic to
redirect from root to the non-root URL, I guess.
AFAIK this is trivial, but advice is welcome. Here's the problem.
A Roundup daemon can handle several trackers at the same. The way to
tell the daemon about a tracker to serve is
roundup-server tracker-name=/path/to/tracker/data
and it serves the URL
http://tracker-host.net/base-path/tracker-name/
(base-path can be null). It really wants that tracker-name on the end
of the URL AFAICT. I guess just a mod_rewrite rule that redirects
"^/$" to "/XEmacs/its/" should work?
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
6:49 a.m.
--- "Stephen J. Turnbull" <stephen(a)xemacs.org> wrote:
Vladimir G. Ivanovic writes:
> Is the URL of the XEmacs Tracker itself http://tracker.xemacs.org?
If
> so, something's amiss because I don't get anything that looks like
a
> bug tracker. (I can access the User Guide without problem.)
Amazingly enough, the User Guide doesn't mention the correct URL
... fixed now. Thanks for the report.
No, the correct URL is http://tracker.xemacs.org/XEmacs/its/.
Roundup needs a non-root path. I need to do some Apache magic to
redirect from root to the non-root URL, I guess.
AFAIK this is trivial, but advice is welcome. Here's the problem.
A Roundup daemon can handle several trackers at the same. The way to
tell the daemon about a tracker to serve is
roundup-server tracker-name=/path/to/tracker/data
and it serves the URL
http://tracker-host.net/base-path/tracker-name/
(base-path can be null). It really wants that tracker-name on the
end
of the URL AFAICT. I guess just a mod_rewrite rule that redirects
"^/$" to "/XEmacs/its/" should work?
I think a redirectmatch will help:
---- >8 ----
RedirectMatch ^/$ /XEmacs/its/
---- 8< ----
And if you want apache to serve(to make use of the sendfile()
function)static htdoc documents inside the XEmacs/its virtual hierarchy
(eg. roundup help guide XEmacs/its/＠(a)file/xxx.html ) then you can use
mod_rewrite:
---- >8 ----
# Service static contents by mod_alias and mod_rewrite
Alias /roundup-htdocs /path/to/the/roundup/static/htdocs
<Directory "/path/to/the/roundup/static/htdocs">
Order allow,deny
Allow from all
</Directory>
RewriteEngine on
RewriteRule ^/XEmacs/its/＠(a)file/(.*)$ /trac-htdocs/$2 [PT]
---- 8< ----
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now.
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
6:57 a.m.
Sorry, in my previrus mail
the last $2 should be $1
____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
6121
days inactive
6129
days old
18 comments
9 participants
participants (9)
-
Adrian Aichner -
Andreas Röhler -
Eric Knauel -
FKtPp -
Mike Kupfer -
Skip Montanaro -
Stephen J. Turnbull -
The XEmacs Package Smoketest -
Vladimir G. Ivanovic