Chris Sutcliffe wrote: > For the packages I maintain (w32api, mingw-runtime, hexedit, astyle) I > didn't think there would be much of an impact between 1.5 and 1.7. If > there is some benefit, please let me know and I will build 1.7 > versions of these packages. Is there a naming convention or something > I should use, since I assume using the same name / version as the 1.5 > binaries may cause a problem?
Corinna has been using a paired approach for openssh (e.g. simultaneous releases of -5 for cygwin-1.5 and -6 for cygwin-1.7, followed by -7/-8, etc.) For autotools, I "jumped" to the next multiple of 10 for the new -1.7 series of releases, reserving (e.g.) -3 to -9 for any future updates to the packages for -1.5. However, in those particular cases I do NOT expect any additional releases for -1.5 anyway, so -3 to -9 most likely will be forever "empty". But yeah, using the same release number for different -1.5 and -1.7 packages is just asking for trouble. -- Chuck
