gEDA-user: Launchpad: pcb next-bug-release
Hi all, On https://launchpad.net/pcb/+milestone/next-bug-release I see some bugs marked with the status fix-released. IMO these should aleady be included in the latest release of pcb (20100929) and not in the list for the pending bug release, or should have the status fix commited. Could anyone please give some clarification ? Let us avoid unnecessary rework on the status of bugs before these bugs drop out of sight. Kind regards, Bert Timmerman. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Launchpad: pcb next-bug-release
On Saturday 08 January 2011 10:16:48 Bert Timmerman wrote: Hi all, On https://launchpad.net/pcb/+milestone/next-bug-release I see some bugs marked with the status fix-released. IMO these should aleady be included in the latest release of pcb (20100929) and not in the list for the pending bug release, or should have the status fix commited. Could anyone please give some clarification ? Let us avoid unnecessary rework on the status of bugs before these bugs drop out of sight. Yes, as I understand it they should have the status fix committed if the fixes haven't yet appeared in a release. Cheers, Peter -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre signature.asc Description: This is a digitally signed message part. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Apply to join the geda-bugs team to triage bugs...
sorry, I see the prios differently: Peter Clifton wrote: Crasher / data loss - High (or perhaps even Critical if it is likely to be hit). depends on type of data loss: high if recent changes disappear, critical if the design vanishes (I know, the later is near impossible with move/write on saves) It also depends if the data loss is immediately evident - if not it's worse. Board output fault this is a catastrophic failure in a production environment or incorrect netlist likely to cause design breakage to my understanding an incorrect net will cause a design break with 100.0% likelihood - critical error UI wart / cosmetics - Low what is a wart ? freezes, hickups of state engine: medium button should be more to the left = cosmetic: low ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
gEDA-user: Icarus Verilog: $setup, $hold, $width
Hello, I wish to know if $setup, $hold and $width tasks of specify blocks are implemented in Icarus verilog v0.9.3. If they are implemented, where can I view the violations raised by them? Thanks, Edwards ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
gEDA-user: Launchpad bug managment by email
Just to make people aware, it is possible to do bug management on Launchpad via email - if that suits you better. See: https://help.launchpad.net/Bugs/EmailInterface Note that it requires you to GPG sign your messages in order to prove who you are. Best wishes, -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me) ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Symbol question - suggestions?
On Jan 7, 2011, at 4:06 AM, Johnny Rosenberg wrote: So, if I decide to use a 74-power symbol after all, is there any way I can design it making it automatically understand where it belongs, so I don't need to manually enter all those ”U1, U2, U3” und so weiter? If I wanted a lot of work, I could draw my components with a pen on a piece of paper and then scan the whole thing… Perhaps you want symbols with hidden power pins. They're not as flexible as putting in the power symbols explicitly, but they may be right for your application. In my applications, I often have multiple power nets, so it is essential to be explicit. John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ j...@noqsi.com ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Bug triage
On 7 January 2011 10:14, Peter Clifton pc...@cam.ac.uk wrote: Pick a bug from here: https://launchpad.net/geda/+bugs?search=Searchfield.status=New (gEDA) or: https://launchpad.net/pcb/+bugs?search=Searchfield.status=New (pcb) Grab git HEAD of whichever package the bug is in (if you don't have it already), and try to confirm whether the bug is still present or not. Bug present: New - Confirmed Bug absent: Make a comment - set bug to Invalid, Fix released, or Incomplete... depending on how confident you are that the bug was bogus, fixed by some commit since the bug reported, or Incomplete if you ask the reporter a question which requires answering. Does it make sense to move (other peoples) Wishlist items to Confirmed, or just leave them as New? Just thinking these might be a lot more subjective than bug reports. Cheers Gareth ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Bug triage
On Sat, 2011-01-08 at 19:16 +, Gareth Edwards wrote: Does it make sense to move (other peoples) Wishlist items to Confirmed, or just leave them as New? Just thinking these might be a lot more subjective than bug reports. I'd suggest that anyone who also wishes the same should tick the bug affects me option, so we get an idea of the demand. That feature was designed to avoid lots of ME TOO, +1 comments on bugs. Perhaps leave the status update for developers who are sufficiently familiar with the design issues to decide if the wishlist item is a Confirmed, WontFix or Opinion. It seems there is no need to confirm that someone wishes something ;) -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me) ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Symbol question - suggestions?
Den 2011-01-08 16:33:06 skrev John Doty j...@noqsi.com: On Jan 7, 2011, at 4:06 AM, Johnny Rosenberg wrote: So, if I decide to use a 74-power symbol after all, is there any way I can design it making it automatically understand where it belongs, so I don't need to manually enter all those ”U1, U2, U3” und so weiter? If I wanted a lot of work, I could draw my components with a pen on a piece of paper and then scan the whole thing… Perhaps you want symbols with hidden power pins. They're not as flexible as putting in the power symbols explicitly, but they may be right for your application. In my applications, I often have multiple power nets, so it is essential to be explicit. John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ j...@noqsi.com You mean like the default symbols with lines like the following? net=Vcc:14 net=GND:7 -- Kind regards Johnny Rosenberg ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Bug triage
On Saturday 08 January 2011 19:33:40 Gareth Edwards wrote: On 8 January 2011 19:28, Peter Clifton pc...@cam.ac.uk wrote: On Sat, 2011-01-08 at 19:16 +, Gareth Edwards wrote: Does it make sense to move (other peoples) Wishlist items to Confirmed, or just leave them as New? Just thinking these might be a lot more subjective than bug reports. I'd suggest that anyone who also wishes the same should tick the bug affects me option, so we get an idea of the demand. That feature was designed to avoid lots of ME TOO, +1 comments on bugs. Perhaps leave the status update for developers who are sufficiently familiar with the design issues to decide if the wishlist item is a Confirmed, WontFix or Opinion. Yes, this sound like a good process. Think it's worthwhile me trying to capture the process on the wiki somewhere or is it transient until we complete the first pass of the migration? It's spread over 3 or 4 email threads now and my email filing sucks. :) Yes, it is definitely worthwhile to try and capture the process on the wiki somewhere! Very much so! Please do! Peter :-) -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre signature.asc Description: This is a digitally signed message part. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Symbol question - suggestions?
On Jan 8, 2011, at 12:28 PM, Johnny Rosenberg wrote: Den 2011-01-08 16:33:06 skrev John Doty j...@noqsi.com: On Jan 7, 2011, at 4:06 AM, Johnny Rosenberg wrote: So, if I decide to use a 74-power symbol after all, is there any way I can design it making it automatically understand where it belongs, so I don't need to manually enter all those ”U1, U2, U3” und so weiter? If I wanted a lot of work, I could draw my components with a pen on a piece of paper and then scan the whole thing… Perhaps you want symbols with hidden power pins. They're not as flexible as putting in the power symbols explicitly, but they may be right for your application. In my applications, I often have multiple power nets, so it is essential to be explicit. John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ j...@noqsi.com You mean like the default symbols with lines like the following? net=Vcc:14 net=GND:7 Yes. John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ j...@noqsi.com ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Bug triage
On Sat, 2011-01-08 at 19:33 +, Gareth Edwards wrote: Think it's worthwhile me trying to capture the process on the wiki somewhere or is it transient until we complete the first pass of the migration? It's spread over 3 or 4 email threads now and my email filing sucks. :) Writing a bug triage guide would be handy I think.. thanks! We can update it if and when we find problems with how things are working. Realistically, the migration is done already.. we are just catching up with bug triage work which has been very neglected in the past. I'm currently working on writing a robot to update status of bugs as we commit related code. See: https://bugs.launchpad.net/pcb/+bug/700413 and our mindless helper: https://launchpad.net/~gpleda-launchpad-robot -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me) ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Symbol question - suggestions?
Den 2011-01-08 20:39:41 skrev John Doty j...@noqsi.com: On Jan 8, 2011, at 12:28 PM, Johnny Rosenberg wrote: Den 2011-01-08 16:33:06 skrev John Doty j...@noqsi.com: On Jan 7, 2011, at 4:06 AM, Johnny Rosenberg wrote: So, if I decide to use a 74-power symbol after all, is there any way I can design it making it automatically understand where it belongs, so I don't need to manually enter all those ”U1, U2, U3” und so weiter? If I wanted a lot of work, I could draw my components with a pen on a piece of paper and then scan the whole thing… Perhaps you want symbols with hidden power pins. They're not as flexible as putting in the power symbols explicitly, but they may be right for your application. In my applications, I often have multiple power nets, so it is essential to be explicit. John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ j...@noqsi.com You mean like the default symbols with lines like the following? net=Vcc:14 net=GND:7 Yes. John Doty Well, I think that would work best for what I'm doing. I think I will go that way, at least until I run into some kind of case where this does not work… Maybe my symbols won't be interesting then for anybody else than me, but it doesn't hurt to share them anyway, I guess. I could include some kind of warning, I guess. -- Kind regards Johnny Rosenberg ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Bug triage
On Sat, 08 Jan 2011 19:40:49 + Peter Clifton pc...@cam.ac.uk wrote: On Sat, 2011-01-08 at 19:33 +, Gareth Edwards wrote: Writing a bug triage guide would be handy I think.. thanks! We can update it if and when we find problems with how things are working. Yes, it would be useful to have a bug triage guide. Realistically, the migration is done already.. we are just catching up with bug triage work which has been very neglected in the past. I'll just take this moment to say thanks for making the switch to Launchpad! I've used Launchpad a little bit in the past, but after using it for only a little while with the pcb project, I find using Launchpad EXTREMELY PLEASANT! ... especially compared with SourceForge. Regards, Colin ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Bug triage
Gareth Edwards wrote: Think it's worthwhile me trying to capture the process on the wiki somewhere IMHO, bug reporting is worth a dedicated page in the wiki. I just started one at: http://geda.seul.org/wiki/geda:howto_report_bugs?#bug_trackers Feel free to add a section on bug triage and etiquette. BTW, there about 100 links to source forge in the wiki http://geda.seul.org/wiki/?do=searchid=sourceforge Many of them are obsolete since pcb and now also the bug trackers have moved somewhere else. I'll try to catch them... ---)kaimartin(--- -- Kai-Martin Knaak Email: k...@familieknaak.de Öffentlicher PGP-Schlüssel: http://pool.sks-keyservers.net:11371/pks/lookup?search=0x6C0B9F53 ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Bug triage
Hi On 8 January 2011 21:26, Kai-Martin Knaak k...@lilalaser.de wrote: Gareth Edwards wrote: Think it's worthwhile me trying to capture the process on the wiki somewhere IMHO, bug reporting is worth a dedicated page in the wiki. I just started one at: http://geda.seul.org/wiki/geda:howto_report_bugs?#bug_trackers Feel free to add a section on bug triage and etiquette. I'm already half way through writing one elsewhere. I'll add a link. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Bug triage
On Saturday 08 January 2011 21:26:59 Kai-Martin Knaak wrote: Gareth Edwards wrote: Think it's worthwhile me trying to capture the process on the wiki somewhere IMHO, bug reporting is worth a dedicated page in the wiki. I just started one at: http://geda.seul.org/wiki/geda:howto_report_bugs?#bug_trackers Feel free to add a section on bug triage and etiquette. BTW, there about 100 links to source forge in the wiki http://geda.seul.org/wiki/?do=searchid=sourceforge Many of them are obsolete since pcb and now also the bug trackers have moved somewhere else. I'll try to catch them... Note that http://bugs.launchpad.net/geda/+bug/sf-bugnum links to the bug which had ID bugnum on Sourceforge. This is useful. ;-) Peter -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre signature.asc Description: This is a digitally signed message part. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Bug triage
Kai-Martin Knaak wrote: BTW, there about 100 links to source forge in the wiki http://geda.seul.org/wiki/?do=searchid=sourceforge Many of them are obsolete since pcb and now also the bug trackers have moved somewhere else. I'll try to catch them... The hunt led me to http://pcb.gpleda.org/bugs.html This page needs to be updated, too. It is not part of the wiki. So DJ, Ales, or somebody else with privileged write permissions has to do the changes. ---)kaimartin(--- -- Kai-Martin Knaak Email: k...@familieknaak.de Öffentlicher PGP-Schlüssel: http://pool.sks-keyservers.net:11371/pks/lookup?search=0x6C0B9F53 ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
gEDA-user: Clearance of polygons around tracks/pins/pads
Sorry for the noise, but even extended googling didn't show me how to set the clearance around tracks, pins and pads. I've found the related DRC preference, I'm aware of the K key to change it for single elements, but what I want is a preference, setting the clearance for all elements. Is this possible? Thanks, Markus - - - - - - - - - - - - - - - - - - - Dipl. Ing. (FH) Markus Hitter http://www.jump-ing.de/ ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Clearance of polygons around tracks/pins/pads
On Sat, Jan 8, 2011 at 3:44 PM, Markus Hitter m...@jump-ing.de wrote: Sorry for the noise, but even extended googling didn't show me how to set the clearance around tracks, pins and pads. I've found the related DRC preference, I'm aware of the K key to change it for single elements, but what I want is a preference, setting the clearance for all elements. Is this possible? Select all, then use the :ChangeClearSize action. Regards, Mark markra...@gmail -- Mark Rages, Engineer Midwest Telecine LLC markra...@midwesttelecine.com ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Clearance of polygons around tracks/pins/pads
Mark Rages wrote: On Sat, Jan 8, 2011 at 3:44 PM, Markus Hitter but even extended googling didn't show me how to set the clearance around tracks, pins and pads. I've found the related DRC preference, I'm aware of the K key to change it for single elements, but what I want is a preference, setting the clearance for all elements. Is this possible? Select all, then use the :ChangeClearSize action. ack. see: http://geda.seul.org/wiki/geda:pcb_tips#how_do_i_change_polygon_clearance ---)kaimartin(--- -- Kai-Martin Knaak Email: k...@familieknaak.de Öffentlicher PGP-Schlüssel: http://pool.sks-keyservers.net:11371/pks/lookup?search=0x6C0B9F53 ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Bug triage
On 8 January 2011 21:29, Gareth Edwards gar...@edwardsfamily.org.uk wrote: Think it's worthwhile me trying to capture the process on the wiki somewhere http://geda.seul.org/wiki/geda:bug_triage_guide ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Bug triage
On Saturday 08 January 2011 22:44:48 Kai-Martin Knaak wrote: Gareth Edwards wrote: http://geda.seul.org/wiki/geda:bug_triage_guide Nice. Would you object against a merge with Howto report bugs? I don't think that one is really needed -- reporting bugs and triaging bugs are different jobs. For instance, a large part of the triage guide is about what to set importances and statuses to in different situations, whereas for a reporter, their bug should always start out as New and Undecided. Peter -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre signature.asc Description: This is a digitally signed message part. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Bug triage
Peter TB Brett wrote: Nice. Would you object against a merge with Howto report bugs? I don't think that one is really needed -- reporting bugs and triaging bugs are different jobs. Sure, but I'd like to: 1) not spread bug reporting advice all over the site like we currently do. 2) suggest, that someone, who reports a bug may also confirm others. I imagine, this works better, if the triage 3) have a single page for all bug related issues. This page can be linked to from many other pages. (And potentially from the manuals). ---)kaimartin(--- -- Kai-Martin Knaak Email: k...@familieknaak.de Öffentlicher PGP-Schlüssel: http://pool.sks-keyservers.net:11371/pks/lookup?search=0x6C0B9F53 ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Bug triage
On Saturday 08 January 2011 23:31:43 Kai-Martin Knaak wrote: Peter TB Brett wrote: Nice. Would you object against a merge with Howto report bugs? I don't think that one is really needed -- reporting bugs and triaging bugs are different jobs. Sure, but I'd like to: 1) not spread bug reporting advice all over the site like we currently do. 2) suggest, that someone, who reports a bug may also confirm others. I imagine, this works better, if the triage 3) have a single page for all bug related issues. This page can be linked to from many other pages. (And potentially from the manuals). Well, it's up to you. Peter -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre signature.asc Description: This is a digitally signed message part. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Bug triage
On Sat, 2011-01-08 at 22:38 +0100, Kai-Martin Knaak wrote: Kai-Martin Knaak wrote: The hunt led me to http://pcb.gpleda.org/bugs.html This page needs to be updated, too. It is not part of the wiki. So DJ, Ales, or somebody else with privileged write permissions has to do the changes. I fixed it. -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me) ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Bug triage
Peter Clifton wrote: On Sat, 2011-01-08 at 22:38 +0100, Kai-Martin Knaak wrote: Kai-Martin Knaak wrote: The hunt led me to http://pcb.gpleda.org/bugs.html This page needs to be updated, too. It is not part of the wiki. So DJ, Ales, or somebody else with privileged write permissions has to do the changes. I fixed it. Thanks. Here is another find: http://geda.seul.org/wiki/gschem-projects On the bottom of the page is a link to sourceforge that is supposed to offer some work done for an interactive sub sheet generator. However, the link is dead. I couldn't locate a corresponding report on launchpad, either. Just typed in the bug number (1800913) in launchpads search facility. ---)kaimartin(--- -- Kai-Martin Knaak Email: k...@familieknaak.de Öffentlicher PGP-Schlüssel: http://pool.sks-keyservers.net:11371/pks/lookup?search=0x6C0B9F53 ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
