[jira] Created: (JDO-585) Process for providing post-release notes for tck users

Process for providing post-release notes for tck users
------------------------------------------------------

                 Key: JDO-585
                 URL: https://issues.apache.org/jira/browse/JDO-585
             Project: JDO
          Issue Type: Improvement
          Components: tck2, tck2-legacy
    Affects Versions: JDO 2 maintenance release 1, JDO 2 maintenance release 2, JDO 2.0 TCK challenge fixes
            Reporter: Michelle Caisse
            Assignee: Michelle Caisse
            Priority: Minor


There is a README.txt file that is checked in to the top-level of trunk, releases, and branches. It is distributed with each source package. To provide release notes that become available after the release is built, I suggest adding the line "View the latest version of this file online.", with a link to the online version (which of course will have this self-referential line).

Each branch has its own version of README.txt. When a maintenance  release (e.g. 2.1) needs to be updated, we add a new bug fix branch (e.g. 2.1.1). We don't create a release from this branch, but tell users to check it out of svn. When we provide a bug fix release to a maintenance release we need to update README.txt in the parent branch, adding the following line: "This release has been deprecated. Please use version 2.x.y.", with a link to the svn web interface for that version.


--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

     [ https://issues.apache.org/jira/browse/JDO-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Craig Russell updated JDO-585:
------------------------------

    Fix Version/s: JDO 2 maintenance release 2

> Process for providing post-release notes for tck users
> ------------------------------------------------------
>
>                 Key: JDO-585
>                 URL: https://issues.apache.org/jira/browse/JDO-585
>             Project: JDO
>          Issue Type: Improvement
>          Components: tck2, tck2-legacy
>    Affects Versions: JDO 2 maintenance release 1, JDO 2 maintenance release 2, JDO 2.0 TCK challenge fixes
>            Reporter: Michelle Caisse
>            Assignee: Michelle Caisse
>            Priority: Minor
>             Fix For: JDO 2 maintenance release 2
>
>
> There is a README.txt file that is checked in to the top-level of trunk, releases, and branches. It is distributed with each source package. To provide release notes that become available after the release is built, I suggest adding the line "View the latest version of this file online.", with a link to the online version (which of course will have this self-referential line).
> Each branch has its own version of README.txt. When a maintenance  release (e.g. 2.1) needs to be updated, we add a new bug fix branch (e.g. 2.1.1). We don't create a release from this branch, but tell users to check it out of svn. When we provide a bug fix release to a maintenance release we need to update README.txt in the parent branch, adding the following line: "This release has been deprecated. Please use version 2.x.y.", with a link to the svn web interface for that version.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

     [ https://issues.apache.org/jira/browse/JDO-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michelle Caisse updated JDO-585:
--------------------------------

    Attachment: HowToReleaseJDO.html

Converted this doc to html, added new process for post-release notes.

> Process for providing post-release notes for tck users
> ------------------------------------------------------
>
>                 Key: JDO-585
>                 URL: https://issues.apache.org/jira/browse/JDO-585
>             Project: JDO
>          Issue Type: Improvement
>          Components: tck2, tck2-legacy
>    Affects Versions: JDO 2 maintenance release 1, JDO 2 maintenance release 2, JDO 2.0 TCK challenge fixes
>            Reporter: Michelle Caisse
>            Assignee: Michelle Caisse
>            Priority: Minor
>             Fix For: JDO 2 maintenance release 2
>
>         Attachments: HowToReleaseJDO.html
>
>
> There is a README.txt file that is checked in to the top-level of trunk, releases, and branches. It is distributed with each source package. To provide release notes that become available after the release is built, I suggest adding the line "View the latest version of this file online.", with a link to the online version (which of course will have this self-referential line).
> Each branch has its own version of README.txt. When a maintenance  release (e.g. 2.1) needs to be updated, we add a new bug fix branch (e.g. 2.1.1). We don't create a release from this branch, but tell users to check it out of svn. When we provide a bug fix release to a maintenance release we need to update README.txt in the parent branch, adding the following line: "This release has been deprecated. Please use version 2.x.y.", with a link to the svn web interface for that version.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

     [ https://issues.apache.org/jira/browse/JDO-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michelle Caisse updated JDO-585:
--------------------------------

    Attachment: README.html

Converted to html, reorganized content. This version is for trunk, but will be merged to the 2.1.1 branch and edited there to include information about changes to the 2.1 release.

> Process for providing post-release notes for tck users
> ------------------------------------------------------
>
>                 Key: JDO-585
>                 URL: https://issues.apache.org/jira/browse/JDO-585
>             Project: JDO
>          Issue Type: Improvement
>          Components: tck2, tck2-legacy
>    Affects Versions: JDO 2 maintenance release 1, JDO 2 maintenance release 2, JDO 2.0 TCK challenge fixes
>            Reporter: Michelle Caisse
>            Assignee: Michelle Caisse
>            Priority: Minor
>             Fix For: JDO 2 maintenance release 2
>
>         Attachments: HowToReleaseJDO.html, README.html
>
>
> There is a README.txt file that is checked in to the top-level of trunk, releases, and branches. It is distributed with each source package. To provide release notes that become available after the release is built, I suggest adding the line "View the latest version of this file online.", with a link to the online version (which of course will have this self-referential line).
> Each branch has its own version of README.txt. When a maintenance  release (e.g. 2.1) needs to be updated, we add a new bug fix branch (e.g. 2.1.1). We don't create a release from this branch, but tell users to check it out of svn. When we provide a bug fix release to a maintenance release we need to update README.txt in the parent branch, adding the following line: "This release has been deprecated. Please use version 2.x.y.", with a link to the svn web interface for that version.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

    [ https://issues.apache.org/jira/browse/JDO-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608885#action_12608885 ]

Michelle Caisse commented on JDO-585:
-------------------------------------

Checked in updated versions of HowToReleaseJDO.html and README.html.  revision: 672352  

> Process for providing post-release notes for tck users
> ------------------------------------------------------
>
>                 Key: JDO-585
>                 URL: https://issues.apache.org/jira/browse/JDO-585
>             Project: JDO
>          Issue Type: Improvement
>          Components: tck2, tck2-legacy
>    Affects Versions: JDO 2 maintenance release 1, JDO 2 maintenance release 2, JDO 2.0 TCK challenge fixes
>            Reporter: Michelle Caisse
>            Assignee: Michelle Caisse
>            Priority: Minor
>             Fix For: JDO 2 maintenance release 2
>
>         Attachments: HowToReleaseJDO.html, README.html
>
>
> There is a README.txt file that is checked in to the top-level of trunk, releases, and branches. It is distributed with each source package. To provide release notes that become available after the release is built, I suggest adding the line "View the latest version of this file online.", with a link to the online version (which of course will have this self-referential line).
> Each branch has its own version of README.txt. When a maintenance  release (e.g. 2.1) needs to be updated, we add a new bug fix branch (e.g. 2.1.1). We don't create a release from this branch, but tell users to check it out of svn. When we provide a bug fix release to a maintenance release we need to update README.txt in the parent branch, adding the following line: "This release has been deprecated. Please use version 2.x.y.", with a link to the svn web interface for that version.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

     [ https://issues.apache.org/jira/browse/JDO-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michelle Caisse resolved JDO-585.
---------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: JDO 2 maintenance release 2)

Updated HowToReleaseJDO.html with process changes.

> Process for providing post-release notes for tck users
> ------------------------------------------------------
>
>                 Key: JDO-585
>                 URL: https://issues.apache.org/jira/browse/JDO-585
>             Project: JDO
>          Issue Type: Improvement
>          Components: tck2, tck2-legacy
>    Affects Versions: JDO 2 maintenance release 1, JDO 2 maintenance release 2, JDO 2.0 TCK challenge fixes
>            Reporter: Michelle Caisse
>            Assignee: Michelle Caisse
>            Priority: Minor
>         Attachments: HowToReleaseJDO.html, README.html
>
>
> There is a README.txt file that is checked in to the top-level of trunk, releases, and branches. It is distributed with each source package. To provide release notes that become available after the release is built, I suggest adding the line "View the latest version of this file online.", with a link to the online version (which of course will have this self-referential line).
> Each branch has its own version of README.txt. When a maintenance  release (e.g. 2.1) needs to be updated, we add a new bug fix branch (e.g. 2.1.1). We don't create a release from this branch, but tell users to check it out of svn. When we provide a bug fix release to a maintenance release we need to update README.txt in the parent branch, adding the following line: "This release has been deprecated. Please use version 2.x.y.", with a link to the svn web interface for that version.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

     [ https://issues.apache.org/jira/browse/JDO-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Bouschen updated JDO-585:
---------------------------------

    Fix Version/s: JDO 2 maintenance release 2
                   JDO 2 maintenance release 1 update 1

> Process for providing post-release notes for tck users
> ------------------------------------------------------
>
>                 Key: JDO-585
>                 URL: https://issues.apache.org/jira/browse/JDO-585
>             Project: JDO
>          Issue Type: Improvement
>          Components: tck2, tck2-legacy
>    Affects Versions: JDO 2 maintenance release 1, JDO 2 maintenance release 2, JDO 2.0 TCK challenge fixes
>            Reporter: Michelle Caisse
>            Assignee: Michelle Caisse
>            Priority: Minor
>             Fix For: JDO 2 maintenance release 1 update 1, JDO 2 maintenance release 2
>
>         Attachments: HowToReleaseJDO.html, README.html
>
>
> There is a README.txt file that is checked in to the top-level of trunk, releases, and branches. It is distributed with each source package. To provide release notes that become available after the release is built, I suggest adding the line "View the latest version of this file online.", with a link to the online version (which of course will have this self-referential line).
> Each branch has its own version of README.txt. When a maintenance  release (e.g. 2.1) needs to be updated, we add a new bug fix branch (e.g. 2.1.1). We don't create a release from this branch, but tell users to check it out of svn. When we provide a bug fix release to a maintenance release we need to update README.txt in the parent branch, adding the following line: "This release has been deprecated. Please use version 2.x.y.", with a link to the svn web interface for that version.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.