On Wed, Apr 9, 2014 at 7:45 AM, Dave <[email protected]> wrote: > After my Usergrid talk at ApacheCon a couple of us Usergridlers started > talking about how to get a first release out. Here's a summary of what we > talked about. > > The discussion started with the question: should we release what we have > now in master as a "1.0" release or should we wait for the "two-dot-o" > branch to be merged into master. After some discussion we arrived at the > conclusion that the "two-dot-o" branch is not really Usergrid 2.0. Instead > it is really just a new feature -- a new "Core Persistence" implementation > of the existing Entity Manager interface, one that can be turned on and off > via configuration. > > We should rename the two-dot-o branch to something that reflects the fact > that is is essentially a new feature, perhaps we should call it > "core-persistence" or something like that. > > More importantly, we should not hold-up our first Apache release by waiting > for the new "Core Persistence" feature to be complete. And, we definitely > should not force amazing contributions like Sungju's Jersey 2 work to be > merged into the Core Persistence branch. Sungju's work should go into > master and we should work to get a first release done from the master > branch as soon as possible, regardless of the work on the new "Core > Persistence" engine. > > Thoughts? >
I agree with getting a release out soon. Cleaning up the code (in terms of licenses) and getting the release packaged and voted will take a some time and effort, which will probably delay work on the core persistence feature. But once that first Apache Usergrid release is out, some things can get started in parallel with any 2.0 work. For example, ensuring deployment in maven central, platform-native packages for all SDK's, marketing etc. Lieven > - Dave
