... I think we should take increasing the major version as a chance and remove some old compatibility stuff with it like e.g. APIv1. Or fix some APIv2 inconsistencies. Maybe we could move foreman tasks to core. Just some suggestions. Just increasing the major version is in, but I think just a cosmetic thing.
Timo > On 29. Nov 2017, at 10:39, Lukas Zapletal <l...@redhat.com> wrote: > > What have Linus Torvalds and me in common? We both don't remember > numbers higher than ten. > > I propose to follow Linux kernel versioning and do 2.0 instead of 1.18 > for no other reason that it's just too high number and it's > approaching crazy 20. "One point eighteen" sounds crazy, I always mess > up with "One point eight". Frankly, I kinda lost track somewhere after > 1.14. :-) > > I'd like also to propose to avoid exceeding 10 in the future - someone > speak up as we will approach to 1.8. Or we can put this to release > wiki. > > If we already have some infrastructure set for 1.18, I propose 1.19 to > be 2.0 and act now - let's define a plan what needs to be done in > advance. I can only think of version number in RedMine, but you tell > me here what's needed. > > I really hope it's not just me messing around with higher numbers or > having problems with typing four characters instead of three many > times. > > -- > Later, > Lukas @lzap Zapletal > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
