Re: gEDA-user: Users of verilog and VHDL gnetlist backends -=(BREAKAGE IN 1.4.0)=-

[Ales Hvezda <ahvezda@xxxxxxxxxxxxxx>]

[snip]
>IMHO, if you intend to change globally something, then there should be
>clearly posted RFCs for them, so that people do not have to check
>every changes you made which should normally not affect them.

	Actually PeterC did post a RFC and it was more than sufficient:

http://archives.seul.org/geda/dev/Jan-2008/msg00058.html

	Everybody is free to submit their comments to such threads.

	I'm not about to institute a full blown "RFC required policy"
for every change that might affect users.  The verilog/vhdl breakage was
unfortunate, but its just a fixable bug (live and learn; and we need
to improve the test suite).  I'm not going to worry about it.  Also,
_not_ one person complained about this breakage during the 1.3.x cycle so
that make me worry even less.

	The only time I would like to see RFC is when developers want
to change something drastic.  And I'm not exempt from that either.

	It is not an accident that the current active developers have
push/write access to the repository.  I trust them all to do the right
thing(s) and no evil.

[snip]
>I would like to suggest a forum post "geda-RFC" similar to the
>"geda-announce", so that the RFCs which have global significance
>are clearly visible to everyone.  This is also a good way to
>avoid unintended mistakes.
>

	That's a bit on the overkill side.  We have the mailing lists
and wiki for that purpose.

								-Ales



_______________________________________________
geda-user mailing list
geda-user@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user