Tag a New Release

[haneefmubarak]

I know that the project is dormant and development has stagnated, but it'd be awesome if y'all could tag a new release at whatever commit you feel is reasonable. I'd like to include this as a dependency in a project, but I'd hate to have to refer to either HEAD or a specific commit hash directly.

Thanks!

[hisundar]

Sure, we will try to tag the releases but if it helps perhaps you can refer to a branch instead?
The branches in order are watson-> spock-> vulcan
We backport fixes too so picking say vulcan should get you the future fixes too.

[0joshuaolson1]

This is dormant/stagnated?

https://developer.couchbase.com/open-source-projects lists this and neither https://github.com/couchbase/moss nor https://github.com/couchbase/nitro. What's the recommended embedded key-value store going forward, if I may ask?

[hisundar]

The term used by Couchbase for forestdb is "maintenance mode".
There are certainly bug fixes going in but those are into specific release branches like vulcan as listed above.
Both moss and nitro are currently in use under couchbase server products of full text search and global secondary indexes respectively. Each product has evolved a highly specialized embedded key-value store that serves its specific needs so if you are asking for a single solution that can serve all use cases, right now there isn't one.

[pjc158]

It is a pity that Couchbase has abandoned Forestdb as a stand-alone product as it is very good. That is the problem with open source projects even when a major company is behind it and that includes the likes of Google. Get Outlook for iOS<https://aka.ms/o0ukef>

…

________________________________ From: Sundar Sridharan <[email protected]> Sent: Tuesday, April 10, 2018 9:52:53 PM To: couchbase/forestdb Cc: Subscribed Subject: Re: [couchbase/forestdb] Tag a New Release (#18) The term used by Couchbase for forestdb is "maintenance mode". There are certainly bug fixes going in but those are into specific release branches like vulcan as listed above. Both moss and nitro are currently in use under couchbase server products of full text search and global secondary indexes respectively. Each product has evolved a highly specialized embedded key-value store that serves its specific needs so if you are asking for a single solution that can serve all use cases, right now there isn't one. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#18 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AGgFtIEqEdS-SzCovY8bxj3o11Ti9Rfoks5tnRulgaJpZM4SbS_j>.

[0joshuaolson1]

Each product has evolved a highly specialized embedded key-value store that serves its specific needs so if you are asking for a single solution that can serve all use cases

Oh, I didn't mean to imply that - neither of them are clear about the use cases.

BTW, this project's readme doesn't mention 'maintenance mode' at this time.

[hisundar]

Well the maintenance mode is only with respect to Couchbase. That does not mean open source contributions are not welcome. There are users of forestdb outside of Couchbase as well.