Any idea on timing of 4U2? Reason being is https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=140002 and a pair of DPT SmartRAID V Milleniums. -- Lamar Owen Director of Information Technology Pisgah Astronomical Research Institute 1 PARI Drive Rosman, NC 28772 (828)862-5554 www.pari.edu
On Wed, 2005-09-14 at 17:54 -0400, Lamar Owen wrote:> Any idea on timing of 4U2? > > Reason being is https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=140002 > and a pair of DPT SmartRAID V Milleniums.The end of the beta period for el4u2 is tomorrow. The upstream provider usually releases their official product 1-4 weeks after the end of that period. We usually release our first arch (i386) with a week of the upstream release and our other arches within a week after the first arch release. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://lists.centos.org/pipermail/centos/attachments/20050914/be41607f/attachment.sig>
Lamar Owen wrote:> Any idea on timing of 4U2? > > Reason being is > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=140002 > and a pair of DPT SmartRAID V Milleniums.If you are really anxious... http://people.redhat.com/~jbaron/rhel4/ (from specfile) * Thu Jun 2 2005 Dave Jones <davej at redhat.com> [2.6.9-11.1] - U2 begin. ... - Increase i2o_block timeout, fixing installs with Adaptec 2400A (#140002) Greg
> On Wed, 2005-09-14 at 17:54 -0400, Lamar Owen wrote: >> Any idea on timing of 4U2?> The end of the beta period for el4u2 is tomorrow. The upstream provider > usually releases their official product 1-4 weeks after the end of that > period.> We usually release our first arch (i386) with a week of the upstream > release and our other arches within a week after the first arch release.2-5 weeks. Ok. I'll try the prelim RHEL kernel first; should be pretty close. Many thanks! -- Lamar Owen Director of Information Technology Pisgah Astronomical Research Institute 1 PARI Drive Rosman, NC 28772 (828)862-5554 www.pari.edu
Hi, On Wed, Sep 14, 2005 at 05:52:15PM -0500, Johnny Hughes wrote:> > We usually release our first arch (i386) with a week of the upstream > release and our other arches within a week after the first arch release. >I find it a bit offensive when it's brough out as it is above. It really should be 'we have a policy of releasing i386 first even when anything else would be ready before'. -- Pasi Pirhonen - upi at iki.fi - http://iki.fi/upi/
Also, Upi, people need more than work, they need work patterns. Making arch releases in a particular order is safer than an 'as available' order in many cases. So the particular order is 'i386 first'. If you were a (co)developer/tester/maintainer/distributor, your work pattern would be significant. So: Help row the boat, or (happily) enjoy the scenery. Brian Brunner brian.t.brunner at gai-tronics.com (610)796-5838>>> Jay.Hilliard at disney.com 09/15/05 01:47AM >>>Pasi Pirhonen wrote:> Hi, > > > On Wed, Sep 14, 2005 at 05:52:15PM -0500, Johnny Hughes wrote: > >>We usually release our first arch (i386) with a week of the upstream >>release and our other arches within a week after the first arch release. >> > > > I find it a bit offensive when it's brough out as it is above. > It really should be 'we have a policy of releasing i386 first > even when anything else would be ready before'. >Well, I appreciate the efforts of Johnny H. and if it takes a week or two, regardless of ARCH, so be it. He's doing a lot. What happens if he needs an extended vacation? He *is* CentOS, you know (that's not sarcasm). -- Jay _______________________________________________ CentOS mailing list CentOS at centos.org http://lists.centos.org/mailman/listinfo/centos ******************************************************************* This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept for the presence of computer viruses. www.hubbell.com - Hubbell Incorporated