[Feedhenry-raincatcher] How do we npm prerelease

[Michal Ogrodniczak]

Just to expand more on "adjust version just before publish and merge" with
an example:
- there is fh-wfm-user prereleased with 0.5.1.X
- I prerelease with 0.5.2.X
- my PRs and JIRAS had been reviewed/verified and I'm ready to release
- I run `npm info fh-wfm-user' and see that 0.5.1 is still in prerelease
- I change my version to 0.5.1 and release it.
- When person working on prerelease of 0.5.1 is ready to publish he/she can
either check for latest or just run publish and will get an error that the
version 0.5.1 is already published. He/she can then just bump to 0.5.2 and
publish that.

On Fri, Mar 24, 2017 at 10:03 AM, Michal Ogrodniczak <mogrodni at redhat.com>
wrote:

> Hi all,
>
> Quick question but IMO important enough to get an agreement of wider group.
> I need to publish new prerelease for fh-wfm-user last few versions on npm
> info:
>
>  '0.5.1-rc1': '2017-03-16T15:56:02.162Z',
>  '0.5.1-alpha.1': '2017-03-22T15:32:04.177Z',
>  '0.5.1-alpha.2': '2017-03-22T16:44:18.255Z',
>  '0.5.1-rc2': '2017-03-23T15:57:29.500Z',
>
> Do I just publish 0.5.1-alpha.X? I can see this being confusing to the
> person that published 0.5.1-alpha.X-1.
> I would prefer us to use 0.5.X+1-alpha.Y and keep it that way and adjust
> version just before publish and merge. At the moment it looks like there
> are two people working in independently on 0.5.1.
>
> Cheers
> Michal
> ​
> --
> Michal Ogrodniczak
> Associate Software Engineer, Red Hat Mobile
>
> mobile: *+353 83 334 5030 <//+353833345030> *
> slack: *@mogrodni*
> mail: *mogrodni at redhat.com <mogrodni at redhat.com>*
>
>
>


-- 
Michal Ogrodniczak
Associate Software Engineer, Red Hat Mobile

mobile: *+353 83 334 5030 <//+353833345030> *
slack: *@mogrodni*
mail: *mogrodni at redhat.com <mogrodni at redhat.com>*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/feedhenry-raincatcher/attachments/20170324/22c9356f/attachment.htm>