Thanks! Maybe this should go into METADATA.jl Readme, or into the docs?
On Thu, 2015-10-01 at 08:28, Jiahao Chen <cjia...@gmail.com> wrote: > Hello package developers, > > Please note our new policies for accepting entries into METADATA.jl, which > take effect immediately: > > 1. New packages submitted for registration must have at least one tagged > version. > 2. The lowest package version that will be accepted is v0.0.1. *v0.0.0 > is no longer permitted*. > 3. All new tagged versions of packages must have a requires file, which > must at a minimum contain a single line like > julia 0.3 > specifying a minimum version of Julia the package is expected to run on. > > A common mistake is to have an entry of the form > julia 0.3- > with the intention of specifying "version 0.3 and up". On the contrary, > this line means "at least a 0.3 pre-release julia". > 4. New package version tags must support at least Julia version 0.3. > *0.3- (0.3 pre-releases) is no longer allowed. *Exceptions may be granted > for julia 0.2 if package authors are willing to vouch that they still > test that their packages work on 0.2. > 5. We strongly encourage everyone to *update METADATA.jl through pull > requests*, which can be generated for you automatically when using > Pkg.publish(). GitHub's pull requests allow us to run basic checks on > the metadata entries. All developers (especially experienced developers!) > are *strongly discouraged from editing METADATA.jl directly* unless > absolutely necessary. > > These new policies have been the result of many months of discussion to > improve the quality of registered packages and the overall user experience > with Julia packages. > > As a friendly reminder, do consult the package development section of the > manual > <http://julia.readthedocs.org/en/latest/manual/packages/#package-development> > for guidelines for getting your package accepted into METADATA.jl.
