new development strategy.

guillaumearm commented 8 years ago

due to #37, we need to be careful about staging.

react-redux-polyglot use redux-polyglot as main dependency, so i think we need to work on a devbranch and follow this 3 principles :

this branch must be as clean as master, so npm run prepublish must be ok.
all master merges should be tagged by a new version. (on the master branch only)
all change must be validated by react-redux-polyglot unit testing before merge on master ( maybe find for an automation )

todo before close this issue :

create a dev branch [DONE]
explain this principles in redux-polyglot CONTRIBUTING.md [DONE]
pre-release react-redux-polyglot 0.0.1
write documentation for this when it's done.

note: please see react-redux-polyglot/issues/3

guillaumearm commented 8 years ago

I think this issue must be a priority. @JalilArfaoui ? @jvincent42 ?

guillaumearm commented 8 years ago

dev branch created.

guillaumearm commented 8 years ago

PR here in #55

JalilArfaoui commented 8 years ago

As we discussed @guillaumearm we should merge both redux-polyglot and react-redux-polyglot NPM modules in the same repository to ensure full synchronicity and simpler tests.

JalilArfaoui commented 7 years ago

Can we close this one ?

Tiqa / redux-polyglot

new development strategy. #52