瀏覽代碼

- Cleaned up the Dev folder.
- bugs.txt should store 'fatal/known' bugs that have been going on for a long time and have not been fixed yet. The forums are the preferred method for day-to-day bug finding/fixing.
- todo-for-stable.txt should list all changes in trunk that need to be merged into stable.


git-svn-id: https://svn.code.sf.net/p/rathena/svn/trunk@5370 54d463be-8e91-2dee-dedb-b68131a5f0ec

skotlex 19 年之前
父節點
當前提交
26d56fc08b
共有 5 個文件被更改,包括 57 次插入415 次删除
  1. 4 0
      Changelog-Trunk.txt
  2. 0 347
      Dev/Message to Celest.txt
  3. 19 8
      Dev/bugs.txt
  4. 34 0
      Dev/todo-for-stable.txt
  5. 0 60
      Dev/trunk_vs_branch.txt

+ 4 - 0
Changelog-Trunk.txt

@@ -5,6 +5,10 @@ IF YOU HAVE A WORKING AND TESTED BUGFIX PUT IT INTO STABLE AS WELL AS TRUNK.  EV
 GOES INTO TRUNK AND WILL BE MERGED INTO STABLE BY VALARIS AND WIZPUTER. -- VALARIS
 
 2006/02/22
+	* Cleaned up the Dev folder. [Skotlex]
+	- Take note of the file todo-for-stable, which holds all modifications in
+	  trunk that have not yet made it into stable. Be sure to update the file
+	  as needed.
 	* Updated the path searching code with jA's current implementation.
 	  [Skotlex]
 	- There is a slight chance the CELL_NOSTACK mod broke, someone test that.

文件差異過大導致無法顯示
+ 0 - 347
Dev/Message to Celest.txt


+ 19 - 8
Dev/bugs.txt

@@ -1,8 +1,19 @@
-Reported Bug: It seems cards (somehow) aren't working properly. For instance, 
-		the doppelganger card does not stack properly anymore (although 
-		I think that might be a "fix") and previously I created a 
-		custom card that added 255 to all stats (after checking if the 
-		person was a GM) and this card, as well, has problems: I used 
-		to be able to do 999999 damage with Jupital Thunder and now it 
-		does approximaetly 19000 (perhaps this, too, is a stacking 
-		problem).
+- NOTE: Use this file to place BIG BAD BUGS that have been going on for a good
+  while and it seems noone can fix them (Use the forums for common everyday
+  bugs). Bugs in this file are not meant to be "fixed" as much as they are a
+  "reminder" of big bugs that have not been fixed yet. An good example would
+  be "the matrix bug" from the good old days.
+
+BUG: grf loading is broken.
+DESC: Specifying multiple grfs is badly broken, as the 'checksum' applied to
+files usually returns the wrong index, thus looking the file up on the wrong
+grf file. Users have also reported that reading from the data/ dir is messed
+up. See link for all details. 
+LINKS:
+- http://www.eathena.ws/board/index.php?showtopic=78372
+
+BUG: @reloadscript causes a crash
+DESC: Do a @reloadscript, and it will inmediately crash on the
+skill_unit_timer function. Apparently the global objects array gets messed up
+when cleaning the npcs. Valgrind doesn't seems to point at any particular
+cause. I suspect it may have to do with NPC shops.

+ 34 - 0
Dev/todo-for-stable.txt

@@ -0,0 +1,34 @@
+Place in this file any updates you did on trunk that should be merged into
+stable. Remove it from the list once merged.
+
+- restricted mapflag (which restricts equipment/cards from being used in
+  certain maps)
+- function battle_calc_return_damage which encapsulates damage return
+  cards/status.
+- The update to the status change structure which unifies opt values in the
+  same structure as sc_data ones. Also includes a rewrite of
+  status_change_start as well as battle options for adjusting sc-def and
+  max-sc-def.
+- Improved npc timers which enable multiple characters to be attached to a
+  timer, and each one will be executed with the attached player accordingly.
+- irc bot system (which isn't even finished yet on trunk)
+- The new implementation of NPC_POWERUP which uses SC_INKATK rather than
+  Explosion Spirits.
+- Stat window showing the added damage of both weapons for dual-wielding
+  assassins.
+- Deleting pet eggs from inventory after the pet data has arrived, not upon
+  hatching request.
+- Updated the char-SQL server to use auto-incremental IDs and retrieve them
+  from code.
+- Battle option pk_level_range, allow_es_magic_player
+- Cleanup of pc_useitem code
+- Autocasted Teleport should now show a menu.
+- Skill system update, usage of the new splash area range column in the db.
+  Code-wise lots of code cleanup.
+- Skill SG_MIRACLE
+- Gangster's Paradise behaviour update.
+- Menu-based skill update to allow menu skills to be precasted.
+- Cleanup of the global chat function.
+- Revert the map-sql handling of the gm-list retrieval.
+- Send the guild/party mini-dots on map-login.
+- Updated the path-finding routines from jA

+ 0 - 60
Dev/trunk_vs_branch.txt

@@ -1,60 +0,0 @@
-- This is a small summary of the roles of trunk vs a branch, as well as their
-  current state in eA. 
-
-- Trunk: This should be the base source-codebase, well all the flashy lights
-  and new enhacements get added. It gets updated a lot, breaks often.
-
-- Current situation: Noone works on trunk anymore and it's seriously outdated.
-
-
-- Branch: This should be a snapshot of the trunk at some given time, and
-  receives no enhancements at all, only bug fixes. Once the branch becomes
-  stable enough, it is "released" to the public with an appropiate version
-  number, and the next branch is created from a new snapshot from the trunk.
-
-- Current situation: Everyone is working on branches/stable s if it were a
-  stable + development source.
-
-As Akaru has pointed out, we need to sort this out inmediately:
-- branches/stable must be moved and become the new trunk/
-- We should probably make a branch snapshot from a few days ago (before the
-  latest feature additions like string permanent variables?) for next release
-  base.
-- All devs should stick to the roles of branch/trunk.
-- It appears most devs who have heard of this agree with Akaru, however the
-  initial steps to clean up the SVN repository have yet to be taken. This task
-  seems assigned to Kayla, maintainer of said repository.
-
-Post your thoughts/ideas about here...
-- [Skotlex] I think fixing skills counts as bug fixing, and goes to branch.
-  But implementing missing skills should go to trunk.
-
-- [Vicious Pucca]
-* Have you read this? http://eathena.ws/board/index.php?showtopic=65827
-At least one of dev seems to agree with me(on irc) that we don't have enough resources(on devs or testers) to do trunk/stable.
-simply.
-1. who's going to test trunk? if no one is gonna test it, and bugs slips into stable... what's the point. good example would be whole guild cache. i'm sure it worked fine on kevin's setting. but when lots of people tested, in various settings, we found out how broke it was.
-2. who's gonna manage trunk->stable transfer? and when? as you know, there always will be some bug... it's like whole eA 1.0 thing. There is always something to fix. It was never quite "stable" enough to do "stable" release. so trunk is gonna be our current stable branch, except even more broken... great. :o
-imo, eA is fine as is.
-and if you REALLY want to dev, should be 3 branches.
-dev: where you commit things. broken often. do-whatever-dev-wants
-trunk/"testing": things that are "complete," but needs testing. primary bug fixes
-stable: the release. should be almost no bugs. shouldn't need update, unless it's critical update.
-
-- [Lance] Now who's in charge of merging back fixes from the stable -> trunk and vise versa
-
-- [Skotlex] From what I heard Akaru explain, after there's a release, the next
-  stage should be merging all the bugfixes that went into stable to trunk.
-  There's no viceversa since the bug fixes in trunk are for features in trunk
-  itself that haven't gone into the branch yet. So to answer yer question,
-  everyone who codes would be in charge. :X
-
-- [Kayla] I was speaking with Devi, do we have the OK from Mass to do this? If so we should reset to
-  revision 0, wipe the trunk, dump stable into the trunk and toss the Preview Release inside of Stable 
-  (or youngest version). 
-
-- [Vicious_Pucca] We should talk about this in dev forum.=p
-Anyway, if this trunk/stable DOES happen, it should happen AFTER TK/SL/SG are DONE-done. really, no half-assed classes please. :o (well, more like 3/4-assed classes right now)
-Another thing. how would DB/NPC update would work? let's say, new npc that are missing, such as Swordie class quest. Is it required? no. Is it official? yes. Is it a bug? not really. Is it a feature? to some, appearantly is... so. what about that?
-and fixes for stable means probably fixes for trunk as well. :o
-If trunk/stable happens, i'm breaking trunk so bad. XD

部分文件因文件數量過多而無法顯示