From: Thijs K. <ki...@sq...> - 2006-05-07 10:08:11
|
Hello devs, I'd like us to start a planning for a 1.4.7 release. The current changelog contains already quite a number of fixes, and looking over them seems quite a number fix bugs that could be labeled as "annoying" (a mild security bug, prefs issues, session lockup, prevent errors). My proposal is to aim for a stable release at or around the end of June (let's say the 30th). I'm confident that the little less than two months time that gives us, will get even more fixes into place making it a package even more worthy for release. Opinions please? Stable managers? bye, Thijs |
From: Tomas K. <to...@us...> - 2006-05-09 06:00:08
|
> Hello devs, > > I'd like us to start a planning for a 1.4.7 release. The current > changelog contains already quite a number of fixes, and looking over > them seems quite a number fix bugs that could be labeled as > "annoying" (a mild security bug, prefs issues, session lockup, prevent > errors). > > My proposal is to aim for a stable release at or around the end of June > (let's say the 30th). I'm confident that the little less than two months > time that gives us, will get even more fixes into place making it a > package even more worthy for release. > > Opinions please? Stable managers? 1368154 - Extend ldap search filter 1212618 - LDAP_SCOPE_* search options in ldap address books 1212618 - LDAP_SCOPE_* search options in ldap address books 1035454 - Active Directory in Windows Server 2003 as an LDAP address b 539534 - Configurable LDAP search filters all five trackers can be closed by porting functions/abook_ldap_server.php and config/conf.pl changes from devel. abook_ldap_server.php port is simple copy + phpdoc update, conf.pl port - $ldap_server configuration changes. All five trackers are about new features. 1233721 - Preference database error I think all updates are in functions/db_prefs.php, config/conf.pl and config/default_config.php. Fixes prevent unexplained errors in PostgreSQL and data corruption in MySQL. 1374174 - safe_mode + php-4.3.11 = messages not sent error handling changes are only in class/deliver/Deliver_Sendmail.class.php. Some other changes are in sanitizing of delivery errors (3 locations). Other Deliver_Sendmail.class.php devel updates fix issues with some /usr/sbin/sendmail wrappers. Fixes prevent email loss on /usr/sbin/sendmail execution errors. I won't work on these issues in stable unless I know that my patches will be accepted. -- Tomas |
From: Chris H. <ta...@sq...> - 2006-05-09 12:25:14
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tomas Kuliavas wrote: > all five trackers can be closed by porting functions/abook_ldap_server.php > and config/conf.pl changes from devel. abook_ldap_server.php port is > simple copy + phpdoc update, conf.pl port - $ldap_server configuration > changes. All five trackers are about new features. My general policy is that no new features go into stable. (Sort of the Debian policy, in a way - new features go into devel/unstable, security fixes are the only thing in stable.) Tomas and Jon, do you have any thoughts on that? > 1233721 - Preference database error > 1374174 - safe_mode + php-4.3.11 = messages not sent I don't see any problem fixing these two issues. Thanks Tomas. - -- Chris Hilts ta...@sq... Say it with flowers -- Send them a triffid! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (MingW32) iD8DBQFEYIor98ixrK2vMtARAk0QAKCKnn3maqVF1ZvvKFCtzMQcXT/2pACfXqWP AYfdj0isw9RH4oKW8mmAtpM= =AU/r -----END PGP SIGNATURE----- |
From: Jonathan A. <jo...@sq...> - 2006-05-16 04:02:24
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Still playing catch-up... oh well... here is my 2cents. On Tue, May 9, 2006 07:25, Chris Hilts wrote: >> all five trackers can be closed by porting >> functions/abook_ldap_server.php and config/conf.pl changes from devel. >> abook_ldap_server.php port is simple copy + phpdoc update, conf.pl por= t >> - $ldap_server configuration >> changes. All five trackers are about new features. > My general policy is that no new features go into stable. (Sort of the > Debian policy, in a way - new features go into devel/unstable, security > fixes are the only thing in stable.) Tomas and Jon, do you have any > thoughts on that? I generally agree, stable should be mostly bug fixes, however to some extent, and in terms of the way our dev/stable setup seems to be, I believe some "features" can be back ported. Development is in a state of total chaos, and I'd not recomment it for production use with the mixed templating, and such. I'll take a look at Tomas' requests, and see about back porting them. :) - --=20 Jonathan Angliss <jo...@sq...> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) iEYEARECAAYFAkRpTjIACgkQK4PoFPj9H3MXCQCfdE5n4Uh9zPRPnZ4rkz6dA58m A0gAoOU9cwODYsww0/I4Ox5AvJ1fj4vw =3DGSIY -----END PGP SIGNATURE----- |
From: Thijs K. <ki...@sq...> - 2006-05-17 10:56:41
|
On Mon, 2006-05-15 at 22:59 -0500, Jonathan Angliss wrote: > > My general policy is that no new features go into stable. (Sort of the > > Debian policy, in a way - new features go into devel/unstable, security > > fixes are the only thing in stable.) Tomas and Jon, do you have any > > thoughts on that? >=20 > I generally agree, stable should be mostly bug fixes, however to some > extent, and in terms of the way our dev/stable setup seems to be, I > believe some "features" can be back ported. Development is in a state of > total chaos, and I'd not recomment it for production use with the mixed > templating, and such. >=20 > I'll take a look at Tomas' requests, and see about back porting them. :) Good. Just one more thing: do you and/or Chris agree to the timeline I proposed, i.e. aim for end of June? Thijs |