From: Vincent M. <vm...@oc...> - 2001-08-16 22:26:14
|
----- Original Message ----- From: "Steve Freeman" <st...@m3...> To: <moc...@li...> Sent: Thursday, August 16, 2001 10:47 PM Subject: Re: [Mockobjects-java-dev] [Proposal] List of tasks for release 0.02 > I'm a bit concerned if we cannot release _anything_ before all of this is done, given our current rate of progress. I agree that all of this should be part of a proper release, but we have ongoing code changes to the library which need to be released. Can we have a mechanism for interim releases as well as official releases? I don't think T1-T9 are big tasks. Documentation as important as code if not even more ... and for the time being there isn't much ... So I don't agree that we need to release code prior to documentation. The code is in CVS and accessible to anyone. Interim release would correspond to snapshots (or nightly builds), yes that's something that we could do but I don't think it is the issue. What source do you want to release ? > > T1 should be the original paper, perhaps with extensions. ok > T2 I should take a look at that too > T3 Guess I could do that > T4 Can you extend the current version I was thinking about coding standards to normal java code not Mock Objects naming conventions but yes we can extend the current although I am not sure they belong to the same document. > T5 not sure what to put there. easy : Servlet API mock implementation that does this this and this, JDBC one, ... Expectation classes for this, ..... > T7 versioning, sure. But we should be releasing sources, not javadoc, except for occasional notes. Maybe a common header that says Just Look at the Code? I mentioned "where needed". That would be to the core framework and may not be needed to the mock implementations themselves ? > T8 getting there. you see we're almost there. -Vincent > > > ----- Original Message ----- > From: "Vincent Massol" <vm...@oc...> > To: <moc...@li...> > Sent: Wednesday, August 15, 2001 3:14 PM > Subject: [Mockobjects-java-dev] [Proposal] List of tasks for release 0.02 > > > > Here is a list of tasks that I propose for Release 0.02. Can you please > > state your agreement and others that would like to see. I'll wait for your > > approval before entering them in the todo page : > > > > T1 - [doc] What are MockObjects? > > T2 - [doc] Difference between MO and Stubs ? > > T3 - [doc] Goal page that explains short term and long term goals of the > > project > > T4 - [doc] Coding conventions (in a "Developer" menu) > > T5 - [doc] Features page > > T6 - [doc] Release process page (in a "Developer" menu) > > T7 - [code] add javadoc to all code where needed + add version number to > > sources (@version @version@) + packages.html + overview.html > > T8 - [code] Code aligned with coding conventions (and MO naming conventions > > already present on the web site) > > T9 - [build] finalized build process (still need to finalize directory > > structure + manage examples + manage extensions) > > > > These are the "mnimum" set of task that is can we before the release 0.02. > > > > Tell me also if you wish to volunteer for a given task. There can be several > > persons volunteering for the same task. > > > > I volunteer for T2, T4, T6, T9. > > > > Thanks > > -Vincent > > > > > > _______________________________________________ > > Mockobjects-java-users mailing list > > Moc...@li... > > http://lists.sourceforge.net/lists/listinfo/mockobjects-java-users > > > > > > > > > > _______________________________________________ > > Mockobjects-java-dev mailing list > > Moc...@li... > > http://lists.sourceforge.net/lists/listinfo/mockobjects-java-dev > > > 2¡rjzS,´'yuS²q®z¶-²¢-³²~¡n¶½ |