Yup, I'll agree with that.. But there can be several levels of 'releases'.. For company stuff I would assume the 'small incremental releases' thing would mean 'upload/update into the central directory of stuff' (cvs, or whereever), so that any other product/dept that might need something fixed, can test/use/integrate it.

QA only (should get) gets it when its actually released for a customer, which they then test together with other actual product releases meant to be delivered to a customer.

At least, thats how the $company I work for does it. Eg the defect/feature/whatever is 'finished' from the developers point of view.

I'd say, you're both right.

C.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

Outside of code tags, you may need to use entities for some characters:

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.