| [stellation-res] Imposing some process |
As Jonathan pointed out in his earlier message: we're reaching a point where it's about time for some project management process. There's a couple of things that I think we should try to cover. The biggest issue is release management. What I mean by this is, if we expect people to use Stellation, we need to have regular releases, where we designate a release for a version of the system that is stable and tested on all platforms, and a labelling scheme for releases so that people can reliably know what version of the system they're using. I'd like to start posting regularly on freshmeat whenever we create a new labelled release. We need people to be designated testers for different platforms and databases. When we plan a release, we need to have it tested on every supported combination of databases and operating systems. We also need some system for deciding when it's time for a release. For now, I'd like to propose planning a release around the latest version of the system, with Jonathan's new database code. Can we get volunteers to be designated testers for particular db/OS combinations? I'll be glad to cover Linux/Postgres, and Linux/MySQL. Unless he corrects me, I think Jonathan volunteered for Windows/MySQL, Windows/Postgres, and Windows/Firebird. So we still need: Linux/Firebird Linux/DB2 Linux/Oracle For now, unless we get volunteers, I think windows/Oracle, and Windows/DB2 are probably not necessary. We'll worry about getting them covered later. -Mark -- Mark Craig Chu-Carroll, IBM T.J. Watson Research Center *** The Stellation project: Advanced SCM for Collaboration *** http://www.eclipse.org/stellation *** Work Email: mcc@xxxxxxxxxxxxxx ------- Personal Email: markcc@xxxxxxxxxxx
Attachment:
signature.asc
Description: This is a digitally signed message part