Hi, To keep Joda-Time stable, I only add bug fixes to minor versions. Thus any new 1.x version would need to be 1.7.
The 2.x TRUNK in svn is entirely stable and awaiting release. It is effectively in QA at the moment. I am waiting for Joda-Convert to be available so I can add some annotations to Joda-Time before release. Therefore, if you build a 2.x you will find it completely unaltered from a code perspective when 2.0 is actually released. Note that the 2.x name simply refers to the fact that some deprecated methods were removed, and generics added. The 2.x jar file should be binary compatible and 99.9% source compatible with your existing code (see the release notes in svn). Hope that helps, Stephen On 24 August 2010 08:55, Ansgar Konermann <ansgar.konerm...@googlemail.com> wrote: > Hi Stephen, > > sorry to bother you again... :-) > > We're using Joda Time 1.6 in production code and we would really like to > use the custom MillisProvider feature. Since the current trunk version > obviously already resembles the 2.x development line, we are wondering > if we can switch our production code to the trunk version without > problems -- probably we cannot, or can we? We feel there might be > serious risks, since 2.0 its a new major version. > > As a temporary solution, I'd be willing to backport the custom millis > provider to the 1.6 development branch and maintain a specific version > for my employer. Of course I'd preferr a solution which minimizes effort > on all sides. Some questions regarding this: > > - is it correct that development of the 1.6 line takes place in the > v1_6_000_BRANCH branch, located at > https://joda-time.svn.sourceforge.net/svnroot/joda-time/branches/v1_6_000_BRANCH/ > > - if I provide you with a patch against 1.6.1, which backports custom > millis provider from 2.0 to 1.6.1, would you basically be willing to > apply this patch to the 1.6 development line? This could save us some > effort for future updates in the 1.6.x development line: we wouldn't > have to re-apply the patch and can simply use a version from maven > cental instead of maintaining our own version of Joda Time containing > the backport. > > Thanks for your patience... > > Kind regards > > Ansgar > > On 24.06.2010 18:37, Stephen Colebourne wrote: >> I have no fixed time-line for a release, so I'd recommend building >> your own right now. >> Stephen >> >> On 24 June 2010 17:15, Ansgar Konermann<ansgar.konerm...@googlemail.com> >> wrote: >> >>> Hi Stephen, >>> >>> great! Thanks. >>> >>> Do you plan on making a release any time soon, or is it worth the effort >>> to build the source code on my own and deploy it into our company's >>> maven repo? >>> >>> Best regards >>> >>> Ansgar >>> >>> On 24.06.2010 12:21, Stephen Colebourne wrote: >>> >>>> Please check the latest svn code. It should handle your requirement. >>>> Stephen >>>> > > > ------------------------------------------------------------------------------ > Sell apps to millions through the Intel(R) Atom(Tm) Developer Program > Be part of this innovative community and reach millions of netbook users > worldwide. Take advantage of special opportunities to increase revenue and > speed time-to-market. Join now, and jumpstart your future. > http://p.sf.net/sfu/intel-atom-d2d > _______________________________________________ > Joda-interest mailing list > Joda-interest@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/joda-interest > ------------------------------------------------------------------------------ Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d _______________________________________________ Joda-interest mailing list Joda-interest@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/joda-interest
