Login
User Name:

Password:



Register
Forgot your password?
Vote for Us!
parse description bug
Dec 15, 2017, 10:08 pm
By Remcon
Couple bugs
Dec 12, 2017, 5:42 pm
By Remcon
Bug in disarm( )
Nov 12, 2017, 6:54 pm
By GatewaySysop
Bug in will_fall( )
Oct 23, 2017, 1:35 am
By GatewaySysop
Bug in do_zap( ), do_brandish( )
Oct 18, 2017, 1:52 pm
By GatewaySysop
LOP 1.45
Author: Remcon
Submitted by: Remcon
LOP Heroes Edition
Author: Vladaar
Submitted by: Vladaar
Heroes sound extras
Author: Vladaar
Submitted by: Vladaar
6Dragons 4.3
Author: Vladaar
Submitted by: Vladaar
Memwatch
Author: Johan Lindh
Submitted by: Vladaar
Users Online
CommonCrawl, Yahoo!

Members: 0
Guests: 20
Stats
Files
Topics
Posts
Members
Newest Member
477
3,706
19,240
608
LAntorcha
Today's Birthdays
There are no member birthdays today.
Related Links
» SmaugMuds.org » General » General Discussions » Official bugfix policy?
Forum Rules | Mark all | Recent Posts

Official bugfix policy?
< Newer Topic :: Older Topic >

Pages:<< prev 1 next >>
Post is unread #1 Sep 9, 2006, 10:21 pm
Go to the top of the page
Go to the bottom of the page

Samson
Black Hand
GroupAdministrators
Posts3,639
JoinedJan 1, 2002

Been asked a few times now about official vs unofficial fixes. I guess it's time for a bit of clarification.

Fixes posted by members or admins of the site outside of one of the 3 "Bugfix" forums are not supported. Use of any fix which has not been posted by myself in the designated areas is an "at your own risk" activity. Even if I post something there.

The reason for this is that not all fixes posted by other members are necessary, working, complete, or verified. The fix may be in discussion. May get changed, or even completely redone by someone else who offers a different solution. It may even be rejected.

This is also why some proposals take longer to migrate to the official lists than others. The review process will take longer the more complex the fix is. We don't want to include something which is dangerous by accident. And if a new fix is posted which depends on one that's not approved, that too will get delayed.

Only once I have applied it to the distributed package and verified that it compiles cleanly will it be posted in the "official" sections. This does mean there is some trust involved that a fix which makes it to the official lists and into the packages has been tested properly. Hopefully the review process has done its job. I don't have time to do this myself. I only have time to compile them and package the updates.

Hopefully this clears things up. Though I suspect not :P
       
Pages:<< prev 1 next >>