You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@usergrid.apache.org by Rod Simpson <ro...@rodsimpson.com> on 2014/12/12 19:00:44 UTC
Usergrid 2.0 on the horizon
Usergriders,
As many of you know, some of the Usergrid committers have been working on an updated version of Usergrid, currently called 2.0. This new release will bring a number of improvements, largely around performance and code maintainability.
The 2.0 code base has been used in production and is stable enough that if you are getting started with Usergrid now, you should seriously consider using 2.0.
One important note: the way 2.0 stores data is not compatible with 1.0. In other words, you can’t take a 2.0 .war file and just replace your existing 1.0 build. It just won’t work. We do not yet have a migration tool for converting 1.0 data to 2.0 format -- and even when we do migration may be operationally difficult. That's all the more reason to consider the 2.0 code base for your next Usergrid setup.
Rod
--
Rod Simpson
@rockerston
rodsimpson.com
Re: Usergrid 2.0 on the horizon
Posted by ja...@apps4u.com.au.
This sounds cool Im happy that 2.0 is coming along , Ive just spent the lsat few weeks working a new iOS SDK that is close to being done and released to the community. I would like to help with getting the SDK's into there own repos so we can take advantage of current library dependency systems for each language. Im happy to help out with this so we can get each sdk out with the correct commit message for the SDK's. Im going to be making the iOS SDK public over the next week or so Ive also built it like the new PHP SDK I did to be package managed with Cocoapods so having its own repo will help.
December 13 2014 11:11 AM, "Rod Simpson" <ro...@rodsimpson.com> wrote:
> The docs are in markdown format in the /docs directory. Just submit a PR in the normal way.
> Whoever acks the PR will trigger a build of the docs in readthedocs.org.
>
> Rod
>
> --
> Rod Simpson
> @rockerston
> rodsimpson.com
>
> On December 12, 2014 at 6:01:12 PM, John D. Ament (johndament@apache.org) wrote:
>
> Quick question. How do you contribute to the docs at this point? Since I specifically added a new
> config param, I think it's good to list it out.
>
> On Fri Dec 12 2014 at 7:43:49 PM <ro...@rodsimpson.com> wrote:
> Lets do it this next week! I will finish up the release notes and we will be ready to go.
>
> Rod Simpson
>
> On Fri, Dec 12, 2014 at 4:02 PM, Todd Nine <to...@gmail.com> wrote:
>
> Agreed, 2.0 is really coming along. We're making great progress in our
> refactor and performance. I think we should release another 1.0 release to
> get all the client SDKs out then roll them into the 2.0 branch as well.
> On Fri, Dec 12, 2014 at 1:58 PM Rod Simpson <ro...@rodsimpson.com> wrote:
>
>> John,
>>
>> That is great to hear. We have been thinking about doing a 1.0.1 release
>> next week. We have a new PHP SDK as well as a number of community
>> contributions.
>>
>> Dave Johnson has agreed to oversee the release again, which is awesome
>> (thanks dave!).
>>
>> Rod
>>
>> --
>> Rod Simpson
>> @rockerston
>> rodsimpson.com
>>
>> On December 12, 2014 at 11:47:44 AM, John D. Ament (johndament@apache.org)
>> wrote:
>>
>> On Fri Dec 12 2014 at 1:30:25 PM Dave Johnson <sn...@gmail.com> wrote:
>>
>>>
>>> > On Dec 12, 2014, at 1:00 PM, Rod Simpson <ro...@rodsimpson.com> wrote:
>>> >
>>> > Usergriders,
>>> >
>>> > As many of you know, some of the Usergrid committers have been working
>>> on an updated version of Usergrid, currently called 2.0. This new release
>>> will bring a number of improvements, largely around performance and code
>>> maintainability.
>>> >
>>> > The 2.0 code base has been used in production and is stable enough that
>>> if you are getting started with Usergrid now, you should seriously
>> consider
>>> using 2.0.
>>>
>>> +1 to that! We should talk about when to merge two-dot-o into master.
>>> Perhaps after a 1.0.1 bug fix release?
>>>
>>
>> Funny you say that. My QA's pretty much done for 1.0.1, the changes were
>> minimal that we had.
>>
>>>
>>> - Dave
>>>
>>>
>>> > One important note: the way 2.0 stores data is not compatible with 1.0.
>>> In other words, you can’t take a 2.0 .war file and just replace your
>>> existing 1.0 build. It just won’t work. We do not yet have a migration
>>> tool for converting 1.0 data to 2.0 format -- and even when we do
>> migration
>>> may be operationally difficult. That's all the more reason to consider
>> the
>>> 2.0 code base for your next Usergrid setup.
>>>
>>>
Re: Usergrid 2.0 on the horizon
Posted by Rod Simpson <ro...@rodsimpson.com>.
The docs are in markdown format in the /docs directory. Just submit a PR in the normal way. Whoever acks the PR will trigger a build of the docs in readthedocs.org.
Rod
--
Rod Simpson
@rockerston
rodsimpson.com
On December 12, 2014 at 6:01:12 PM, John D. Ament (johndament@apache.org) wrote:
Quick question. How do you contribute to the docs at this point? Since I specifically added a new config param, I think it's good to list it out.
On Fri Dec 12 2014 at 7:43:49 PM <ro...@rodsimpson.com> wrote:
Lets do it this next week! I will finish up the release notes and we will be ready to go.
Rod Simpson
On Fri, Dec 12, 2014 at 4:02 PM, Todd Nine <to...@gmail.com> wrote:
Agreed, 2.0 is really coming along. We're making great progress in our
refactor and performance. I think we should release another 1.0 release to
get all the client SDKs out then roll them into the 2.0 branch as well.
On Fri, Dec 12, 2014 at 1:58 PM Rod Simpson <ro...@rodsimpson.com> wrote:
> John,
>
> That is great to hear. We have been thinking about doing a 1.0.1 release
> next week. We have a new PHP SDK as well as a number of community
> contributions.
>
> Dave Johnson has agreed to oversee the release again, which is awesome
> (thanks dave!).
>
> Rod
>
>
> --
> Rod Simpson
> @rockerston
> rodsimpson.com
>
> On December 12, 2014 at 11:47:44 AM, John D. Ament (johndament@apache.org)
> wrote:
>
> On Fri Dec 12 2014 at 1:30:25 PM Dave Johnson <sn...@gmail.com> wrote:
>
> >
> > > On Dec 12, 2014, at 1:00 PM, Rod Simpson <ro...@rodsimpson.com> wrote:
> > >
> > > Usergriders,
> > >
> > > As many of you know, some of the Usergrid committers have been working
> > on an updated version of Usergrid, currently called 2.0. This new release
> > will bring a number of improvements, largely around performance and code
> > maintainability.
> > >
> > > The 2.0 code base has been used in production and is stable enough that
> > if you are getting started with Usergrid now, you should seriously
> consider
> > using 2.0.
> >
> > +1 to that! We should talk about when to merge two-dot-o into master.
> > Perhaps after a 1.0.1 bug fix release?
> >
>
> Funny you say that. My QA's pretty much done for 1.0.1, the changes were
> minimal that we had.
>
>
> >
> > - Dave
> >
> >
> > > One important note: the way 2.0 stores data is not compatible with 1.0.
> > In other words, you can’t take a 2.0 .war file and just replace your
> > existing 1.0 build. It just won’t work. We do not yet have a migration
> > tool for converting 1.0 data to 2.0 format -- and even when we do
> migration
> > may be operationally difficult. That's all the more reason to consider
> the
> > 2.0 code base for your next Usergrid setup.
> >
> >
>
Re: Usergrid 2.0 on the horizon
Posted by "John D. Ament" <jo...@apache.org>.
Quick question. How do you contribute to the docs at this point? Since I
specifically added a new config param, I think it's good to list it out.
On Fri Dec 12 2014 at 7:43:49 PM <ro...@rodsimpson.com> wrote:
> Lets do it this next week! I will finish up the release notes and we will
> be ready to go.
>
> Rod Simpson
>
>
> On Fri, Dec 12, 2014 at 4:02 PM, Todd Nine <to...@gmail.com> wrote:
>
>> Agreed, 2.0 is really coming along. We're making great progress in our
>> refactor and performance. I think we should release another 1.0 release
>> to
>> get all the client SDKs out then roll them into the 2.0 branch as well.
>> On Fri, Dec 12, 2014 at 1:58 PM Rod Simpson <ro...@rodsimpson.com> wrote:
>>
>> > John,
>> >
>> > That is great to hear. We have been thinking about doing a 1.0.1
>> release
>> > next week. We have a new PHP SDK as well as a number of community
>> > contributions.
>> >
>> > Dave Johnson has agreed to oversee the release again, which is awesome
>> > (thanks dave!).
>> >
>> > Rod
>> >
>> >
>> > --
>> > Rod Simpson
>> > @rockerston
>> > rodsimpson.com
>> >
>> > On December 12, 2014 at 11:47:44 AM, John D. Ament (
>> johndament@apache.org)
>> > wrote:
>> >
>> > On Fri Dec 12 2014 at 1:30:25 PM Dave Johnson <sn...@gmail.com>
>> wrote:
>> >
>> > >
>> > > > On Dec 12, 2014, at 1:00 PM, Rod Simpson <ro...@rodsimpson.com>
>> wrote:
>> > > >
>> > > > Usergriders,
>> > > >
>> > > > As many of you know, some of the Usergrid committers have been
>> working
>> > > on an updated version of Usergrid, currently called 2.0. This new
>> release
>> > > will bring a number of improvements, largely around performance and
>> code
>> > > maintainability.
>> > > >
>> > > > The 2.0 code base has been used in production and is stable enough
>> that
>> > > if you are getting started with Usergrid now, you should seriously
>> > consider
>> > > using 2.0.
>> > >
>> > > +1 to that! We should talk about when to merge two-dot-o into master.
>> > > Perhaps after a 1.0.1 bug fix release?
>> > >
>> >
>> > Funny you say that. My QA's pretty much done for 1.0.1, the changes
>> were
>> > minimal that we had.
>> >
>> >
>> > >
>> > > - Dave
>> > >
>> > >
>> > > > One important note: the way 2.0 stores data is not compatible with
>> 1.0.
>> > > In other words, you can’t take a 2.0 .war file and just replace your
>> > > existing 1.0 build. It just won’t work. We do not yet have a
>> migration
>> > > tool for converting 1.0 data to 2.0 format -- and even when we do
>> > migration
>> > > may be operationally difficult. That's all the more reason to
>> consider
>> > the
>> > > 2.0 code base for your next Usergrid setup.
>> > >
>> > >
>> >
>>
>
>
Re: Usergrid 2.0 on the horizon
Posted by ro...@rodsimpson.com.
Lets do it this next week! I will finish up the release notes and we will be ready to go.
Rod Simpson
On Fri, Dec 12, 2014 at 4:02 PM, Todd Nine <to...@gmail.com> wrote:
> Agreed, 2.0 is really coming along. We're making great progress in our
> refactor and performance. I think we should release another 1.0 release to
> get all the client SDKs out then roll them into the 2.0 branch as well.
> On Fri, Dec 12, 2014 at 1:58 PM Rod Simpson <ro...@rodsimpson.com> wrote:
>> John,
>>
>> That is great to hear. We have been thinking about doing a 1.0.1 release
>> next week. We have a new PHP SDK as well as a number of community
>> contributions.
>>
>> Dave Johnson has agreed to oversee the release again, which is awesome
>> (thanks dave!).
>>
>> Rod
>>
>>
>> --
>> Rod Simpson
>> @rockerston
>> rodsimpson.com
>>
>> On December 12, 2014 at 11:47:44 AM, John D. Ament (johndament@apache.org)
>> wrote:
>>
>> On Fri Dec 12 2014 at 1:30:25 PM Dave Johnson <sn...@gmail.com> wrote:
>>
>> >
>> > > On Dec 12, 2014, at 1:00 PM, Rod Simpson <ro...@rodsimpson.com> wrote:
>> > >
>> > > Usergriders,
>> > >
>> > > As many of you know, some of the Usergrid committers have been working
>> > on an updated version of Usergrid, currently called 2.0. This new release
>> > will bring a number of improvements, largely around performance and code
>> > maintainability.
>> > >
>> > > The 2.0 code base has been used in production and is stable enough that
>> > if you are getting started with Usergrid now, you should seriously
>> consider
>> > using 2.0.
>> >
>> > +1 to that! We should talk about when to merge two-dot-o into master.
>> > Perhaps after a 1.0.1 bug fix release?
>> >
>>
>> Funny you say that. My QA's pretty much done for 1.0.1, the changes were
>> minimal that we had.
>>
>>
>> >
>> > - Dave
>> >
>> >
>> > > One important note: the way 2.0 stores data is not compatible with 1.0.
>> > In other words, you can’t take a 2.0 .war file and just replace your
>> > existing 1.0 build. It just won’t work. We do not yet have a migration
>> > tool for converting 1.0 data to 2.0 format -- and even when we do
>> migration
>> > may be operationally difficult. That's all the more reason to consider
>> the
>> > 2.0 code base for your next Usergrid setup.
>> >
>> >
>>
Re: Usergrid 2.0 on the horizon
Posted by Todd Nine <to...@gmail.com>.
Agreed, 2.0 is really coming along. We're making great progress in our
refactor and performance. I think we should release another 1.0 release to
get all the client SDKs out then roll them into the 2.0 branch as well.
On Fri, Dec 12, 2014 at 1:58 PM Rod Simpson <ro...@rodsimpson.com> wrote:
> John,
>
> That is great to hear. We have been thinking about doing a 1.0.1 release
> next week. We have a new PHP SDK as well as a number of community
> contributions.
>
> Dave Johnson has agreed to oversee the release again, which is awesome
> (thanks dave!).
>
> Rod
>
>
> --
> Rod Simpson
> @rockerston
> rodsimpson.com
>
> On December 12, 2014 at 11:47:44 AM, John D. Ament (johndament@apache.org)
> wrote:
>
> On Fri Dec 12 2014 at 1:30:25 PM Dave Johnson <sn...@gmail.com> wrote:
>
> >
> > > On Dec 12, 2014, at 1:00 PM, Rod Simpson <ro...@rodsimpson.com> wrote:
> > >
> > > Usergriders,
> > >
> > > As many of you know, some of the Usergrid committers have been working
> > on an updated version of Usergrid, currently called 2.0. This new release
> > will bring a number of improvements, largely around performance and code
> > maintainability.
> > >
> > > The 2.0 code base has been used in production and is stable enough that
> > if you are getting started with Usergrid now, you should seriously
> consider
> > using 2.0.
> >
> > +1 to that! We should talk about when to merge two-dot-o into master.
> > Perhaps after a 1.0.1 bug fix release?
> >
>
> Funny you say that. My QA's pretty much done for 1.0.1, the changes were
> minimal that we had.
>
>
> >
> > - Dave
> >
> >
> > > One important note: the way 2.0 stores data is not compatible with 1.0.
> > In other words, you can’t take a 2.0 .war file and just replace your
> > existing 1.0 build. It just won’t work. We do not yet have a migration
> > tool for converting 1.0 data to 2.0 format -- and even when we do
> migration
> > may be operationally difficult. That's all the more reason to consider
> the
> > 2.0 code base for your next Usergrid setup.
> >
> >
>
Re: Usergrid 2.0 on the horizon
Posted by Rod Simpson <ro...@rodsimpson.com>.
John,
That is great to hear. We have been thinking about doing a 1.0.1 release next week. We have a new PHP SDK as well as a number of community contributions.
Dave Johnson has agreed to oversee the release again, which is awesome (thanks dave!).
Rod
--
Rod Simpson
@rockerston
rodsimpson.com
On December 12, 2014 at 11:47:44 AM, John D. Ament (johndament@apache.org) wrote:
On Fri Dec 12 2014 at 1:30:25 PM Dave Johnson <sn...@gmail.com> wrote:
>
> > On Dec 12, 2014, at 1:00 PM, Rod Simpson <ro...@rodsimpson.com> wrote:
> >
> > Usergriders,
> >
> > As many of you know, some of the Usergrid committers have been working
> on an updated version of Usergrid, currently called 2.0. This new release
> will bring a number of improvements, largely around performance and code
> maintainability.
> >
> > The 2.0 code base has been used in production and is stable enough that
> if you are getting started with Usergrid now, you should seriously consider
> using 2.0.
>
> +1 to that! We should talk about when to merge two-dot-o into master.
> Perhaps after a 1.0.1 bug fix release?
>
Funny you say that. My QA's pretty much done for 1.0.1, the changes were
minimal that we had.
>
> - Dave
>
>
> > One important note: the way 2.0 stores data is not compatible with 1.0.
> In other words, you can’t take a 2.0 .war file and just replace your
> existing 1.0 build. It just won’t work. We do not yet have a migration
> tool for converting 1.0 data to 2.0 format -- and even when we do migration
> may be operationally difficult. That's all the more reason to consider the
> 2.0 code base for your next Usergrid setup.
>
>
Re: Usergrid 2.0 on the horizon
Posted by "John D. Ament" <jo...@apache.org>.
On Fri Dec 12 2014 at 1:30:25 PM Dave Johnson <sn...@gmail.com> wrote:
>
> > On Dec 12, 2014, at 1:00 PM, Rod Simpson <ro...@rodsimpson.com> wrote:
> >
> > Usergriders,
> >
> > As many of you know, some of the Usergrid committers have been working
> on an updated version of Usergrid, currently called 2.0. This new release
> will bring a number of improvements, largely around performance and code
> maintainability.
> >
> > The 2.0 code base has been used in production and is stable enough that
> if you are getting started with Usergrid now, you should seriously consider
> using 2.0.
>
> +1 to that! We should talk about when to merge two-dot-o into master.
> Perhaps after a 1.0.1 bug fix release?
>
Funny you say that. My QA's pretty much done for 1.0.1, the changes were
minimal that we had.
>
> - Dave
>
>
> > One important note: the way 2.0 stores data is not compatible with 1.0.
> In other words, you can’t take a 2.0 .war file and just replace your
> existing 1.0 build. It just won’t work. We do not yet have a migration
> tool for converting 1.0 data to 2.0 format -- and even when we do migration
> may be operationally difficult. That's all the more reason to consider the
> 2.0 code base for your next Usergrid setup.
>
>
Re: Usergrid 2.0 on the horizon
Posted by Dave Johnson <sn...@gmail.com>.
> On Dec 12, 2014, at 1:00 PM, Rod Simpson <ro...@rodsimpson.com> wrote:
>
> Usergriders,
>
> As many of you know, some of the Usergrid committers have been working on an updated version of Usergrid, currently called 2.0. This new release will bring a number of improvements, largely around performance and code maintainability.
>
> The 2.0 code base has been used in production and is stable enough that if you are getting started with Usergrid now, you should seriously consider using 2.0.
+1 to that! We should talk about when to merge two-dot-o into master. Perhaps after a 1.0.1 bug fix release?
- Dave
> One important note: the way 2.0 stores data is not compatible with 1.0. In other words, you can’t take a 2.0 .war file and just replace your existing 1.0 build. It just won’t work. We do not yet have a migration tool for converting 1.0 data to 2.0 format -- and even when we do migration may be operationally difficult. That's all the more reason to consider the 2.0 code base for your next Usergrid setup.