On Thu, Nov 27, 2014 at 5:30 PM, Daan Hoogland <daan.hoogl...@gmail.com> wrote:
> ok, so that would go in 442to443? > Yes, but do you plan to do a 4.4.3? The whole debate around maintaining 4.3 vs 4.4 comes down to stakeholder's interests, you've shared that you may not want to put a lot of efforts on 4.4 branch since 4.5.0 is around but if I'm mistaken and since you're the release manager you should backport changes applicable on 4.4 and do a 4.4.3 release. That would be great for 4.4.x users. Before the patch could be ported, Hari will need to use an empty upgrade path from 4.4.2 to 4.4.3 and change versions in pom files etc. Hari let me know if you can do that in your backport or if Daan or I need to add that for you. Thanks. > > On Thu, Nov 27, 2014 at 12:52 PM, Rohit Yadav <bhais...@apache.org> wrote: > > Daan, > > > > On Thu, Nov 27, 2014 at 4:17 PM, Daan Hoogland <daan.hoogl...@gmail.com> > > wrote: > >> > >> If this contains db upgrade code, where did this go in 4.3? In the > >> review request I see changes to 442to450 upgrade files so this should > >> not go in 4.3 or 4.4. What am I missing? > > > > > > For 4.3, the upgrade path (it's just data migration no schema changes so > > easily backportable) is from 4.3.1 to 4.3.2 in Upgrade431to432 class. > > > > The fix simply goes through existing VRs and updates their RAM size, no > > schema changes here only data migrations. > > > > Regards. > > > > > > -- > Daan >
