On 5/10/07, Danny Angus <[EMAIL PROTECTED]> wrote:
On 5/9/07, robert burrell donkin <[EMAIL PROTECTED]> wrote:
> so, i would like to propose we allow experimental modules in trunk.
We could even have an "experimental" or "technology preview" distribution.
I like this idea a lot, a whole big lot.
I don't think we should prefix the names, but perhaps we could find
some other means of identifying experimental modules, perhaps using
messages on the startup screen and in the build. E.G.:
the prefixing would be for module names so that it's obvious to
developers which modules are considered experimental
James Mail Server next-major
EXPERIMENTAL MailboxManager has been initialized
Remote Manager Service started plain:4555
EXPERIMENTAL IMAP Service started plain:10143
POP3 Service started plain:110
etc...
+1
this should also include the version number
and ...
ant -Dinclude=experimental dist
or
ant -Dinclude=stable dist
WDYT?
+1
this raises the issues of profiles: there may be several different
experimental profiles. your example would need to be
ant -Dinclude=<profile>
where <profile> is a particular profile
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
