On 9/14/2013 02:45, Ozkan Sezer wrote: > On 9/13/13, Kai Tietz wrote: >> Well, I consider, if we might want to define _FORCENAMELESSUNION in >> _mingw.h for 3.0, and remove it on our trunk. By this we reduce >> fallout right now, provide a version check later on for changed >> behavior. > > I don't know the specifics about that fallout, but is it impossible that > defining that would cause another fallout? >
Alternative, we postpone dealing with it until v4, branch now and revert the changes in v3 so _FORCENAMELESSUNION is not needed. >> >> By this experience - as it must be possible to modify things on our >> trunk and our release cycle can take more then a year - I would >> encourage to change our habit of seeing trunk as release-branch. It >> has shown here, that this causes simply troubles on evolution. >> >> JonY, Jacek, Ozkan, your opion about this suggestion? >> >> Regards, >> Kai > > We will need more regular releases with safe changes merged in > and only unsafe stuff kept in devel branch (versus keeping new features > in devel branch and not merging back.) That might prevent people, to > some degree, from using trunk as if it is a release branch. Trunk is already the devel branch, /stable/* is for stable users. what we could do is make a new "/testing" that constantly have safe and proven changes merged from /trunk, kind of like debian-testing, where trunk is Sid unstable.
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ How ServiceNow helps IT people transform IT departments: 1. Consolidate legacy IT systems to a single system of record for IT 2. Standardize and globalize service processes across IT 3. Implement zero-touch automation to replace manual, redundant tasks http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk
_______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
