setup: Bug tracking services?
I find myself wishing for a bug tracker for setup. Is there any likelyhood of sources.redhat.com provided bug-trackers in the future? For now, I'm contemplating throwing a quick install of Bugzilla (or other software - suggestions very welcome in *private* mail) onto the student webserver at my college Max.
Re: setup: Bug tracking services?
Brian Ford schrieb: Did you see: http://cygwin.com/ml/cygwin/2004-10/msg00194.html ? Reini and I offered to co-maintain it if CGF decides to follow through. Sounds like you have another point in favor? Just setup has to be added as cygwin component at http://sources.redhat.com/bugzilla/ In the meantime I setup a webpage to collect the other known cygwin issues, which should then get into the docs and FAQ. http://www.mega-tokyo.com/osfaq2/index.php/CygwinIssues Not posted here yet, because it's far from complete. If some knowledgable would answer in detail or hint to ml answers it could get finished. All yet to me known answers are there. But I didn't do excessive googling. Kinda problematic if all old answers are already outdated. (as with select or PID's http://cygwin.com/cygwin-ug-net/highlights.html#OV-HI-PROCESS) -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/
Re: Bug tracking services?
On Wed, Oct 27, 2004 at 09:42:11AM -0500, Brian Ford wrote: On Wed, 27 Oct 2004, Max Bowsher wrote: I find myself wishing for a bug tracker for setup. Is there any likelyhood of sources.redhat.com provided bug-trackers in the future? For now, I'm contemplating throwing a quick install of Bugzilla (or other software - suggestions very welcome in *private* mail) onto the student webserver at my college Did you see: http://cygwin.com/ml/cygwin/2004-10/msg00194.html ? Reini and I offered to co-maintain it if CGF decides to follow through. Sounds like you have another point in favor? I've set up the categories for cygwin: http://sourceware.org/bugzilla/describecomponents.cgi?product=cygwin You can go to http://cygwin.com/bugzilla/ and get an account. setup.exe is a separate category, as is cygwin/x. Reini and Brian, please police this. All that I was asking for when I wanted someone to handle this was to have someone available to make sure that the lame entries did not get out of hand. If this is going to be anything like my experience with the cygwin to-do list, then it will be abused by people asking questions and by spammers trying to sell something. I don't think there should be any problems with either of you closing arbitrary bugs, moving them to the appropriate category, etc., but if there are, send the issues to cygwin-apps so that they can be archived. If this really takes off, I'll probably eventually gateway the bugzilla submissions info into a cygwin-bugs mailing list. cgf
Re: setup: Bug tracking services?
Reini Urban wrote: Just setup has to be added as cygwin component at http://sources.redhat.com/bugzilla/ Excellent! And someone already seems to have done that. I will start using it. People should feel free to file setup bugs themselves but *please* try to keep entries in the bugzilla to concise reproduction recipes and technical information. If in doubt, please use email, not bugzilla. Max.
Re: Bug tracking services?
On 2004-10-27T12:08-0400, Christopher Faylor wrote: ) http://sourceware.org/bugzilla/describecomponents.cgi?product=cygwin ) ) You can go to http://cygwin.com/bugzilla/ and get an account. setup.exe ) is a separate category, as is cygwin/x. Can we use this to submit new packages, updates, etc. as RFEs against either a distribution component or the existing Cygwin Applications component? For example, entries could be assigned to the package coordinator, with cygwin-apps@ on to the default Cc: list. Votes (if needed), problems, and reviews can be added as comments. The tools to determine package information from structured text could be adapted to pull directly from the back-end data base. (The mock-ups I made for a custom package-management site were originally modelled after Bugzilla.) -- Daniel Reed [EMAIL PROTECTED] http://people.redhat.com/djr/ http://naim.n.ml.org/ The open source world considers many of its large projects as benevolent dictatorships. It's a democracy only in the sense that cyberspace is infinite so anyone who doesn't like it can move out. -- Alan Cox
Re: Bug tracking services?
Daniel Reed wrote: On 2004-10-27T12:08-0400, Christopher Faylor wrote: ) http://sourceware.org/bugzilla/describecomponents.cgi?product=cygwin ) ) You can go to http://cygwin.com/bugzilla/ and get an account. setup.exe ) is a separate category, as is cygwin/x. Can we use this to submit new packages, updates, etc. as RFEs against either a distribution component or the existing Cygwin Applications component? My preferences can be summarized as: Do not use bugzilla for any task which can be completed within 24 hours. Bugzilla's value is the structured persistence of information for when tasks cannot be conveniently completed in one session in front of the computer. I don't see an advantage to using it where this is not required. Max.
Re: Bug tracking services?
I hate to cross post like this, but I think it's appropriate for the question posed... On Wed, 27 Oct 2004, Christopher Faylor wrote: I've set up the categories for cygwin: http://sourceware.org/bugzilla/describecomponents.cgi?product=cygwin Should the Default Owner be changed for Cygwin/X and setup.exe to Alex and Max respectively? Just curious... -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained pilot...
Re: Bug tracking services?
On 2004-10-27T19:19+0100, Max Bowsher wrote: ) Daniel Reed wrote: ) Can we use this to submit new packages, updates, etc. as RFEs against ) either ) a distribution component or the existing Cygwin Applications ) component? ) Bugzilla's value is the structured persistence of information for when tasks ) cannot be conveniently completed in one session in front of the computer. I ) don't see an advantage to using it where this is not required. For new packages, we have a lot of state to track. Package-specific information like descriptions, download URLs, etc.; distribution-specific information like votes, packaging problems and reviews, functionality reviews; misc. rhetoric on the merits of including a non-ubiquitous package in the distribution. In the past, I have tried to maintain a lot of this information in one central location, to periodically publish to the list. However, our packaging maintenance grew faster than our infrastructure, and the process of manually extracting information from mailing list traffic to put into a data base, only to later be re-presented to the mailing list, no longer makes sense. Updates might not have a definite need to be put into a long-term state-tracking system like Bugzilla, but I feel it would be beneficial to track new packages in such a system, and it might make sense to have all package-upload-relateted information kept in the same place (accessible by the same scripts). -- Daniel Reed [EMAIL PROTECTED] http://people.redhat.com/djr/ http://naim.n.ml.org/ What makes a man great? A man may be great in his aims, or in his achievements, or in both, but I think that man is truly great who makes the world his debtor... who does something for the world which the world needs and which nobody before him has done or known how to do. -- Rupert Gould [Longitude]
Re: Bug tracking services?
On 2004-10-27T14:10-0400, Daniel Reed wrote: ) (The mock-ups I made for a custom package-management site were originally ) modelled after Bugzilla.) The mock up is still available at http://shell.n.ml.org/n/package-maint/ -- Daniel Reed [EMAIL PROTECTED] http://people.redhat.com/djr/ http://naim.n.ml.org/ The best executive is the one who has sense enough to pick good men to do what he wants done, and self-restraint enough to keep from meddling with them while they do it. -- Theodore Roosevelt
Re: Bug tracking services?
On Wed, Oct 27, 2004 at 01:56:00PM -0500, Brian Ford wrote: I hate to cross post like this, but I think it's appropriate for the question posed... On Wed, 27 Oct 2004, Christopher Faylor wrote: I've set up the categories for cygwin: http://sourceware.org/bugzilla/describecomponents.cgi?product=cygwin Should the Default Owner be changed for Cygwin/X and setup.exe to Alex and Max respectively? Just curious... When everyone has accounts and has indicated assent, I will reassign the ownership of the groups. There is no reason to cross-post, btw. Alexander reads cygwin-apps. I asked for questions to go to cygwin-apps to minimize cross-list chatter, especially from people who aren't going to be responsible for dealing with entered bugs. I cross-posted to begin with because the people who would be entering bugs are not guaranteed to be reading cygwin-apps. cgf
Re: Bug tracking services?
Christopher Faylor schrieb: When everyone has accounts and has indicated assent, I will reassign the ownership of the groups. Ok. I do indicate assent, already have an account and already have the required perms, thanks. -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/
Re: Bug tracking services?
On Wed, Oct 27, 2004 at 09:42:11AM -0500, Brian Ford wrote: On Wed, 27 Oct 2004, Max Bowsher wrote: I find myself wishing for a bug tracker for setup. Is there any likelyhood of sources.redhat.com provided bug-trackers in the future? For now, I'm contemplating throwing a quick install of Bugzilla (or other software - suggestions very welcome in *private* mail) onto the student webserver at my college Did you see: http://cygwin.com/ml/cygwin/2004-10/msg00194.html ? Reini and I offered to co-maintain it if CGF decides to follow through. Sounds like you have another point in favor? I've set up the categories for cygwin: http://sourceware.org/bugzilla/describecomponents.cgi?product=cygwin You can go to http://cygwin.com/bugzilla/ and get an account. setup.exe is a separate category, as is cygwin/x. Reini and Brian, please police this. All that I was asking for when I wanted someone to handle this was to have someone available to make sure that the lame entries did not get out of hand. If this is going to be anything like my experience with the cygwin to-do list, then it will be abused by people asking questions and by spammers trying to sell something. I don't think there should be any problems with either of you closing arbitrary bugs, moving them to the appropriate category, etc., but if there are, send the issues to cygwin-apps so that they can be archived. If this really takes off, I'll probably eventually gateway the bugzilla submissions info into a cygwin-bugs mailing list. cgf
Re: Bug tracking services?
I hate to cross post like this, but I think it's appropriate for the question posed... On Wed, 27 Oct 2004, Christopher Faylor wrote: I've set up the categories for cygwin: http://sourceware.org/bugzilla/describecomponents.cgi?product=cygwin Should the Default Owner be changed for Cygwin/X and setup.exe to Alex and Max respectively? Just curious... -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained pilot...
Re: Bug tracking services?
On Wed, Oct 27, 2004 at 09:42:11AM -0500, Brian Ford wrote: On Wed, 27 Oct 2004, Max Bowsher wrote: I find myself wishing for a bug tracker for setup. Is there any likelyhood of sources.redhat.com provided bug-trackers in the future? For now, I'm contemplating throwing a quick install of Bugzilla (or other software - suggestions very welcome in *private* mail) onto the student webserver at my college Did you see: http://cygwin.com/ml/cygwin/2004-10/msg00194.html ? Reini and I offered to co-maintain it if CGF decides to follow through. Sounds like you have another point in favor? I've set up the categories for cygwin: http://sourceware.org/bugzilla/describecomponents.cgi?product=cygwin You can go to http://cygwin.com/bugzilla/ and get an account. setup.exe is a separate category, as is cygwin/x. Reini and Brian, please police this. All that I was asking for when I wanted someone to handle this was to have someone available to make sure that the lame entries did not get out of hand. If this is going to be anything like my experience with the cygwin to-do list, then it will be abused by people asking questions and by spammers trying to sell something. I don't think there should be any problems with either of you closing arbitrary bugs, moving them to the appropriate category, etc., but if there are, send the issues to cygwin-apps so that they can be archived. If this really takes off, I'll probably eventually gateway the bugzilla submissions info into a cygwin-bugs mailing list. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
