| 1 |
<!-- |
| 2 |
Licensed to the Apache Software Foundation (ASF) under one or more |
| 3 |
contributor license agreements. See the NOTICE file distributed with |
| 4 |
this work for additional information regarding copyright ownership. |
| 5 |
The ASF licenses this file to you under the Apache License, Version 2.0 |
| 6 |
(the "License"); you may not use this file except in compliance with |
| 7 |
the License. You may obtain a copy of the License at |
| 8 |
|
| 9 |
http://www.apache.org/licenses/LICENSE-2.0 |
| 10 |
|
| 11 |
Unless required by applicable law or agreed to in writing, software |
| 12 |
distributed under the License is distributed on an "AS IS" BASIS, |
| 13 |
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. |
| 14 |
See the License for the specific language governing permissions and |
| 15 |
limitations under the License. |
| 16 |
--> |
| 17 |
<!-- |
| 18 |
TEMPLATE FOR CREATING A RELEASE NOTE FOR A SIGNIFICANT JIRA ENTRY |
| 19 |
|
| 20 |
This is a standard form for filling in a release note for a |
| 21 |
significant issue logged in JIRA. This could be an issue |
| 22 |
which introduces a new feature. Or it could be an issue |
| 23 |
which changes Derby in a way which breaks existing |
| 24 |
applications. By using this standard form, you help the |
| 25 |
release manager generate documentation for the next |
| 26 |
release. |
| 27 |
|
| 28 |
When you are done filling in this form, attach it to the appropriate |
| 29 |
JIRA as "releaseNote.html". You can improve your release note as |
| 30 |
many times as you like. The release machinery will simply use the |
| 31 |
last version of releaseNote.html attached to the JIRA. |
| 32 |
|
| 33 |
This template has the following standard sections. Brackets mark |
| 34 |
optional sections. |
| 35 |
|
| 36 |
Summary of Change |
| 37 |
Symptoms Seen by Applications Affected by Change |
| 38 |
[ Incompatibilities with Previous Release ] |
| 39 |
Rationale for Change |
| 40 |
[ Application Changes Required ] |
| 41 |
|
| 42 |
Go through this template and replace all instances of "????" with |
| 43 |
appropriate text. Remove the optional sections if you don't need them. |
| 44 |
|
| 45 |
--> |
| 46 |
|
| 47 |
<html> |
| 48 |
<body> |
| 49 |
|
| 50 |
<!-- |
| 51 |
SUMMARIZE THE ISSUE. This is a one line, one sentence summary of the |
| 52 |
issue. It serves as the title for the issue in the Issues section of |
| 53 |
the full Release Notes. |
| 54 |
|
| 55 |
For instance: |
| 56 |
|
| 57 |
Applications may no longer open two InputStreams on the same ResultSet column. |
| 58 |
--> |
| 59 |
|
| 60 |
<h4>Summary of Change</h4> |
| 61 |
<p> |
| 62 |
???? |
| 63 |
</p> |
| 64 |
|
| 65 |
|
| 66 |
<!-- |
| 67 |
DESCRIBE WHAT IT IS THAT THE USER ACTUALLY SEES WHEN THE PROBLEM OCCURS. |
| 68 |
|
| 69 |
For instance: |
| 70 |
|
| 71 |
In the previous release, applications were able to open two |
| 72 |
InputStreams on the same column. Depending on how these streams |
| 73 |
interacted, the value siphoned out of the column was erratic. Now |
| 74 |
Derby raises a SQLException when the application attempts to create |
| 75 |
the second InputStream. |
| 76 |
--> |
| 77 |
|
| 78 |
<h4>Symptoms Seen by Applications Affected by Change</h4> |
| 79 |
<p> |
| 80 |
???? |
| 81 |
</p> |
| 82 |
|
| 83 |
|
| 84 |
<!-- |
| 85 |
OPTIONAL: DESCRIBE INCOMPATIBILITIES WITH PREVIOUS RELEASE, IF ANY. |
| 86 |
|
| 87 |
For instance: |
| 88 |
|
| 89 |
Applications which open two InputStreams on the ResultSet column now |
| 90 |
fail. |
| 91 |
--> |
| 92 |
|
| 93 |
<h4>Incompatibilities with Previous Release</h4> |
| 94 |
<p> |
| 95 |
???? |
| 96 |
</p> |
| 97 |
|
| 98 |
|
| 99 |
<!-- |
| 100 |
DESCRIBE WHY THE CHANGE WAS MADE. |
| 101 |
|
| 102 |
For instance: |
| 103 |
|
| 104 |
The previous behavior violated the JDBC standard. The new behavior |
| 105 |
is correct. |
| 106 |
--> |
| 107 |
|
| 108 |
<h4>Rationale for Change</h4> |
| 109 |
<p> |
| 110 |
???? |
| 111 |
</p> |
| 112 |
|
| 113 |
|
| 114 |
<!-- |
| 115 |
OPTIONAL: DESCRIBE HOW TO REVERT TO THE PREVIOUS BEHAVIOR OR |
| 116 |
OTHERWISE AVOID THE INCOMPATIBILITIES INTRODUCED BY THIS CHANGE. |
| 117 |
|
| 118 |
For instance: |
| 119 |
|
| 120 |
Users must recode applications which open multiple streams on the same column. |
| 121 |
--> |
| 122 |
|
| 123 |
<h4>Application Changes Required</h4> |
| 124 |
<p> |
| 125 |
???? |
| 126 |
</p> |
| 127 |
|
| 128 |
|
| 129 |
</body> |
| 130 |
</html> |