Publish 0.5.x branch to iojs or beta tag

[mleavitt]

In the now infamous issue #243

On June 24, 2015 @DmitrySoshnikov wrote:

As of #374, Jest should work on latest io.js. It's currently in a separate branch, https://github.com/facebook/jest/tree/0.5.x, and can also be installed via npm facebook/jest#0.5.x. Later on we'll consider moving to io.js, and making this branch as master (and when Node 2.0 will fully be merged with io.js, it automatically work with node). If you use io.js, we'll be glad to get the feedback on the experience with 0.5.x.

On June 24, 2015 @zertosh wrote:

@DmitrySoshnikov Thanks! Can you publish it to npm under a beta/iojs/whatever tag?

There was no response to this request, so I'm opening it as a new issue to see if we can get a response outside of the noise of that other thread. Thanks!

[DmitrySoshnikov]

@mleavitt, yeah, sorry, I didn't have chance. The plan is now to make 0.5.x as master, and maintain legacy 0.4.x separately. This should happen on August 1st, 2015 (we started to issue deprecation notice). From this perspective, not sure we need to publish additional version on npm yet (and legacy version can be installed from the Github's branch). If this is still very on demand, we can probably publish the new beta tag (though later it'll become obsolete and may bring confusions).

[zertosh]

When I made the request for publishing 0.5.x under a beta tag, the August 1st notice wasn't up (or at least I didn't see it). Since that's only a few weeks away and a tagged release would def cause confusion, I'm totally ok with waiting. So no worries from my side @DmitrySoshnikov.

[mleavitt]

@DmitrySoshnikov I overlooked the deprecation notice. Thanks for the quick response.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.