- ignite-3.0 branch deleted - all resolved tickets with fixVersion = 3.1 changed to fixVersion = 3.0 - new projected code freeze date - Jan 20
For now, please use the 3.0 fixVersion when resolving tickets as we've been doing before. If there is a change that we don't want to include in 3.0, let me know in this thread. On Tue, Jan 14, 2025 at 12:12 PM Pavel Tupitsyn <ptupit...@apache.org> wrote: > Metastorage compaction takes more time than expected > (IGNITE-23280, IGNITE-23466), and we have a lot of small fixes coming every > day. > > Proposal: > - Move code freeze to Jan 20 (next Monday) > - Delete ignite-3.0 branch to avoid spending time on cherry-picks > - Cut ignite-3.0 again after the code freeze > > Let me know if you have any concerns or objections before tomorrow. > > On Tue, Jan 14, 2025 at 11:43 AM Andrey Mashenkov < > andrey.mashen...@gmail.com> wrote: > >> Hi, Pavel. >> >> I've found a bug in BinaryTupleComparator, which is used by Indexes, >> that byte[] comparison is non-conformed with SQL standard. >> The fix is ready [1] and merged to master. >> The fix breaks ordering in Indexes for byte strings that affects binary >> compatibility between versions. >> >> Can we add a fix to the 3.0? >> >> [1] https://issues.apache.org/jira/browse/IGNITE-24176 >> >> >> On Mon, Jan 13, 2025 at 7:30 PM Pavel Tupitsyn <ptupit...@apache.org> >> wrote: >> >> > Mikhail, no objections. Please merge to main and cherry-pick to >> ignite-3.0 >> > (I've set the fix version accordingly). >> > >> > Looks like we have to postpone the code freeze, I'll post an update >> > tomorrow. >> > >> > On Mon, Jan 13, 2025 at 6:15 PM Mikhail Pochatkin < >> m.a.pochat...@gmail.com >> > > >> > wrote: >> > >> > > Hi, guys. I have fixed a bug in CLI with incorrect SQL exception >> handling >> > > (IGNITE-24179). Any objections to merge it before code freeze? >> > > >> > > пн, 13 янв. 2025 г. в 08:45, Pavel Tupitsyn <ptupit...@apache.org>: >> > > >> > > > > Found a very nasty error IGNITE-24186, I think it's worth adding, >> > since >> > > > we might not be able to restart the cluster. >> > > > >> > > > Kirill, are you going to work on this? Any ETA? >> > > > >> > > > >> > > > > worth adding this performance fix into the scope IGNITE-24163 >> > > > >> > > > Already done and cherry-picked, nice. >> > > > >> > > > On Sun, Jan 12, 2025 at 10:00 PM Nusrat Shakarov < >> nusrat...@gmail.com> >> > > > wrote: >> > > > >> > > > > Considering that we have EventLog-related tickets in the scope, I >> > think >> > > > it >> > > > > is also worth adding this performance fix into the scope >> IGNITE-24163 >> > > > > >> > > > > On Sat, 11 Jan 2025 at 11:18, ткаленко кирилл < >> tkalkir...@yandex.ru> >> > > > > wrote: >> > > > > >> > > > > > Found a very nasty error IGNITE-24186, I think it's worth >> adding, >> > > since >> > > > > we >> > > > > > might not be able to restart the cluster. >> > > > > > >> > > > > >> > > > >> > > >> > > >> > > -- >> > > best regards, >> > > Pochatkin Mikhail. >> > > >> > >> >> >> -- >> Best regards, >> Andrey V. Mashenkov >> >
