On 08/08/2011 05:02 PM, Ruben Van Boxem wrote: > - What we agreed on about versioning: > --> mingw-w64 should adopt a semi-rolling release model. It's > source only, so (Linux) packagers should just pick a (release) branch > and use its latest revision.
it's a support nightmare! how can one know eg what does the 2.0 means if it's changes every days? eg what happened if someone report a bug which is already fixed in the git? imho there must be one and only one 2.0 tarball, but the git may have 2.0 and 2.1 branch/tag all changes in the 2.0 branch can be merged into 2.1 and any time can be release 2.0.1 if the developer don't thing it's time to 2.1 > --> binutils: latest trunk is the only sensible version does it means you always send all mingw/windows specific patches to binutils upstream and those are always merged? if not it'd be useful to keep all patches for the a given release somewhere. > --> GCC: latest stable versions, meaning the latest released version. distros not always use the latest release. it'd be useful at least support the latest 2 major release (eg. 4.5.3 and 4.6.1 now). and in this case also a version specific patches directory would be useful for packages. all other proposal seems good:-) -- Levente "Si vis pacem para bellum!" ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
