--- "Mark R. Diggory" <[EMAIL PROTECTED]> wrote:
> I'd like us to get together a solid documentation fragment so that 
> releases are cut using the same approach each time.
> 
> Proposal for Current Release Cutting Strategy:
> 
> 1.) Maven should be used to generate releases in the various required 
> formats.
> 
> 2.) We should define or override clear maven goals within the 
> math/maven.xml to produce the release and clearly document the process 
> for the Release Manager.
> 
> 3.) We should start using version numbers and documenting when we cut in 
> the project.xml and cvs tagging.
> 
> commons-math-0.1-dev is sort of a weak and inadequate starting point, 
> recommend we change it to "commons-math-1.0" and start incrementing. 
> Once we establish our release date, I don't see how [dev|alpha|beta|rcX] 
> designations are really going to help us this early on. Lets just cut it 
> and then deal with real issues that arise afterward. If our users really 
> want testing versions, we can start using them.

I think that we should release a 0.1 "soon."  I will post a straw man
release plan / updated task list this evening.  I think 0.1 is a good
starting point. 

> 
> 
> 4.) We should outline the appropriate contents and directory structuring 
> for a release.The current configuration I've worked on produces the 
> following:
> 
> 
> *binary releases* (tar.gz and zip)
> 
> > Archive:  commons-math-0.1-dev.zip
> >   Length     Date   Time    Name
> >  --------    ----   ----    ----
> >         0  01-29-04 09:31   commons-math-0.1-dev/
> >     11358  01-29-04 09:31   commons-math-0.1-dev/LICENSE.txt
> >         0  01-29-04 09:31   commons-math-0.1-dev/docs/
> >         0  01-29-04 09:31   commons-math-0.1-dev/docs/clover/
>  > ...
> >      6103  01-29-04 09:31   commons-math-0.1-dev/docs/apidocs/
> > ...
> >    124140  01-29-04 09:31  
> commons-math-0.1-dev/commons-math-0.1-dev.jar
> >    110531  01-29-04 09:31  
> commons-math-0.1-dev/commons-beanutils-1.5.jar
> >    165119  01-29-04 09:31  
> commons-math-0.1-dev/commons-collections-2.1.jar
> >     72176  01-29-04 09:31  
> commons-math-0.1-dev/commons-discovery-20030211.213356.jar
> >     31605  01-29-04 09:31  
> commons-math-0.1-dev/commons-logging-1.0.3.jar
> >    169763  01-29-04 09:31   commons-math-0.1-dev/commons-lang-2.0.jar
> 

I don't know if bundling the dependent jars is the best idea.  What is the
most prevalent practice among other commons components?  In any case, it
might be better to bundle them in a separate /lib directory.

> 
> *src release* (tar.gz and zip)
> 
> > Archive:  commons-math-0.1-dev-src.zip
> >   Length     Date   Time    Name
> >  --------    ----   ----    ----
> >         0  01-29-04 09:31   commons-math-0.1-dev/
> >         0  01-29-04 09:31   commons-math-0.1-dev/src/
>  >       282  01-29-04 09:31   commons-math-0.1-dev/src/conf/MANIFEST.MF
> >         0  01-29-04 09:31   commons-math-0.1-dev/src/test/...
> ...
> >         0  01-29-04 09:31   commons-math-0.1-dev/src/java/...
> ...
> >         0  01-29-04 09:31   commons-math-0.1-dev/src/experimental/...
> ... (actually think this shouldn't be here).
> 
> >         0  01-29-04 09:31   commons-math-0.1-dev/src/conf/
> >       370  01-29-04 09:31   commons-math-0.1-dev/maven.xml
> >      4692  01-29-04 09:31   commons-math-0.1-dev/project.xml
> 
> This project.xml is the one with the dependencies resolved to a version.
> 
> >       801  01-29-04 09:31   commons-math-0.1-dev/project.properties
> >     11358  01-29-04 09:31   commons-math-0.1-dev/LICENSE.txt
> >      6635  01-29-04 09:31   commons-math-0.1-dev/build.xml
> 
> This build.xml is generated off the above project.xml, so its 
> dependencies are resolved as well.
> 
> 
> 
> *jar release* (jar)
> 
> > Archive:  commons-math-0.1-dev.jar
> >   Length     Date   Time    Name
> >  --------    ----   ----    ----
> >         0  01-29-04 09:30   META-INF/
> >       423  01-29-04 09:30   META-INF/MANIFEST.MF
>  >     11358  01-29-04 09:23   META-INF/LICENSE.txt
> >         0  01-17-04 15:05   org/
> >         0  01-17-04 15:05   org/apache/
> >         0  01-17-04 15:05   org/apache/commons/
> >         0  01-17-04 15:05   org/apache/commons/math/
> >         0  01-17-04 15:05   org/apache/commons/math/analysis/
> >         0  01-29-04 09:24   org/apache/commons/math/complex/
> >         0  01-28-04 16:32   org/apache/commons/math/distribution/
> >         0  01-28-04 16:32   org/apache/commons/math/linear/
> >         0  01-17-04 15:05   org/apache/commons/math/random/
> >         0  01-28-04 16:32   org/apache/commons/math/stat/
> >         0  01-17-04 15:05   org/apache/commons/math/stat/univariate/
> >         0  01-17-04 15:05  
> org/apache/commons/math/stat/univariate/rank/
> >         0  01-17-04 15:05  
> org/apache/commons/math/stat/univariate/moment/
> >         0  01-17-04 15:05  
> org/apache/commons/math/stat/univariate/summary/
> >         0  01-17-04 15:05   org/apache/commons/math/special/
> >         0  01-17-04 15:05   org/apache/commons/math/util/
> >      1609  01-29-04 09:24  
> org/apache/commons/math/analysis/BisectionSolver.class
> >      3033  01-29-04 09:24  
> org/apache/commons/math/analysis/UnivariateRealSolverImpl.class
> >       799  01-29-04 09:24  
> org/apache/commons/math/analysis/UnivariateRealSolver.class
> >       247  01-29-04 09:24  
> org/apache/commons/math/analysis/UnivariateRealFunction.class
> ...
> 
> So the jar has no tests and no experimental code within it.
> 
> 
> 
> Any Comments?
> 
> -Mark
> 
> -- 
> Mark Diggory
> Software Developer
> Harvard MIT Data Center
> http://www.hmdc.harvard.edu
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free web site building tool. Try it!
http://webhosting.yahoo.com/ps/sb/

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to