Hello everybody out there using L2j
After discussing and talking for a while with people from almost every group in the L2j community, we figured out several key changes in the way this project development should continue from now on.
All this time the development have suffered some slowdown and we think that H5 release might be a perfect time to revert and sort some of the issues that caused such delay, and that -we are aware- have diminished developers+community interaction/flow of goods.
At this point team and community should be one and the same, collaborating towards a single ideal of perfecting our beloved free software piece, teh L2j. With the upcoming changes we’re going to reinforce our commitment with this perspective, and we’re counting on you to succeed.
Starting from H5, further development will take place in a public branch, named (surprise) unstable. Initiates and devs should work there at will, with the single premise of taking L2J to the next possible level of perfection and stability. Fine grain details such as naming/coding conventions will be derived from current ones, but may evolve as the group of persons working there see fit. This way all of us will be able to test ideas, contribute and provide consistent feedback, and see the talent of our teammates in action from the very beginning. Trunk will still contain CT2.5 ’till H5 reaches enough stability. At this time a 2.5 branch will be created and trunk will be stable H5. Unstable branch will remain in service for H5 and the upcoming expansions.
Nightlies, that are now fully functional again will be taken from stable/trunk only, and source code exports will be created from time to time for FS/OS reference directories such as freshmeat, SF.net, etc. BUT there will be no nightly from unstable. People interested in giving a try to it will have to catch it up on their own. This way we should keep newcomers apart from bugs and stability/installation issues the unstable branch may hold now and then.
In the next couple of days we’ll be informing you about more changes, and the ways you can join the team to make L2J roar again.
Oh, and the diff_view thing should be back one of these days.
Gotta say sorry for the delay too, but better late than never. Hoping to hear from you soon. Sincerely.
The L2J development team.