39

The author made it explicit that the backwards compatibility will be broken. Though the issues are definitely worth fixing, it is still up to the package author to decide how to do that. Making people aware of this fact should be sufficient. I have to say that I'm not in favor of backwards compatibility that much though. Things should change once in a ...


29

There are a lot of loaded terms in the description in this question. There are no easy answers to compatibility. My own packages tend to be very stable and backward compatible but they also have bug reports that have been open for 20 years as they can't really be fixed in a compatible way. Not everyone would say that is better. As @percusse says in his ...


27

No, it is not ok, surely not in a question. Remember that StackExchange is not a forum, questions have to be questions, and even beyond, have to be objective, one question per question etc. Package patch proposal doesn't sound like a question. It is, however, ok to propose a patch to an existing package, but only in an answer. I believe that the maintainer ...


25

Nobody but Florent Chervet knows what the next version of tabu will break. There have already been a few backwards incompatible changes between major revisions of the package, but limited in extent. It's a very promising package, because many things are possible with it that weren't before (or required low level tricks). When I read that message on comp....


23

The code in the answers and its documentation is cc-wiki with attribution required, so you are allowed to use this code for making packages if you fulfill the requirements, i.e. link to the answer and the profile of the user who contributed, in the package code and in the package documentation. Note, some users offere a more relaxed licensing, have a look ...


22

If you actually find questions that are related to your package content, then you can fire an answering frenzy by mentioning you can also do this with <insert package name> and so on. Then I don't see why it should be a problem since we have loads of package authors answering questions with their own poison of choice. And it is a very very good thing ...


20

The author of tabu may not be too concerned with backward compatibility, but the maintainers of CTAN are. I corresponded with Robin Fairbairns some time ago about a package I am the maintainer for, and was dissuaded from changing a problem feature, enabled by default, into a package option. CTAN best practice would be to issue the new, improved tabu under a ...


19

Strange, mostly I use the site for the opposite use: Don't use longtable Longtable vs. supertabular: Which is right for which job? Don't use xspace https://tex.stackexchange.com/a/86620/1090 Don't use tabularx Alignment in tabularx environment Column width table in tabularx environment https://tex.stackexchange.com/a/145918/1090 https://tex....


16

As others have already said, equating backward incompatibility with dangerous is a subjective matter. As a case in point, consider ConTeXt. Compared to LaTeX core, ConTeXt does not assert that new changes will not break backward compatibility. Sometimes, the only way to add new features or to fix bugs is to break backward compatibility, and ConTeXt tends ...


Only top voted, non community-wiki answers of a minimum length are eligible