I like this versioning model. It makes the path-forward a little more clear.
In terms of a 4.1 RC, is there any chance of getting pending pull requests looked at? I'm currently having to use a personal build which has a fix for NH-3904. On Wednesday, November 16, 2016 at 5:56:25 AM UTC-5, Oskar Berggren wrote: > > > > 2016-11-16 2:20 GMT+00:00 Surya Pratap <pratap...@gmail.com <javascript:>> > : > >> Should'nt this be 5.1-pre or -beta or something 5.whatever without the >> tag will then be the API stable version. >> Nuget users will face less confusion if the tags are there since the >> tagged versions will go to the pre-release section. > > > No, the point of my suggestion was that these releases would NOT be > prereleases. We've had alpha/beta releases since forever, but these > releases would be intended as production quality BUT you have to accept > that API breakage might happen more frequently. If one can't accept that, > then you would stay on the "long-term release" to basically only get bug > fixes and minor feature additions. > > The aim would be to avoid good-to-go patches to just sit around as pull > requests for years before ending up in a release, such as (some of) the > ones here: > https://github.com/nhibernate/nhibernate-core/milestone/1 > > One notable difference in practice would be where bug fixes are applied. > Suppose we have released these versions: > 4.2 > 5.0 > 5.1 > 5.2 > > If there is an important bug fix, we might release 4.2.1, 5.0.1, 5.1.1 and > 5.2.1. Under the new scheme we would only do bugfixes for the long-term > releases and the latest release: 4.2.1 and 5.2.1, in this example. > > > > For NuGet there are multiple options: > > 1) Provide separate packages, something like NHibernate-LT and > NHibernate-Edge, where one would be updated less frequently. > > 2) Or continue to use just one package, document the scheme, and those > that feel they can't cope with changing NHibernate API more than every few > years would use version pinning. > > > I favor the second since it seems easier for us with less packages, and > easier for users to switch pack and forth if they just need to update the > version pinning. > > > >> >> >> On 11/11/2016 10:33 PM, Oskar Berggren wrote: >> >>> NH 5.1 may also break API >>> >>> NH 5.2 may also break API >>> >> >> >> -- >> >> --- 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 >> <javascript:>. >> 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.
