Github user stevengill commented on the pull request:
https://github.com/apache/cordova-coho/pull/49#issuecomment-58249073
I agree that having a private npm registry for testing in the long run is
the better option.
For now though, I disagree with not publishing RCs to npm. Why add a
barrier to testing RCs? If we publish no tool rcs to npm, we would expect
our users/testers to grab the tags for lib/cli/plugman/js, npm link them
and then they are able to test. I'm sure we have commiters & contributors
who wouldn't be able to do it properly now!
Being able to tell our users npm install -g cordova@rc to test has been a
great way to get them to try it before we do an official release. Even when
we setup a private npm repo to do this, it will still be one more step to
get people to test for us. Adding barriers!
Worst case, we find a issue with cordova-lib, we will have to fix the
version and do a minor bump and then republish as an RC. CLI & Plugman will
also need to be republished. This happens infrequently enough that I don't
think it is a big deal. Definitely when you consider how easy it is for
people to test.
On Tue, Oct 7, 2014 at 12:40 PM, Marcel Kinard <[email protected]>
wrote:
> I'd suggest that no RCs be pushed to the real npm registry. If there is a
> respin, then you can't reuse the version number. I think that is more
> problematic on tools than platforms. If we really want to test via npm
> install, I'd suggest a private registry.
>
> --
> Reply to this email directly or view it on GitHub
> <https://github.com/apache/cordova-coho/pull/49#issuecomment-58247365>.
>
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
