Yesterday afternoon, pytrainer 1.9.1 Debian packages were uploaded to Debian unstable.
If you're not familiar with Debian processes, it means the following: - if no RC bugs are reported in 10 days AND if all dependencies and build dependencies are satisfied, these packages will migrate to Debian "testing", which is to become Debian "wheezy", the release that we, Debian developers, are preparing (release "sometime in 2012") - these packages should soon land in Ubuntu 12.04 release in preparation (whatever funky name is given to that Ubuntu release) - the won't be any update of pytrainer in Debian "stable" (squeeze) or released Ubuntu releases (11.10 and below). This goes against the respective distros policies for their stable releases. Of course, anyone is free to "backport" the packages (that should be easy for 1.9.1 because of the relaxed dependency on python-migrate). As usual, using such backported (and often unsigned) packages is done at your own risks. Most opened bugs were closed by this release as I also worked on some cleaning of the packaging part. On the other hand, I opened several tickets in Trac, mostly for minor issues revealed by the Debian quality check tools. None of them is really critical. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Pytrainer-devel mailing list Pytrainer-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytrainer-devel
