If you are using the c4-testing repository from http://dev.centos.org/ please consider providing feedback about the rpms you're using either here to the devel list with a quick email, or (my preference, but open for discussion/suggestions) via bugs.centos.org. We need the feedback for packages to be able to move them to centosplus, extras,addons, or where-ever else they're destined to go. Your feedback will help us to provide stable packages that benefit everyone.
-- Jim Perrin System Architect - UIT Ft Gordon & US Army Signal Center
On Mon, Jan 09, 2006 at 09:53:13AM -0500, Jim Perrin enlightened us:
If you are using the c4-testing repository from http://dev.centos.org/ please consider providing feedback about the rpms you're using either here to the devel list with a quick email, or (my preference, but open for discussion/suggestions) via bugs.centos.org. We need the feedback for packages to be able to move them to centosplus, extras,addons, or where-ever else they're destined to go. Your feedback will help us to provide stable packages that benefit everyone.
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.
Matt
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?
-- Jim Perrin System Architect - UIT Ft Gordon & US Army Signal Center
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?
That sounds like a great idea - especially as it probably prohibits doubled or tripled tickets for the same bug.
Ralph
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 ? ).
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.
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
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".
That hopefully won't happen again. I'm going to be checking out ways to make the two play nice and shove them both in the same src.rpm with some ifarch love. I'll take the blame for that one....
-- Jim Perrin System Architect - UIT Ft Gordon & US Army Signal Center
On Monday 09 January 2006 11:24, Jim Perrin wrote:
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".
That hopefully won't happen again. I'm going to be checking out ways to make the two play nice and shove them both in the same src.rpm with some ifarch love. I'll take the blame for that one....
Don't blame yourself for an upstream problem. The compat rpm should be a different src.rpm, but will need the entire previous PostgreSQL source tarball (previous -> officially supported).
On Mon, 2006-01-09 at 09:55 -0500, Matt Hyclak wrote:
On Mon, Jan 09, 2006 at 09:53:13AM -0500, Jim Perrin enlightened us:
If you are using the c4-testing repository from http://dev.centos.org/ please consider providing feedback about the rpms you're using either here to the devel list with a quick email, or (my preference, but open for discussion/suggestions) via bugs.centos.org. We need the feedback for packages to be able to move them to centosplus, extras,addons, or where-ever else they're destined to go. Your feedback will help us to provide stable packages that benefit everyone.
In order to get more testers/feedback, how about posting the availability of test packages (with appropriate caveats about the nature of the packages, and outlining desired bug-reporting procedures) to centos-announce@centos.org?
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.
Good idea. Looked for ticket entries on the firefox test version 1.5 I've been using and found nothing.
Either approach seems OK, or perhaps a combination - a bugs.centos.org report with details and an e-mail with a pointer to the report to devel list.
Phil
Phil Schaffner wrote:
On Mon, 2006-01-09 at 09:55 -0500, Matt Hyclak wrote:
If you are using the c4-testing repository from http://dev.centos.org/ please consider providing feedback about the rpms you're using either here to the devel list with a quick email, or (my preference, but open for discussion/suggestions) via bugs.centos.org. We need the feedback for packages to be able to move them to centosplus, extras,addons, or where-ever else they're destined to go. Your feedback will help us to provide stable packages that benefit everyone.
In order to get more testers/feedback, how about posting the availability of test packages (with appropriate caveats about the nature of the packages, and outlining desired bug-reporting procedures) to centos-announce@centos.org?
no! lets not post to centos-announce. Way too many people really dont want to know about these pkgs. They use CentOS for the stable == RHEL == someone supports it.
we *should*, however, be announcing these testing packages _here_ in centos-devel. I think we've done that previously.
-
Jim Perrin -
Karanbir Singh -
Lamar Owen -
Matt Hyclak -
Phil Schaffner -
Ralph Angenendt