diff options
author | vorlon <vorlon@alioth.debian.org> | 2007-11-21 17:29:21 +0000 |
---|---|---|
committer | vorlon <vorlon@alioth.debian.org> | 2007-11-21 17:29:21 +0000 |
commit | 58b37572718ed65d1b143f44de16aa5efb512f11 (patch) | |
tree | 96694e5871586bd21d9b2b91f9a277111ace0812 /Roadmap | |
parent | f24db2434a26f04e1761c6dbde69d4be999a1cfc (diff) | |
download | samba-58b37572718ed65d1b143f44de16aa5efb512f11.tar.gz |
Load samba-3.0.27a into branches/upstream.upstream/3.0.27a
git-svn-id: svn://svn.debian.org/svn/pkg-samba/branches/upstream@1583 fc4039ab-9d04-0410-8cac-899223bdd6b0
Diffstat (limited to 'Roadmap')
-rw-r--r-- | Roadmap | 35 |
1 files changed, 35 insertions, 0 deletions
diff --git a/Roadmap b/Roadmap new file mode 100644 index 0000000000..c4359b1387 --- /dev/null +++ b/Roadmap @@ -0,0 +1,35 @@ +Copyright (C) 1997-2003 Samba-Team + +The Samba-Team are committed to an aggressive program to deliver quality +controlled software to a well defined roadmap. + +The current Samba series of Samba 3.0.0 is called the "Domain Integration" +release. + +The following development objectives for future releases +are in progress: +---------------------------------------------------------------------------- +Samba-3.0.20 The release that is focussing on scalability and domain + integration and migration. See the WHATSNEW.txt file for + update notes. + +Samba-3.0.x Improvements in Management and Migration tools, & + general code stabilization work. It is recommended to use + only stable releases in production environments. You have + been duly warned! + +Samba-3.1.x The test bed for all new developments. Do NOT use in any + production environment. + +Samba-4 Danger Will Robinson, a big code clean up with major + system redesign. More will be announced as this work + starts to take shape. + + +Note that it is a given that the Samba-Team will continue to track +Windows (NT/200x) update releases, ensuring that Samba will work +well with whatever "Beta" releases Redmond throws our way :-). + +You may also note that the release numbers get fuzzier the +further into the future the objectives get. This is intentional +as we cannot commit to exact timeframes. |