[aerogear-dev] Breaking changes in between UPS 1.1.0.Beta3 and 1.1.0.Final

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

[aerogear-dev] Breaking changes in between UPS 1.1.0.Beta3 and 1.1.0.Final

Karel Piwko
Hello All,

I'm really unhappy with number of breaking changes that has appeared in the latest staged 1.1.0.Final - mostly these changes were related to massive DB schema updates. I'd expect such changes to happen in Alpha phase and not in between Beta3 and Final.

I understand that a lot of these changes have been driven by late inclusion of migrator to 1.1 branch. That said, what is the plan with 1.1.0.Final? Are you guys going to remove the changes or at least make sure they do not impact users running Beta3? I've seen it has been de-staged and there have been a few commits reverting DB changes back. Is there any estimate when 1.1.0.Final will be restaged?

QE plan is to make sure that migration from 1.0.3 is smooth, however we also want migration from Beta3 to be smooth.

Many thanks,

Karel

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev
Reply | Threaded
Open this post in threaded view
|

Re: [aerogear-dev] Breaking changes in between UPS 1.1.0.Beta3 and 1.1.0.Final

Matthias Wessendorf
Hi Karel,

On Mon, Aug 17, 2015 at 9:08 AM, Karel Piwko <[hidden email]> wrote:
Hello All,

I'm really unhappy with number of breaking changes that has appeared in the latest staged 1.1.0.Final - mostly these changes were related to massive DB schema updates. I'd expect such changes to happen in Alpha phase and not in between Beta3 and Final.

I fully understand your frustration. I think the source of this issue is that the migration work took much longer than expected, getting it ported to master branch (was introduced on 1.0.3).
 

I understand that a lot of these changes have been driven by late inclusion of migrator to 1.1 branch. That said, what is the plan with 1.1.0.Final? Are you guys going to remove the changes or at least make sure they do not impact users running Beta3?

I think the biggest concern is clearly supporting users, upgrading from 1.0.3
 
I've seen it has been de-staged and there have been a few commits reverting DB changes back. Is there any estimate when 1.1.0.Final will be restaged?

Yeah, there will be a re-staging coming soon. Question, due to the huge changes, what about doing a Beta.4 and following up w a .Final in week or two?
To make sure things are stable, before we stage a 1.1.0.Final - makes sense ? 
 

QE plan is to make sure that migration from 1.0.3 is smooth, however we also want migration from Beta3 to be smooth.

I am actually over asked about the migration from beta.3, not sure that's really a huge concern here
 

Many thanks,

Karel

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev
Reply | Threaded
Open this post in threaded view
|

Re: [aerogear-dev] Breaking changes in between UPS 1.1.0.Beta3 and 1.1.0.Final

Karel Piwko

Thanks Matthias,

Comments inline.

Karel

Dne 17. 8. 2015 11:54 napsal uživatel "Matthias Wessendorf" <[hidden email]>:
>
> Hi Karel,
>
> On Mon, Aug 17, 2015 at 9:08 AM, Karel Piwko <[hidden email]> wrote:
>>
>> Hello All,
>>
>> I'm really unhappy with number of breaking changes that has appeared in the latest staged 1.1.0.Final - mostly these changes were related to massive DB schema updates. I'd expect such changes to happen in Alpha phase and not in between Beta3 and Final.
>
>
> I fully understand your frustration. I think the source of this issue is that the migration work took much longer than expected, getting it ported to master branch (was introduced on 1.0.3).
>  
>>
>>
>> I understand that a lot of these changes have been driven by late inclusion of migrator to 1.1 branch. That said, what is the plan with 1.1.0.Final? Are you guys going to remove the changes or at least make sure they do not impact users running Beta3?
>
>
> I think the biggest concern is clearly supporting users, upgrading from 1.0.3
>  
>>
>> I've seen it has been de-staged and there have been a few commits reverting DB changes back. Is there any estimate when 1.1.0.Final will be restaged?
>
>
> Yeah, there will be a re-staging coming soon. Question, due to the huge changes, what about doing a Beta.4 and following up w a .Final in week or two?
> To make sure things are stable, before we stage a 1.1.0.Final - makes sense ? 

Sounds good to me!

>  
>>
>>
>> QE plan is to make sure that migration from 1.0.3 is smooth, however we also want migration from Beta3 to be smooth.
>
>
> I am actually over asked about the migration from beta.3, not sure that's really a huge concern here

If that's not required, we can obviously skip such testing.
>  
>>
>>
>> Many thanks,
>>
>> Karel
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> [hidden email]
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev
Reply | Threaded
Open this post in threaded view
|

Re: [aerogear-dev] Breaking changes in between UPS 1.1.0.Beta3 and 1.1.0.Final

Matthias Wessendorf


On Mon, Aug 17, 2015 at 4:52 PM, Karel Piwko <[hidden email]> wrote:

Thanks Matthias,

Comments inline.

Karel

Dne 17. 8. 2015 11:54 napsal uživatel "Matthias Wessendorf" <[hidden email]>:
>
> Hi Karel,
>
> On Mon, Aug 17, 2015 at 9:08 AM, Karel Piwko <[hidden email]> wrote:
>>
>> Hello All,
>>
>> I'm really unhappy with number of breaking changes that has appeared in the latest staged 1.1.0.Final - mostly these changes were related to massive DB schema updates. I'd expect such changes to happen in Alpha phase and not in between Beta3 and Final.
>
>
> I fully understand your frustration. I think the source of this issue is that the migration work took much longer than expected, getting it ported to master branch (was introduced on 1.0.3).
>  
>>
>>
>> I understand that a lot of these changes have been driven by late inclusion of migrator to 1.1 branch. That said, what is the plan with 1.1.0.Final? Are you guys going to remove the changes or at least make sure they do not impact users running Beta3?
>
>
> I think the biggest concern is clearly supporting users, upgrading from 1.0.3
>  
>>
>> I've seen it has been de-staged and there have been a few commits reverting DB changes back. Is there any estimate when 1.1.0.Final will be restaged?
>
>
> Yeah, there will be a re-staging coming soon. Question, due to the huge changes, what about doing a Beta.4 and following up w a .Final in week or two?
> To make sure things are stable, before we stage a 1.1.0.Final - makes sense ? 

Sounds good to me!

>  
>>
>>
>> QE plan is to make sure that migration from 1.0.3 is smooth, however we also want migration from Beta3 to be smooth.
>
>
> I am actually over asked about the migration from beta.3, not sure that's really a huge concern here

If that's not required, we can obviously skip such testing.


yeah, sounds good to me!

Ok, Karel, again, I understand the pain, and I will do a beta.4 staging later this evening!
 


>  
>>
>>
>> Many thanks,
>>
>> Karel
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> [hidden email]
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--

_______________________________________________
aerogear-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-dev