[fdo-internals] RE: Relase process (was Trying to Deploy FDO to
Jason.Birch at nanaimo.ca
Mon Mar 2 16:28:30 EST 2009
Yes, understood. I was probably just reading too much into your initial
I don't have any problem with requiring testing of submissions at this
point in the cycle (actually, at any point in the cycle), just worried
that we don't that the resources to apply the kind of intensive Q/A that
a commercial product requires.
From: Greg Boone
Sent: March-02-09 1:13 PM
To: FDO Internals Mail List
Subject: [fdo-internals] RE: Relase process (was Trying to Deploy FDO to
I do not disagree with anything you say. However, we have to have to
follow some common sense principles too. I am not stating that Autodesk
will determine which defects are submitted to the 3.4.0 release stream.
I only state that someone has to QA proposed defect fixes once we get
into Release Candidate territory. That can be Autodesk OSGeo members if
they nominate a defect, or it can be done by other contributors as well.
We have to have someone verify that a fix works outside the contributor
that submits the fix.
I am all for pushing build/installer responsibility out to the
community, but we are not there yet. Hopefully we can get that in place
for the next release. As for Sandboxes/tags, that is fine as well.
However, that does not deal with the possibility that a change made in
the RC timeframe will not get adequate vetting approval. Bottom line, if
a defect needs to be submitted at this point in the process, it needs to
be tested by someone.
More information about the fdo-internals