Rename lightblue-mongo repository

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Rename lightblue-mongo repository

lcestari
I thought it could be nice as the MongoDB next release will be 3.0 ( http://www.mongodb.com/faq#MongoDB_3.0 ) , and that can mean that the API can change and it would be nice if we could maintain both interfaces independtly (e.g. lightblue-mongo2 and lightblue-mongo3, so if 2.6.x still have new updates we could maintain it independtly the changes of the lightblue-mongo3 repository )
Reply | Threaded
Open this post in threaded view
|

Re: Rename lightblue-mongo repository

jewzaam
Administrator
I'd prefer to support both, but there may be some features we adopt eventually that are version specific.  Having two repositories is painful when changes have to happen in both.  Or you end up with a third repository with the generic/common logic.  I recommend for now we update unit tests to run against latest 3.x in addition to the 2.x version.  If there are issues we can see where we need to go, but for now I expect we can keep support for both in one repo.

On Mon Jan 26 2015 at 9:25:14 AM lcestari [via lightblue-dev] <[hidden email]> wrote:
I thought it could be nice as the MongoDB next release will be 3.0 ( http://www.mongodb.com/faq#MongoDB_3.0 ) , and that can mean that the API can change and it would be nice if we could maintain both interfaces independtly (e.g. lightblue-mongo2 and lightblue-mongo3, so if 2.6.x still have new updates we could maintain it independtly the changes of the lightblue-mongo3 repository )


If you reply to this email, your message will be added to the discussion below:
http://dev.forum.lightblue.io/Rename-lightblue-mongo-repository-tp326.html
To start a new topic under lightblue-dev, email [hidden email]
To unsubscribe from lightblue-dev, click here.
NAML