My company is struggling with the issue of service release versus “normal” releases in the context of an on-site application in large organizations that pay for support. First let me define my conditions:
This approach makes the customer happy because we will fix their problem within a day or so, instead of making them wait weeks before the next normal release. In addition, since the service release contains only one small change, they do not need to go through the extensive UAT process, whereas if they move to the next normal release, which may have several versions, they will receive, perhaps, 30 or 40 product changes, which ( in their risky opinion) require an extensive UAT.
The problem is that:
, , ? , ? , , , ?
: , "" , .
(, N , 1 ).
, , .
, , , . , .
, . , - . . , . , . , . ( . , .)
-, . , . .
EDIT, : , , . " " " , ", . , . , .
, unit test ( , ?)
, , . , , .
: " OMG, , , , " ! ", , ( ) , .
. , . . (, webapps - -, gmail?), ( IE6)?.
, , , , . , UAT , , , , , , . , QA.
, , .
, .
, 5.5, , 5.4.0.1, 5.4.1.0, , 5.5 ,
( YMMV):
( "maint" "maintenance" ) . , , (, ), (, , / ).
, , - , , : 1.0 1.1, , . .
, , . , , , . :-)
, ; , , .
- , "". 1.2, 1.3, . . , , , .
Microsoft: , (- > ). , , .
, , - "1.0.1- A" "1.0.1- B", .
. , .