Hi Davide, does that mean you want to create two releases? If 1.3.17 contains the same as 1.4.0 then why do we even want to create a 1.3.17 release?
I think it would be easier if we just rename the 1.3.17 version in JIRA to 1.4 and you only have to create a 1.4.0 release. Am I missing something? Regards Marcel On 25/02/16 15:24, "Davide Giannella" wrote: >Hello team, > >I'm planning to cut Oak 1.3.17 and 1.4.0 on Monday 29th February around >10am GMT. > >We currently have 1 blocker issue and 1 that is not blocker. > >https://issues.apache.org/jira/browse/OAK-4012 >https://issues.apache.org/jira/browse/OAK-4043 > >This means I will defer the non-blocker and block for as long as the >blocker is in place. > >Please I'd like to remind you all that off the same revision I'll branch >out 1.4 and release 1.4.0. These two activities are blocked as well on >the 1.3.17 as I'll branch off the same revision of the tag for the >release. > >So the activity will be > >- cut 1.3.17 >- branch off 1.4 >- cut 1.4.0 > >If there are any objections please let me know. Otherwise I will >re-schedule any non-resolved issue for the next iteration. > >Thanks >Davide > >
