Menu
▾
▴
phpwsbb-developers
|
From: Meiste, G. <me...@ms...> - 2004-09-23 22:55:00
|
Don and Eloi, I've filed a few bugs just now. I didn't get much time to test it and I'm out of time for the day. Could you hold off on the Friday release? I would like some more time to test because I haven't had a chance to test out all the new features yet (and there are a lot of them!). In addition, I'm not convinced that 1.0.0 is ready for prime time just yet. Just my two cents. Greg -----Original Message----- From: php...@li... [mailto:php...@li...] On Behalf Of Don Seiler Sent: Monday, September 20, 2004 9:09 PM To: Eloi George Cc: php...@li... Subject: Re: [phpwsbb] re: phpwsBB 1.0.0 feature freeze On 21:37 Mon 20 Sep , Eloi George wrote: > Everything checks out here. >=20 > I've done all the commits that need to be done for this go-around. Fantastic. Would any able-bodied testers also give this a go-round and we'll get 1.0.0 out the do'. Let's give until Friday for testing? Please report any bugs or all-clears to this list by then. Don. --=20 Don Seiler do...@se... Public Key: = http://pgp.mit.edu:11371/pks/lookup?op=3Dget&search=3D0xFC87F041 Fingerprint: 0B56 50D5 E91E 4D4C 83B7 207C 76AC 5DA2 FC87 F041 |
|
From: Eloi G. <el...@by...> - 2004-09-24 07:25:11
|
Don, I agree. There's been a few minor things that were missed when we merged both versions, so can we hold off until Monday so that phpwsBB can get a more complete shakeout? Also, what do you want the default to be for thread monitoring? Of course I can make it admin-selectable after the feature-freeze is lifted... -Eloi- Meiste, Gregory wrote: >Don and Eloi, > >I've filed a few bugs just now. I didn't get much time to test it and >I'm out of time for the day. Could you hold off on the Friday release? >I would like some more time to test because I haven't had a chance to >test out all the new features yet (and there are a lot of them!). In >addition, I'm not convinced that 1.0.0 is ready for prime time just yet. > >Just my two cents. > >Greg > > |
|
From: Don S. <do...@se...> - 2004-09-28 15:46:53
|
On 03:27 Fri 24 Sep , Eloi George wrote: > There's been a few minor things that were missed when we merged both=20 > versions, so can we hold off until Monday so that phpwsBB can get a more= =20 > complete shakeout? Continuing to hold ... > Also, what do you want the default to be for thread monitoring? Of=20 > course I can make it admin-selectable after the feature-freeze is lifted.= =2E. I changed the default to OFF. Used to be ON but people requested it to be off and then even I became annoyed with spam. I think once we have the notification emails include the text of the reply then we can change it to ON perhaps. For now I would just leave it. --=20 Don Seiler do...@se... Public Key: http://pgp.mit.edu:11371/pks/lookup?op=3Dget&search=3D0xFC87F041 Fingerprint: 0B56 50D5 E91E 4D4C 83B7 207C 76AC 5DA2 FC87 F041 |
|
From: Shaun M. <sh...@ae...> - 2004-09-28 16:09:51
|
On 28 Sep 2004, at 16:47, Don Seiler wrote: > > I changed the default to OFF. Used to be ON but people requested it to > be off and then even I became annoyed with spam. I think once we have > the notification emails include the text of the reply then we can > change > it to ON perhaps. For now I would just leave it. > I'd vote for OFF being the default to most things. If you leave the default as ON then users are lazy enough to leave it like that and on busy websites that's an awful lot of monitoring and emailing. Also, I do hope it's configurable whether the mails going out include the full message or just a message saying there was a new post. If you send out the full message, nobody comes back to your website, just reads the mail so no ad revenue. Maybe you could add Google Adsense ads to the bottom of each mail Don. <ducks> ;-) Shaun aegis design - http://www.aegisdesign.co.uk |
|
From: Eloi G. <el...@by...> - 2004-09-28 17:40:42
|
Don Seiler wrote: >Continuing to hold ... > > OK, I've fixed everything that was found. Since noone's reported any other bugs, I think we can go ahead! -Eloi- |
|
From: Don S. <do...@se...> - 2004-09-29 17:50:35
|
On 13:40 Tue 28 Sep , Eloi George wrote: > OK, I've fixed everything that was found. Since noone's reported any=20 > other bugs, I think we can go ahead! Alright then unless I heard differently, I'll plan on releasing around 10:00 PM US Central time tonight. Don. --=20 Don Seiler do...@se... Public Key: http://pgp.mit.edu:11371/pks/lookup?op=3Dget&search=3D0xFC87F041 Fingerprint: 0B56 50D5 E91E 4D4C 83B7 207C 76AC 5DA2 FC87 F041 |
|
From: Don S. <do...@se...> - 2004-10-07 21:33:49
|
OK. Things seem to have quieted down. There is one open bug left in the tracker and it actually looks more like an RFE to me. Shaun can you please comment. Otherwise we may be ready for a release. I should probably do a test upgrade of my own, perhaps I'll do that tonight. Consider this a last call. I'm leaving for a week in Florida on Sunday and want to get this out before I go so it's not hanging over my head. --=20 Don Seiler do...@se... Public Key: http://pgp.mit.edu:11371/pks/lookup?op=3Dget&search=3D0xFC87F041 Fingerprint: 0B56 50D5 E91E 4D4C 83B7 207C 76AC 5DA2 FC87 F041 |
|
From: Don S. <do...@se...> - 2004-10-20 02:11:33
|
Alright I've finally had a chance to test this myself. I applied some bug fixes from Steven and tested both a funky phresh install and an upgrade from a copy of manitowocbandits.com. Both went well. There is still a bug that I introduced way back. When upgrading messages, it sets the admin as the "last" person to update the thread, which is technically true but that's not what we want. We want the owner of the last message to be the last editor of that thread. I'd like to have that bug fixed. Basically it will involve updating Thread::updateThread() and Forum::updateForum() to find the owner of the most recent message and thread respectively. I'll leave it as an exercise for someone to fix since I need to take a break. Other than that I think we're ready for release. Don. --=20 Don Seiler do...@se... Public Key: http://pgp.mit.edu:11371/pks/lookup?op=3Dget&search=3D0xFC87F041 Fingerprint: 0B56 50D5 E91E 4D4C 83B7 207C 76AC 5DA2 FC87 F041 |
|
From: Don S. <do...@se...> - 2004-10-25 14:52:49
|
On 21:11 Tue 19 Oct , Don Seiler wrote: > There is still a bug that I introduced way back. When upgrading > messages, it sets the admin as the "last" person to update the thread, > which is technically true but that's not what we want. We want the > owner of the last message to be the last editor of that thread. Steven clued me in today in that I can pass parameters to Item->commit() and not have it auto set the "editor" field. I've made this change and just checked it in. If anyone wants to test it, please do and let me know. Don. --=20 Don Seiler do...@se... Public Key: http://pgp.mit.edu:11371/pks/lookup?op=3Dget&search=3D0xFC87F041 Fingerprint: 0B56 50D5 E91E 4D4C 83B7 207C 76AC 5DA2 FC87 F041 |
|
From: Steven L. <st...@tu...> - 2004-10-25 17:50:40
|
On Mon, 2004-10-25 at 10:53, Don Seiler wrote: > On 21:11 Tue 19 Oct , Don Seiler wrote: > > There is still a bug that I introduced way back. When upgrading > > messages, it sets the admin as the "last" person to update the thread, > > which is technically true but that's not what we want. We want the > > owner of the last message to be the last editor of that thread. > > Steven clued me in today in that I can pass parameters to Item->commit() > and not have it auto set the "editor" field. I've made this change and > just checked it in. If anyone wants to test it, please do and let me > know. I tested this and found a few issues. I have fixed these and tested. The changes are now in CVS. If you are testing, please update your copy and try again. Thank you. -- Steven Levin Computer Systems Admin I Electronic Student Services Appalachian State University http://phpwebsite.appstate.edu |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X