Hi Jarmo, comments are inline.
On Sun, Feb 9, 2014 at 6:04 PM, Jarmo <[email protected]> wrote: > What do you mean about yanking these gems? Do you mean yanking all the > versions? > Yes, that was the idea. > I'm not sure this is a good idea - usually only particular versions of the > gems are yanked because they have some critical problem. And if you only > yank the last version, then you can still install the version before that. > I'm pretty sure you can still use firewatir with some older version of > Firefox successfully. There might be still some legacy projects depending > on these particular gems for whatever reason. > After thinking more about it, I agree with you. > A better idea would be to release a newer version of these gems with > having a message similar to the lines of "this gem is now deprecated, use > watir instead or if you really need this gem, then the previous version > might work for you." when loading them. > +1. If nobody does it before me, I can do that. > Do you see any problem with these gems? Is there a lot of confusion > happening because of them? > I would not say a lot, but I remember seeing questions on mailing lists and stack overflow from people that were using firewatir or safariwatir long after they were deprecated. Željko
_______________________________________________ Wtr-development mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-development
