Prematurely requesting stabilization by 10 days since upstream has already releases 1.4.7, and it fixes bugs along with some new features. 1.4.5 was just marked stable on the 28th of November.
Wouldn't it be better to stablize 1.4.7 then if that's the latest upstream release? Also, are the bugfixes critical?
I thought so, but wasn't sure since I just did the bump. Team lead was not sure either. I can't say any bug fixes were critical, but they were bug fixes none the less. A few new features, but nothing major that looked like it could cause breakage. http://www.lowagie.com/iText/history.html#V150 It seems as if they are releasing monthly. I was concerned with not being able to keep up with upstreams current release. We would always be one version behind in stable. Didn't want to start a huge debate. But I am all for stabilizing 1.4.7, and catching up with upstream. Also was not sure if I should even file stabilization bugs for x.y.* releases. Of course if it was x.* release that should not be marked stable. But if a x.y.* release is already stable. Wasn't sure if it was common to go ahead and have the bump be stable, or always filling bugs and giving packages 30 days between any release.
dev-java/itext-1.4.7 USE="doc source" 1. emerges on x86 2. passes collision test still have no idea how to test this =) Portage 2.1.1-r2 (default-linux/x86/2006.1/desktop, gcc-4.1.1, glibc-2.4-r4, 2.6.18.3 i686) ================================================================= System uname: 2.6.18.3 i686 Genuine Intel(R) CPU T2300 @ 1.66GHz Gentoo Base System version 1.12.6 Last Sync: Sun, 03 Dec 2006 13:30:01 +0000 ccache version 2.3 [disabled] app-admin/eselect-compiler: [Not Present] dev-java/java-config: 1.3.7, 2.0.30 dev-lang/python: 2.3.5-r3, 2.4.3-r4 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: 2.3 dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.60 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2 sys-devel/binutils: 2.16.1-r3 sys-devel/gcc-config: 1.3.13-r4 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.17-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=prescott -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config /var/qmail/alias /var/qmail/control" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/java-config/vms/ /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c" CXXFLAGS="-O2 -march=prescott -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" EMERGE_DEFAULT_OPTS="--nospinner" FEATURES="autoconfig collision-protect distlocks metadata-transfer parallel-fetch sandbox sfperms strict test userfetch userpriv usersandbox" GENTOO_MIRRORS="http://mirror.switch.ch/mirror/gentoo/ http://gentoo.inode.at/" LINGUAS="en de en_GB de_CH" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X a52 aac acpi alsa apache2 asf berkdb bitmap-fonts cairo cdr cdrom cli cracklib crypt cups dbus divx dlloader dri dts dvd dvdr dvdread eds elibc_glibc emboss encode fam ffmpeg firefox flac fortran gdbm gif gnome gpm gstreamer gtk hal iconv input_devices_keyboard input_devices_mouse ipv6 isdnlog java jpeg kde kdeenablefinal kernel_linux ldap libg++ linguas_de linguas_de_CH linguas_en linguas_en_GB mad mikmod mmx mono mp3 mpeg ncurses nls nptl nptlonly ogg opengl oss pam pcre perl png ppds pppd python qt3 qt4 quicktime readline reflection rtsp ruby samba sdl session smp spell spl sse sse2 sse3 ssl svg tcpd test tetex theora threads truetype truetype-fonts type1-fonts udev unicode userland_GNU vcd video_cards_fbdev video_cards_i810 video_cards_vesa vorbis win32codecs wxwindows x264 xine xml xorg xprint xv xvid zlib" Unset: CTARGET, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY
I did contact upstream about JUnit tests. But got mixed responses from them on most tests needing to be visual. Any JUnit tests would have to create and spit out PDF files. That would almost have to be checked visually to see if there is a problem or not. Some ideas were discussed on upstream mailing list. No clue when there will be JUnit tests, or a built in way to test the library/api.
We just do it on x86
I know it's way premature, but I just committed a fix to 1.4.7. Which changes the build and install process. The previous 1.4.x versions flat out don't work. All text is off, as I discovered a bit ago the hard way :(. Anyway if we could look to stabilizing 1.4.7-r1. Otherwise I will need to go back and apply the same changes to the older versions as well. Also pretty sure 1.4.8 will be out either this month or first part of January. So also trying to catch up to upstream :) Thanks and sorry for the craziness, and premature requests.
I tried with datavision and that seemed to work (although I hit a bug, corrected it and sumbmitted a report). x86 stable
Changing to itext-1.4.7-r2, the only change was fixing package.env file which caused bug 157496.
amd64 stable
