On Tue, Mar 16, 2010 at 11:38 AM, Dennis Gilmore <[email protected]> wrote: > Hi All, > > I wanted to put out there the plan for EL-6 branching and building. > > > whenever EL-6 beta is announced we will setup the base repos for building. > > we will also announce our intention to branch. > > Every package that is not orphaned in EL-5 will be branched for EL-6. there > will be an opt-out. place a file in your EL-5 branch called nobranch and > place in it the reason why. > > for instance python-hashlib is in EL-5 to support stronger hashed metadata for > the buildsystem. its part of newer pythons so my nobranch file will contain > "Exists in newer python" this is just a historical something so if someone > down the road questions why they can go and see > > We will give 2 weeks from announcement before we setup the cvs branches. this > will let us make sure anything thats in EL-6 gets nobranch files we will be > branching EL-6 branches from F-12 branches
Looks good. During that 2 Weeks is there anything we should do if people want to add stuff from F12 branches to EPEL-6? [EG they don't want to support for 4 or 5 but 6 looks good.] -- Stephen J Smoogen. Ah, but a man's reach should exceed his grasp. Or what's a heaven for? -- Robert Browning _______________________________________________ epel-devel-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/epel-devel-list
