siunitx 2: release timetable

As many readers will know I’ve been working on version 2 of siunitx for some time. There are always more feature requests, but at some stage I have to actually release something. I’ve now got some code that fixes a lot of bugs and annoyances in the current release and provides a better platform for new features, and so I want to move to releasing it.

The plan is to fix the known bugs in the development code and add as many new features as possible by the 25th of the month, and then to freeze development for a beta (testing) release. Depending on feedback, I’ll then aim to fix the bugs in the beta and go for a first production edition of version 2 in June. I’m not going to add any new features between the beta and production releases, but will start on them again once the production version is out. There is a feature tracker on the BerliOS site, which is a good place to put things so I don’t forget about them.

2 thoughts on “siunitx 2: release timetable

  1. Nice work. I also had been using berlios for a year but it was always down so I decided to try bitbucket ( because I can have all my projects in one place and the issue tracker actually allow attaching files which is very nice. I just looked at your siunitx package on CTAN and it seems you are using listings package. I have got a problem and that is when I use listings package in my .dtx files, it actually prints “%” in the pdf. Do you know how I could fix this?

  2. Hello Vafa,

    I’ve not come across bitbucket before: I will take a look (while BerliOS are flexible on licenses I have had some issues, and the site design is not great). On the listings question, you’ll see that I have some custom macros (adapted from the listings manual), which are probably easier to follow in the v2 code than the more patched-up approach in v1 of siunitx. Perhaps I’ll post something on this more fully, but essentially the requirement is to have

    setkeys{lst}{gobble = 3} % or whatever

    where the number of items to gobble includes the “%” column. (I always indent my examples by two spaces in addition to the “%”, so need three in total.)


Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.