[jboss-jira] [JBoss JIRA] Updated: (HIBERNATE-87) Correct version numbers in readme.txt and changelog.txt

[ http://jira.jboss.com/jira/browse/HIBERNATE-87?page=all ] Gail Badner updated HIBERNATE-87: --------------------------------- Summary: Correct version numbers in readme.txt and changelog.txt (was: Correct version numbers in readme.txt) Description: The standalone that will correspond with EAP 4.2 CP03 is referred to as Hibernate 3.2.4.sp1.cp03. Although changes were made to Hibernate source code for EAP CP01 and CP02 there are no corresponding Hibernate standalone releases for these versions. The current changelog.txt for Hibernate 3.2.4.sp1.cp03 is at http://anonsvn.jboss.org/repos/hibernate/core/branches/Branch_3_2_4_SP1_C... The issues listed for 3.2.4.sp1.cp01 were fixed in EAP 4.2 CP01 and the issue listed for 3.2.4.sp1.cp03 (typo, should have been cp02) was fixed in EAP 4.2 CP02. There have been no changes to Hibernate source code for EAP 4.2 CP03. I don't think that the hibernate issues fixed in EAP 4.2 CP01 made it to the EAP release notes. Shouldn't these fixes be recorded somewhere for EAP? The hibernate issue fixed in CP02 is correctly listed in the EAP 4.2 CP02 release notes. If changelog.txt and readme.txt are for the standalone only, and if 3.2.4.sp1.cp03 is the first "supported" hibernate standalone we will support, then shouldn't all the new issues be documented as changes in 3.2.4.sp1.cp03? Is there a reason to also break out the changes by the EAP version where it was fixed? was:Should bug fixes be assigned to correspond with the bug fix in EAP 4.2? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira