I think the major problems at the moment, IMO, are: - Poor TransactionScope support (NH-3568, NH-3583, NH-2838, NH-2107, NH-2176, NH-2238, NH-2181, NH-2928, NH-2237, NH-2057, NH-3454 and NH-3227) - NH overcaching parameters (NH-3673, NH-2658 and NH-2500)
Perhaps we should focus on fixing these? RP On Monday, August 25, 2014 9:16:03 AM UTC+1, Ricardo Peres wrote: > > Oskar, > > I agree with the "no to breaking API changes" part, but not with "no to > new features". Microsoft introduces new features in minor versions. > > RP > > > On Sunday, August 24, 2014 11:17:24 PM UTC+1, Alexander Zaytsev wrote: >> >> I think what we need to do is to prioritize pull request which we >> currently have, assign versions, close what are not going to be merged, >> etc. >> Also we need to do the same with JIRA issues. >> Because otherwise we will have the same mess as we have now:( >> >> Best Regards, >> Alexander >> >> >> 2014-08-25 9:39 GMT+12:00 Oskar Berggren <oskar.b...@gmail.com>: >> >>> If we want to be serious about following the SemVer spec, there can be >>> no API changes in 4.0.x releases and basically only bug fixes not any real >>> feature-improvements. Furthermore, there can be no breaking changes without >>> an increase in the major number. This would be a change compared to how >>> previous releases have been handled, where breaking changes was allowed >>> even when only the second number changed. >>> >>> Anyway, regarding current branches: >>> >>> 3.3.x release series. Latest is 3.3.4. I don't think we should bother >>> doing any more 3.3.x releases. >>> >>> 3.4.x series. Current is 3.4.0. Looking at NuGet statistics compared to >>> NH4.0 so far, it seems interest is low. I don't think we should bother much >>> with features or improvements here. We can fix regressions and important >>> bugs (especially if there is no workaround). >>> >>> 4.0.x series. This is still the master branch. We could let 4.0.x remain >>> as master for a little more time and have some more fixes and do a 4.0.1, >>> before we branch it off and start work on 4.1.0 on master. Delaying the >>> branching means a little less merging between releases. >>> >>> Time-wise I'm thinking something like: >>> 4.0.1 in september >>> 4.1.0 in november or december >>> >>> Thoughts? >>> >>> /Oskar >>> >>> >>> >>> -- >>> >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "nhibernate-development" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to nhibernate-development+unsubscr...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- --- You received this message because you are subscribed to the Google Groups "nhibernate-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to nhibernate-development+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
