We have been discussing the creation of a monthly newsletter. The newsletter would be sent to all of our members, at the start of every month. You will be able unsubscribe by simply clicking "unsubscribe". In the newsletter we will discuss recent and upcoming changes, this will allow everyone to be informed and up to date.
The question remains, however. Is there anything special you (the community) would like to see every month relating to this project? Any specific updates/information?
If so, please tell us in this thread so that we can include it.

Expect to see this topic be updated with pictures of what the newsletter will look like and contain.

Maybe the current core development and wat patch will be released when.
The ''big'' updates of the month.
The changes applied to the DB structure of that month.
Just some ideas

If you are, you breath.
If you breath, you talk.
If you talk, you ask.
If you ask, you think.
If you think, you search.
If you search, you experience.
If you experience, you learn.
If you learn, you grow.
If you grow, you wish.
If you wish, you find.
If you find, you doubt.
If you doubt, you question.
If you question, you understand.
If you understand, you know.
If﻿ you know, you want to know more...
And if you want to know more, you are alive...

maybe it saying what you Fixed (Like if their was chat not working, and you guys fixed it, put "We fixed the not being able to chat!", or if u got vehicles working ("We got vehicles working") or w/e the most important Fix's &/or Updates

The upcoming monthly goals. (development wise)
Gives users a little heads up on what to expect for the following month.
Um, what else... Staff changes, if any.
A small unique "tip / trick / guide" into c++

@This_is_junk,
well I didn't mean hold on to a fix for a newletter, but if it's a big project you're working on. (I.E the new dungeon queue thing) and you happen to be like 50% done with it and the newsletter is about to be released it'll be nice to say "Early this month ArcEmu will be having the new 3.3 dungeon queue support."

I think you should focus your efforts on recruiting devs to the project, if that is through writing interesting content through a newsletter then so be it, otherwise you might want to consider trying to build a good documentation around the source itself to ease programmers' appreciation and contribution to the project.

Other than a devotion to recruiting devs I would love to see a section with a few short interviews with DB-devs, script-devs and other devs asking them what they're up to and what they're working on. Constantly letting the community know work is done on their favorite emulator will increase the support and contribution towards the project.

Since Arcemu is a development project, unfortunately there is no such thing. You can however ask around and the community members can surely help you with that.

Guess I should have said it differently. I mean more of revisions that the developers would use to test whatever area they are coding. Since each revision can be from any of the coders on the project, some revisions would make testing other areas impossible or unreliable.

Like I do scripting in PHP. I keep a "stable revision" on my live site to test things from and do changes on my local copies. I upload to test, but revert to the "stable revision" when I'm done usually.

Edit: *cough* well, guess I just saw the binaries thread, which pretty much assume the rev of those is acceptable rev to use for developmental points.

Guess I should have said it differently. I mean more of revisions that the developers would use to test whatever area they are coding. Since each revision can be from any of the coders on the project, some revisions would make testing other areas impossible or unreliable.

Like I do scripting in PHP. I keep a "stable revision" on my live site to test things from and do changes on my local copies. I upload to test, but revert to the "stable revision" when I'm done usually.

I understand what you mean and I hear you trust me. I'd love to have a stable branch. However the problem is that we inherited a very bad codebase from Ascent, and on top of that most of the "developers" of Arcemu have been very very inexperienced. Some of them didn't even know the basics of the language. I can't say about myself that I'm a hardcore software developer myself so I make mistakes too.
So it is just impossible for the moment.
I started to clean up the codebase so hopefully in the foreseeable future it will become feasible.