One related thought: it would be nice if versions which target a new version of Julia got a larger version bump, to make it easier to backport fixes to previous versions of julia. Something like:
0.2.1 # targets Julia v0.2 0.2.2 0.2.3 # last "real" version which targets v0.2 0.2.4 # simply add "julia -0.2" to REQUIRES 0.3.0 # first version which targets v0.3; use "julia 0.3-" in REQUIRES 0.3.1 0.3.2 # bug fix 0.2.5 # port of bug fix back to 0.2 series There's no reason, of course, that the 0.2.x has to work with Julia v0.2, and 0.3.x has to work with Julia v0.3--It could just as easily be 0.1.x and 0.2.x, or 1.0.x and 2.0.x. Thoughts? Kevin On Sat, Feb 1, 2014 at 3:20 PM, John Myles White <[email protected]>wrote: > I went into METADATA and updated the requires files, then submitted a new > commit. I actually did this for one release of NumericExtensions which > would reliably crash when loading on the 0.2 release. > > — John > > On Feb 1, 2014, at 3:19 PM, Dahua Lin <[email protected]> wrote: > > John, > > Could you elaborate a little bit about how you did this? > > Recent changes in NumericExtensions that rely on some new features have > caused headaches to users who use 0.2 release. I would like to do something > to fix it sometime next week. > > — Dahua > > On February 1, 2014 at 5:08:34 PM, John Myles White ( > [email protected] <//[email protected]>) wrote: > > I think so. I’ve done it recently and fixed some errors by doing it. > > — John > > On Feb 1, 2014, at 3:07 PM, Dahua Lin <[email protected]> wrote: > > Is it possible to update the requirement of previously tagged versions? > > On Friday, January 31, 2014 5:13:21 PM UTC-6, Ivar Nesje wrote: >> >> It seems like you are using the 0.2.0 version of Julia, and some package >> authors have not correctly marked new versions of their package to require >> 0.3.0-prerelease when they decided to use features that has been introduced >> after the release of 0.2.0. The consequence is that Pkg.add and Pkg.update >> installs versions of some packages that is incompatible with your version >> of Julia. I think this is a very unfortunate situation for new people >> evaluating Julia, and the easiest way to solve this us to compile from >> source or download a nightly release. > > >
