Yes, we will tag the dependencies and update rebar.config to point to them.
That's how we do this at Cloudant. Rebar config is only pointing to master
branches while we're getting all the things working.
Sent from my iPhone
> On 22 Jul 2014, at 07:50, Samuel Williams
> wrote:
>
> Is there
Is there some way to maintain versions e.g. like how Gemfile does it?
On 13/07/14 23:47, Alexander Shorin wrote:
Hi devs,
The question I'd like to raise is about version policy for the
components which were extracted from main big couchdb.git repo into
own separate ones. How to track their vers
On 13 Jul 2014, at 13:47 , Alexander Shorin wrote:
> Hi devs,
>
> The question I'd like to raise is about version policy for the
> components which were extracted from main big couchdb.git repo into
> own separate ones. How to track their version now?
>
> For instance, we have jquery-couch.git
The code components (fabric, mem3, rexi, etc) have their own version numbers
(following semver). Because of the way this was merged, many historical tags
(used by Cloudant during our regular release cycle) are missing as they would
pull in the pre-ip-cleared versions of the modules.
I don’t se
Hi devs,
The question I'd like to raise is about version policy for the
components which were extracted from main big couchdb.git repo into
own separate ones. How to track their version now?
For instance, we have jquery-couch.git now - jquery client for CouchDB
which was actively used by Futon an
