[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-devel] How/when to write a Design Document
- Date: Tue, 23 Oct 2012 15:45:10 -0400 (EDT)
- From: Tim St Clair <tstclair@xxxxxxxxxx>
- Subject: Re: [Condor-devel] How/when to write a Design Document
So I've mentioned it before, but I think it worth vetting in a larger audience now that you've brought it up.
Why attach a separate MSFT.doc to a ticket, vs. making the ticket be the design doc, and having all the sections you mentioned?
Cheers,
Tim
----- Original Message -----
> From: "Todd Tannenbaum" <tannenba@xxxxxxxxxxx>
> To: "Condor Developers" <condor-devel@xxxxxxxxxxx>
> Sent: Tuesday, October 23, 2012 2:28:13 PM
> Subject: [Condor-devel] How/when to write a Design Document
>
> I wrote up a howto for writing design documents, along with links to
> examples. See
> https://condor-wiki.cs.wisc.edu/index.cgi/wiki?p=DesignDoc
>
> f your change is an enhancement (new feature) or large bug fix, you
> will
> need to author and attach a design document to the ticket page for
> architecture review and get it approved before code contributions
> will
> be accepted.
> regards,
> Todd
>
>
> --
> Todd Tannenbaum <tannenba@xxxxxxxxxxx> University of
> Wisconsin-Madison
> Center for High Throughput Computing Department of Computer
> Sciences
> Condor Project Technical Lead 1210 W. Dayton St. Rm #4257
> Phone: (608) 263-7132 Madison, WI 53706-1685
> _______________________________________________
> Condor-devel mailing list
> Condor-devel@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/condor-devel
>