On Sat, Jun 30, 2012 at 6:11 AM, Bruno Jouhier <[email protected]> wrote:
> If you publish your module with 0.6.x you tacitly engage yourself to > maintaining it and publishing a newer version shortly after 0.8 is > released, don't you? > Yes, IMHO. > The rule should be to publish with >= x.y.z unless you know that some > upcoming or already released change will break your code. > If you don't know what the future will be, you should bet on the fact that > things won't break. Does not mean that they won't ever break but you'll > take action when they do. Be optimistic!. > > So I don't see anything wrong with the "engines" feature itself. The > problem is that it has been misused. > There's still a bug in that if you've published an older version without the "engines" tag, then npm will backtrack through history to find that version and install that instead. It's this backtracking that is a bug IMHO. Matt. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
