On Mon, Jan 09, 2006 at 04:11:25PM +0000, Karanbir Singh enlightened us: > Jim Perrin wrote: > >>If you want feedback through bugs.centos.org, I would suggest opening a > >>ticket when a new RPM (set) is created, and include the link in the > >>announcement so that there is one spot that gets feedback, not to mention > >>it > >>will help you track how long that software has been available, etc. > > > > > >Agreed. Only about half of the things I've added to the repo have a > >ticket associated with them. Anyone else have opinions on the matter, > >or should this become the standard thing? > > > > lets make it standard, one issue number for each package set ( = per > .src.rpm ? ). > Almost = per .src.rpm, but the recent postgres 8.1 stuff is a good example where there are at least 2 .src.rpms (compat-libs, postgres) for what I would consider a single "set". > And going with the state of things, since we share source evenly over > the various Arch's - we wont need to open issues for each arch. Which is very convenient :-) Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263