From: Frank W. Z. <fz...@om...> - 2005-12-21 16:07:03
|
For all developers/administrators... With the addition of Herman to our "staff", the project bylaws are now officially in effect. However, I'd like to break them already :) Specifically with regard to the release pattern... as specified in the bylaws, each release is supposed to go through an alpha-beta-release cycle. We haven't been doing that to this point, which has been fine. Now though, I'd like to get opinions on how to proceed... The current release is 1.0beta1. My intention before today was to continue to bump the beta number for a while, i.e., 1.0beta2, 1.0beta3, etc., until we decide it is release-quality. This doesn't really fit the specified release pattern, although I suppose it isn't specifically prohibited either. My question is, is this plan OK with everyone? (Tamas and Herman that is!). Also, I think it would be easier to continue releases as has been done so far, that is, no vote, and releases are, usually, every weekend (except when there have been no real changes). I wrote the bylaws with more developers in mind, so some things don't make a whole lot of sense with only three of us. For isntance, technically, we should start voting now for every release, but we also should also hold that vote open for two weeks. That doesn't make a whole lot of sense to me with only three of us. So, do either of you object to leaving things as-is in terms of releases, until we release a 1.0 GA? At that point I think we definitely *should* do things as specified, but while still in beta I'm not sure it matters as much. Opinions? -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com AIM: fzammetti Yahoo: fzammetti MSN: fza...@ho... |