[fdo-internals] RE: Relase process (was Trying to Deploy FDO to Web)

[Greg Boone]

I have talked to Orest and Brent. It appears their schedules are full for the next few weeks. I think it will be highly doubtful that the proposed SQL Server changes will make it into the 3.4.0 release. I am very hesitant to simply make the capabilities changes without robust testing in MapGuide. My recommendation at this point would be to release 3.4.0 and subsequently release a patch that contains the proposed changes for Tickets #469 and #470. Customers willing to test the patch can download it and determine its usefulness.

Greg

-----Original Message-----
From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Greg Boone
Sent: Monday, March 02, 2009 4:33 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] RE: Relase process (was Trying to Deploy FDO to Web)

Let's take it issue by issue. I am willing to test the DELAYLOAD issue. We just will need someone to test the SQLServer Provider changes. Maybe I can convince Orest to do this in co-ordination with Brent.

Greg

-----Original Message-----
From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Jason Birch
Sent: Monday, March 02, 2009 4:29 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] RE: Relase process (was Trying to Deploy FDO to Web)

Yes, understood.  I was probably just reading too much into your initial
message.

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.

Jason

-----Original Message-----
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
Web)

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.

_______________________________________________
fdo-internals mailing list
fdo-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/fdo-internals
_______________________________________________
fdo-internals mailing list
fdo-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/fdo-internals