> In the interest of following the "release often" paradigm I'd like to > propose that we talk about what features to put into 2.2, work on > those and > release 2.2.
2.1 is a branch which exists primarily for bug fixes to v2.1 > I feel a little weird bringing this up since I'm so new to the community, > but I'm seeing a lot of talk about v3 and I'm afraid we're > setting ourselves > up for another year of dev before a release. 1/ it wasn't a year of dev. 2/ we will still be able to release often, but v3 will change a lot between minor versions, whereas v2.1 will remain pretty stable. > So, I guess I should start off. A feature that I think is really important > is an easier way to add custom mailets to James, so that we don't have to > require the user to pack their mailets up in the james.sar. We seem to get > that question a lot and it seems to be to be the biggest obstacle that new > users/developers run into when trying to take advantage of the the thing > that sets James apart from other mail servers. this is slated for v3, check out the wiki to see what else we've come up with so far.. d. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
