http://bugzilla.wpkg.org/show_bug.cgi?id=120 --- Comment #16 from Rainer Meier <r.meier at wpkg.org> 2009-06-16 19:49:27 --- > The list of "volatile-version-markers" is nearly endless. > I use an application which releases Maintenance Releases (MR) and Maintenance > Packs (MP). > MRs' are service packs and MPs' are patches. Well just from the wording I would have assumed that MRs are newer than the base release and MPs are newer than the MRs. But this depends on the definition of course. > I do not think it is good to include too many OOTB, if a user needs one he > can add it through the "customer default" you have graciously included ;-) That's exactly why I made it configurable - even if the purpose of "volatile release markers" will not be obvious to most users new to WPKG. I tried to include some examples which show how it works but the topic is quite complicated in general. I fully agree that we should not try to cover each and every possible "volatile release" string used out there and risk "overmatching". Instead I would like to keep a small list (as I did already) and allow users to extend the list as appropriate. For most users it will be easier anyway not to use such complicated string within the version number but instead add another digit to the version number to be increased each time. e.g. a software uses version 1.0RC0 - use 1.0.0 release version in WPKG, then 1.0RC1 get 1.0.1 in WPKG and when 1.0 is released, then the WPKG release number is just increased once again. > The worst is something like weekly builds. I agree it's difficult to handle but in order to call it "the worst" I would assume that I know every silly/sick versioning scheme out there - and this is not the case. Thanks for feedback. I assume you agree to the implementation as it is currently and I am not asked to change something urgently. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |