CBL iOS Stable Builds

[Todd Orler]

I've been away from this list, and the product I was working on which used CBL, for a few months.  Long story.  Our last CBL integration was from commit 8783a9680627088a57a72a9cb4e673f389741b09 (December 13, 2013).

Now that I'm back, I need to update our product with an update of CBL.  I see there is still a “stable” branch, and there are also tags for various checkpoints, such as “1.0-beta3”.  I’d like some guidance on which to choose.  We’re looking for a very stable branch for now.  I’d normally choose the “stable” branch, but I see that “master” is being merged into the “stable” branch fairly regularly (twice in the last 4 days).  Maybe I’m looking at it backwards.  Knowing where “unstable” changes are being committed would be helpful to know what we should avoid for now.

Thanks,
-Todd

[Traun Leyden]

We're in the midst of creating a 1.0 GA release, so if you want "very stable", you should hold out until that release happens and it's been tagged with a release tag.

I'm in the process of trying to switch the team over to the following branching strategy:

http://tleyden.github.io/blog/2014/04/09/a-successful-git-branching-model-with-enterprise-support/

If you have any feedback or suggestions from a "library consumer" perspective, I'd love to hear them.

--
You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mobile-couchba...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/9750b354-2949-4d85-b8be-12f41930bc2a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Todd Orler]

Thanks, Traun.  Can you give some indication of how long I might want to hold out for the 1.0 release?  :)  Are we talking about days, weeks, or months?

The branching strategy at that link seems sound.  I take your wording to mean that you're not yet switched to this strategy?  That strategy implies that you don't create a "stable" branch until you've actually released something (1.0), right?  But there's currently a "stable" CBL branch, so what is the basis for this branch?  If risky changes in the "master" branch are being merged into the "stable" branch regularly, it seems I may want to avoid the "stable" branch, despite its name.

If the 1.0 release is days away, I can wait.  If it's months away, I guess I'd like more info about where to pick up a fairly stable branch.

Thanks,
-Todd

[Jens Alfke]

On Apr 15, 2014, at 4:18 PM, Todd Orler <tod...@hammersmith.mygbiz.com> wrote:

Now that I'm back, I need to update our product with an update of CBL.  I see there is still a “stable” branch, and there are also tags for various checkpoints, such as “1.0-beta3”.  I’d like some guidance on which to choose.  We’re looking for a very stable branch for now.  

I would download the beta 3.1 release. If you want to build it yourself, you can just check out the tag, which is … um, we forgot to tag it. Let me fix that. The tag is 1.0-beta3.1; here’s the fancy Github release page for it.

I’d normally choose the “stable” branch, but I see that “master” is being merged into the “stable” branch fairly regularly (twice in the last 4 days).

Ordinarily the stable branch should be good to use, but we had an issue yesterday where someone checked in some build-breaking changes that had to be reverted. :/ The branch should be fine now. It’s newer than beta 3.1, basically a candidate for the 1.0 release.

As Traun says, we’re going to start using a new branching strategy. But ‘master’ will continue to be the bleeding-edge stuff, and ‘stable’ will continue to lag a bit behind but be more reliable.

—Jens

[Jens Alfke]

On Apr 15, 2014, at 4:57 PM, Todd Orler <tod...@hammersmith.mygbiz.com> wrote:

Thanks, Traun.  Can you give some indication of how long I might want to hold out for the 1.0 release?  :)  Are we talking about days, weeks, or months?

Weeks. But I believe Couchbase Lite/iOS is pretty close to finished already. There are no open bugs scheduled for 1.0, and I don’t anticipate adding any more changes for that release unless some show-stopper is discovered.

—Jens