[Xastir-dev] Stable Release: Soon. Really!
Chuck Byam
cbyam at virginia.edu
Mon Jan 19 17:25:59 EST 2004
On Monday 19 January 2004 16:55, Curt, WE7U wrote:
| Given:
| ------
| A) We _need_ to get into the habit of doing "stable" releases more
| often.
|
Much talked about and needs to be done.
| B) It's been suggested that we add some tags to CVS so that people
| can update to the latest stable version without downloading large
| files.
|
A good idea and should be easily implemented.
| C) The previous method of doing a code freeze, doing nothing but
| fixing bugs for some large period of time is too slow (my opinion).
|
I still like the "cooling off period" before a stable release. I don't mind
minor check-ins, but any major chnage in functionality should wait until
after a "stable tag." This timeframe could be shortened though.
|
| I propose the following:
| ------------------------
|
| 1) Impose a code freeze immediately. Bug-fixes are allowed.
|
| 2) Update docs by Jan 31st. If they can't be updated in that
| time-frame, it's not a show-stopper.
|
| 3) Release a new "stable" release on or about Feb 1st.
|
| 4) Tag the release with the "RELEASE" and "STABLE" CVS tags.
|
| 5) Tag any new development snapshots with the "STABLE" CVS tag, if
| it is felt that the release is relatively stable. This will have
| the effect of moving the tag along over time. Anyone wanting the
| latest "stable" release will use the "RELEASE" tag to do their
| checkout.
|
| 6) Attempt to get a new "stable" release out each two to three
| months.
|
|
| This scheme will get the first new stable release out there fairly
| quickly that people will have some confidence in. It will also
| allow people to run newer "STABLE" versions via CVS, but keep them
| away from the unstable development CVS stuff (where I play!).
|
| In my opinion the current "stable" release that we have is too old
| to be useful. I think we've even changed the directory structure
| since then.
|
| Comments as to more suitable tag names are appreciated.
|
| In any case, until/unless we hear otherwise from Chuck, consider the
| code-freeze to be in effect.
I would add that those who have been kind enough to provide binaries be
contacted so that we can post binary packages as well (Hamish are you
listening? :) )
On a side note, but related, I am in the process of reworking the entire
website. That's right, the goth page will be replaced by something a little
easier to read and with greater functionality (live FAQ for example). This
should be finished by the end of the month.
73's KG4IJB
--
Chuck Byam
Network Engineer
University of Virginia Health System
Charlottesville, Virginia
434.982.4426
More information about the Xastir-dev
mailing list