Re: [Mesa3d-dev] Mesa 7.5 plans
It looks I'll be postponing the 7.5 release until next week... -Brian -- This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com ___ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
Re: [Mesa3d-dev] Mesa 7.5 plans
Brian Paul wrote: It looks I'll be postponing the 7.5 release until next week... -Brian I've managed to get r300 into a state where it would probably not be harmful, provided that softpipe is the default pipe for the radeon winsys. I'll patch it up to reflect that; please disregard my earlier mail. ~ C. -- This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com ___ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
Re: [Mesa3d-dev] Mesa 7.5 plans
Ian Romanick wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian Paul wrote: Dave Airlie wrote: I'm looking at making the 7.5 release on Friday. The main objective of this development release will be an initial milestone / roll-out of the Gallium bits. Then, I'd like to quickly create the Mesa 7.6 branch for stabilization. git/master will then again be open to any/all development. If this is too soon for anyone, let me know so we can work something out. I also think a 7.4.1 release will happen soon. 7.4 had a bit of a regression in the glTexParameter() code which Roland found/fixed. Plus there's some other useful bug fixes on the 7.4 branch. I'd really like to merge the radeon-rewrite branch sooner rather than later, however I still think DRI2 needs some more work and I'd hate to have us release something where the interfaces haven't settled, I'd at least like to see front buffer rendering working so we run test suites on it. I guess another option is to create a 7.6/stable branch on Friday, but not make the 7.5 release for a little bit. That would give us a stable branch for our work while leaving master as-is. There's no rule that 7.5 must be released before we start 7.6/stable. This is something that I've been wanting to discuss for some time. I think we should slightly adjust our release process. My suggestion is: * Decide on a cut-off date for new features in master. * At that cut-off date, make a branch for the next 7.n release. * Allow bug fixes, testing, etc. on that branch for some period. * Make the 7.n release. * Continue making bug fixes and, perhaps, low-impact new device support to that branch for the next 7.n.m release. This basically means that we'd do Mesa 7.5 really soon, and follow that with Mesa 7.5.1 in a few weeks. Mesa 7.5.1 is, basically, what Mesa 7.6 would have been. I believe that we should establish at least a loose policy of which 7.n branches we intend to maintain. Opinions? Yes, I could go with that. With git it's a lot easier to manage branches than it was with CVS and I'm not sure the whole stable vs. development version model is that useful anymore. The Mesa development releases haven't been *that* unstable. People especially concerned about stability could just wait for X.Y.1 versions. If nobody argues otherwise, I'm inclined to follow your suggestion, Ian. Any other opinions? -Brian -- This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com ___ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
Re: [Mesa3d-dev] Mesa 7.5 plans
Dave Airlie wrote: I'm looking at making the 7.5 release on Friday. The main objective of this development release will be an initial milestone / roll-out of the Gallium bits. Then, I'd like to quickly create the Mesa 7.6 branch for stabilization. git/master will then again be open to any/all development. If this is too soon for anyone, let me know so we can work something out. I also think a 7.4.1 release will happen soon. 7.4 had a bit of a regression in the glTexParameter() code which Roland found/fixed. Plus there's some other useful bug fixes on the 7.4 branch. I'd really like to merge the radeon-rewrite branch sooner rather than later, however I still think DRI2 needs some more work and I'd hate to have us release something where the interfaces haven't settled, I'd at least like to see front buffer rendering working so we run test suites on it. I guess another option is to create a 7.6/stable branch on Friday, but not make the 7.5 release for a little bit. That would give us a stable branch for our work while leaving master as-is. There's no rule that 7.5 must be released before we start 7.6/stable. -Brian -- This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com ___ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
[Mesa3d-dev] Mesa 7.5 plans
I'm looking at making the 7.5 release on Friday. The main objective of this development release will be an initial milestone / roll-out of the Gallium bits. Then, I'd like to quickly create the Mesa 7.6 branch for stabilization. git/master will then again be open to any/all development. If this is too soon for anyone, let me know so we can work something out. I also think a 7.4.1 release will happen soon. 7.4 had a bit of a regression in the glTexParameter() code which Roland found/fixed. Plus there's some other useful bug fixes on the 7.4 branch. -Brian -- This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com ___ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
Re: [Mesa3d-dev] Mesa 7.5 plans
Brian Paul wrote: I'm looking at making the 7.5 release on Friday. The main objective of this development release will be an initial milestone / roll-out of the Gallium bits. Then, I'd like to quickly create the Mesa 7.6 branch for stabilization. git/master will then again be open to any/all development. If this is too soon for anyone, let me know so we can work something out. I also think a 7.4.1 release will happen soon. 7.4 had a bit of a regression in the glTexParameter() code which Roland found/fixed. Plus there's some other useful bug fixes on the 7.4 branch. Unless there is a compelling reason to do otherwise, can we refrain from shipping the r300 pipe, and patch radeon winsys to be softpipe-only? I really do not feel comfortable shipping r300-gallium since I am sure that people will try to use it and end up quite disappointed. ~ C. -- This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com ___ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
Re: [Mesa3d-dev] Mesa 7.5 plans
On Tue, Apr 7, 2009 at 6:42 PM, Corbin Simpson mostawesomed...@gmail.com wrote: Brian Paul wrote: I'm looking at making the 7.5 release on Friday. The main objective of this development release will be an initial milestone / roll-out of the Gallium bits. Then, I'd like to quickly create the Mesa 7.6 branch for stabilization. git/master will then again be open to any/all development. If this is too soon for anyone, let me know so we can work something out. I also think a 7.4.1 release will happen soon. 7.4 had a bit of a regression in the glTexParameter() code which Roland found/fixed. Plus there's some other useful bug fixes on the 7.4 branch. Unless there is a compelling reason to do otherwise, can we refrain from shipping the r300 pipe, and patch radeon winsys to be softpipe-only? I really do not feel comfortable shipping r300-gallium since I am sure that people will try to use it and end up quite disappointed. Sure, no problem. -Brian -- This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com ___ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
Re: [Mesa3d-dev] Mesa 7.5 plans
I'm looking at making the 7.5 release on Friday. The main objective of this development release will be an initial milestone / roll-out of the Gallium bits. Then, I'd like to quickly create the Mesa 7.6 branch for stabilization. git/master will then again be open to any/all development. If this is too soon for anyone, let me know so we can work something out. I also think a 7.4.1 release will happen soon. 7.4 had a bit of a regression in the glTexParameter() code which Roland found/fixed. Plus there's some other useful bug fixes on the 7.4 branch. I'd really like to merge the radeon-rewrite branch sooner rather than later, however I still think DRI2 needs some more work and I'd hate to have us release something where the interfaces haven't settled, I'd at least like to see front buffer rendering working so we run test suites on it. Dave. -- This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com ___ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
