Preparations for 2.1 release discussion

Forum closed. All further discussion to be discussed at https://github.com/OpenKore/

Moderator: Moderators

Message
Author
EternalHarvest
Developers
Developers
Posts: 1798
Joined: 05 Dec 2008, 05:42
Noob?: Yes

Re: Preparations for 2.1 release discussion

#11 Post by EternalHarvest »

itemtypes.txt needs updating ("i neq" displays wrong information).

EternalHarvest
Developers
Developers
Posts: 1798
Joined: 05 Dec 2008, 05:42
Noob?: Yes

Re: Preparations for 2.1 release discussion

#12 Post by EternalHarvest »

Almost all skill configuration didn't support skill handles...
Fixed it, now it will be nice to test everything that involves skills and statuses (use by name, use by handle).
Not tested permitted skills at all.

Technology
Super Moderators
Super Moderators
Posts: 801
Joined: 06 May 2008, 12:47
Noob?: No

Re: Preparations for 2.1 release discussion

#13 Post by Technology »

I just noticed too, i was also working on it.
One ST0 to rule them all? One PE viewer to find them!
One ST_kRO to bring them all and in the darkness bind them...

Mount Doom awaits us, fellowship of OpenKore!

EternalHarvest
Developers
Developers
Posts: 1798
Joined: 05 Dec 2008, 05:42
Noob?: Yes

Re: Preparations for 2.1 release discussion

#14 Post by EternalHarvest »

Macro plugin has something depending on skill names too, in automacro logic.

EternalHarvest
Developers
Developers
Posts: 1798
Joined: 05 Dec 2008, 05:42
Noob?: Yes

Re: Preparations for 2.1 release discussion

#15 Post by EternalHarvest »

I guess after all these months and changes we really need some pre-release (call it alpha or RC), so users can try it and report problems which we're overlooked.

What we need for that:
0. Finish ongoing changes:
- check tablesets for old status files (posted earlier in this topic). Merge them into one
- background colors for Console::Unix (should be the same patch as for ::Simple, needs testing)
- test that nonsense with skill handles in configuration
1. Finish UPDATING (and put it into distribution). It should contain all the needed information for us to be not receiving questions about how to change their configurations, etc (or to be trashing such questions immediately). Small FAQ ("how do I to disable all that translated stuff") would be nice here, too.
2. Branching is not so needed until real release, as we can wait with new stuff, but can be done.
3. Branch (if branching will be decided to be done) or tag, make distribution, maybe with some plugins that were excluded away from trunk.
4. Announce at forums, with link to UPDATING and with note like this:
This is a pre-release of OpenKore 2.1.
It probably contains some bugs we're overlooked, but you're advised to test it, because we can fix bugs before real release if you report them now. And you'll find out new changes and features, unless you're already did that if you're used so called "svn" version.
Inform non-english communities about that, too (if possible). Just make sure they will proxy bug reports to us.

Then, if severe bugs will be found - fix them and make another pre-release. If only small bugs - fix, wait a bit and make a final.

User avatar
kLabMouse
Administrator
Administrator
Posts: 1301
Joined: 24 Apr 2008, 12:02

Re: Preparations for 2.1 release discussion

#16 Post by kLabMouse »

OK. So we could Release "2.0.8t" or something like that.
And Say that "t" marks testing, and it's only for testing out all the changes for upcoming release "2.1s"

EternalHarvest
Developers
Developers
Posts: 1798
Joined: 05 Dec 2008, 05:42
Noob?: Yes

Re: Preparations for 2.1 release discussion

#17 Post by EternalHarvest »

EternalHarvest wrote:background colors for Console::Unix
Done, Unix tested on Ubuntu, Simple tested on Ubuntu & FreeBSD.

EternalHarvest
Developers
Developers
Posts: 1798
Joined: 05 Dec 2008, 05:42
Noob?: Yes

Re: Preparations for 2.1 release discussion

#18 Post by EternalHarvest »

What's the plan?

User avatar
kLabMouse
Administrator
Administrator
Posts: 1301
Joined: 24 Apr 2008, 12:02

Re: Preparations for 2.1 release discussion

#19 Post by kLabMouse »

What Else we Left out?

EternalHarvest
Developers
Developers
Posts: 1798
Joined: 05 Dec 2008, 05:42
Noob?: Yes

Re: Preparations for 2.1 release discussion

#20 Post by EternalHarvest »

Default skill level should be maximum learned instead of undef, in case current character has the skill: that is needed for skill use blocks (currently it crashes when there is no "lvl", and it worked before at least for partySkill).

GM messages still have prefix visible (example: "ssss") and have problems with newline at the end in Wx Console and Chat Log.
UPD: actually, there's just some garbage at the end of the message, maybe wrong packet structure:
Screenshot-4.png
Screenshot-4.png (11.63 KiB) Viewed 3014 times

Locked