/me debates inserting a proxy form... striker <=> gstein :-) :-)
On Mon, Oct 28, 2002 at 03:16:45PM -0000, [EMAIL PROTECTED] wrote: > striker 2002/10/28 07:16:45 > > Modified: . STATUS > Log: > More votes. > > Revision Changes Path > 1.51 +16 -13 commons/STATUS > > Index: STATUS > =================================================================== > RCS file: /home/cvs/commons/STATUS,v > retrieving revision 1.50 > retrieving revision 1.51 > diff -u -r1.50 -r1.51 > --- STATUS 27 Oct 2002 15:25:46 -0000 1.50 > +++ STATUS 28 Oct 2002 15:16:45 -0000 1.51 > @@ -118,7 +118,7 @@ > +0.7: mas > -0: aaron (too early) > -0.9: sanders > - -1: gstein, fitz, jerenkrantz > + -1: gstein, fitz, jerenkrantz, striker > > o A number of very valid issues have been brought up on the > list. We need to figure out how the Commons Project will > @@ -137,10 +137,10 @@ > o Default commit privileges > > - Commons-wide > - -1: gstein > + -1: gstein, striker > > - Per-component > - +1: gstein > + +1: gstein, striker > > - Per-component with self-chosen aggregation > +1: gstein > @@ -274,7 +274,7 @@ > > - Should we have a minimum set of requirements before components > are released? > - +1: donaldp, gstein (mixed, see below) > + +1: donaldp, gstein (mixed, see below), striker > -1: > > - If yes to above then which things should be part of minimum > @@ -283,12 +283,13 @@ > documentation: require basic overview and user docs > +1: donaldp > -0: gstein (recommend highly, but let the committers determine > - what is right for the component) > + what is right for the component), > + striker > -1: > > uptodate website: require website be updated to latest release > but may still host previous release docs. > - +1: donaldp, gstein > + +1: donaldp, gstein, striker > -1: > > unit tests: (okay so this will never get consensus but ...) > @@ -296,12 +297,13 @@ > -1: gstein (unit tests should be recommended, but not > mandated; I also find it unreasonable for initial > development/pre-alpha releases, but it can make > - sense for "final" types of releases) > + sense for "final" types of releases), > + striker > > versioning standard: derived from > http://apr.apache.org/versioning.html > http://jakarta.apache.org/commons/versioning.html > - +1: donaldp, gstein > + +1: donaldp, gstein, striker > -1: > > release process: derived from > @@ -310,7 +312,8 @@ > > http://cvs.apache.org/viewcvs.cgi/jakarta-ant/ReleaseInstructions?rev=1.9.2.1&content-type=text/vnd.viewcvs-markup > +1: donaldp > -1: gstein (we should provide "best practices" but allow each > - components' committers to define their rules) > + components' committers to define their rules), > + striker > > deprecation process: (java specific?) > > http://jakarta.apache.org/turbine/maven/development/deprecation.html > @@ -323,7 +326,8 @@ > http://jakarta.apache.org/turbine/maven/development/branches.html > +1: donaldp > -1: gstein (we should provide "best practices" but allow each > - components' committers to define their rules) > + components' committers to define their rules), > + striker > > > Candidate Projects: > @@ -395,8 +399,7 @@ > (this is really TOPICNAME-dev@ where I preselected > "clients" for TOPICNAME; this question is whether this > style would be appropriate) > - +1: gstein, striker (assuming 'clients' is the label we put > - on this and alike components) > + +1: gstein, striker > -0: sanders > -1: aaron (what is "clients"? I'd probably be +1 if I knew > what that was) > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- Greg Stein, http://www.lyra.org/
