[jira] [Closed] (COUCHDB-2736) Lager versioning

["Robert Kowalski (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/COUCHDB-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Kowalski closed COUCHDB-2736.
------------------------------------
    Resolution: Fixed

> Lager versioning
> ----------------
>
>                 Key: COUCHDB-2736
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2736
>             Project: CouchDB
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Database Core
>            Reporter: Robert Kowalski
>            Priority: Blocker
>
> Hi
> I noticed that couchdb-couch-log points to the master of couchdb-lager:
> https://github.com/apache/couchdb-couch-log/blob/master/rebar.config#L2
> I also noticed that we started to patch the original source code on the master branch.
>  - What is the way to go for pinning the version for a CouchDB release? I saw that the tags on our repo are the original tags of the lager project and our master is in a state after the 2.0.2 release of lager with a few commits from them and a few from us. Should we point to a commit SHA? Can we use tags?
>  - What is the way to go to update lager? The 2.x series is now at 2.1.1 and version 3 is coming soon. Just rebase against their lastest 2.x tag and open a PR/push to our master? 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)