+1 with your sentiments Dave.  I don't feel we should be merging
contributions into a branch other than master if they're stable.

On Wed, Apr 9, 2014 at 12:33 PM, Rod Simpson <[email protected]> wrote:
> Agreed.  Calling it 2.0 is misleading.  It really isn't 2.0.  It is just a 
> re-write of a few parts of the system and the rest of the system will remain 
> unchanged.
>
> We should definitely push for a release as soon as possible, but I don't 
> think it will delay Core Persistence.
>
> We need to add license headers to all SDKs, the Portal, and to UGC. I think 
> the stack is finished.  Ryan Bridges has agreed to add the headers to the JS 
> SDK and Node.js module.  Shawn Feldman will tackle the Portal.  I will make 
> tickets for the rest now, and we will see who can pick them up.
>
> Rod
> --
> Rod Simpson
> @rockerston
> rodsimpson.com
>
> On April 9, 2014 at 8:43:28 AM, Lieven Govaerts ([email protected]) wrote:
>
> 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

Reply via email to