Hi, I sorry but what npm recommends is nothing to do with ASF release policy.
> On the other hand, if a version is deprecated, it will give a warning to tell > the developers to update, which, in our case, is somewhat strange since we > don't have a newer correct version. Yes that is unfortunate but you need to follow ASF release policy. If you want an exception to this then you need to ask the ASF board. > So, the safest and best-for-all solution seems to be, releasing a correct > version with the permission of PPMC ASAP, which we are working on > currently. And after that, mark the 4.2.0-rc1 to be deprecated. I don't think that is the best course of action but discuss with your mentors and see what they say. > I think this way also benefits Apache's branding in saving a large number > of developers' confusion and complaints. > Could @Justin please help judge if this works with Apache? By putting out unapproved released you put the legal protections that the ASF have in place for your project and the ASF itself at risk. It's probably not a large risk but it's there all the same. Please read [1] so you understand why the ASF has a release policy and why we don't allow unapproved releases. Thanks, Justin 1. http://www.apache.org/legal/release-policy.html#why --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
