As announced 20 days ago, it is time to start testing the current
unstable development version. We are still missing a few backends,
but hopefully they will be added as soon as possible. I will wrap up
a new snapshot after the weekend, and move over to the next phase.
The test phase is the most important part before of a new release. We
need to test the snapshots as much as possible, to make sure no stupid
bugs survives before the next release. Try to compile it on as many
platforms and compilers as possible. Test it on as many scanners as
possible. If you find any problems, report them to the list or send a
message to the maintainer.
I plan to end the test phase after tree weeks. When it is over, we
enter code freeze where we only grave fixes bugs and update
documentation to make sure everything is up to date when we make a
release. I hope a 14 day code freeze is enough.
Schedule:
2000-01-22 Start test phase
2000-02-12 Start code freeze
2000-02-26 New release
If everyone pull together, we can have a new release out the door
within 1.5 month.
Happy hacking,
-- ##> Petter Reinholdtsen <## | pere@td.org.uit.no-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
This archive was generated by hypermail 2b29 : Thu Jan 20 2000 - 08:16:29 PST