From: Kevin W. <kw...@co...> - 2024-11-12 02:28:10
|
<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><img width="1" height="1" src='https://fedbdhd.r.af.d.sendibt2.com/tr/op/Ur9uXYhd9DmsbcwB3lXApLXtfNrE1U89Zalyv8u94xSKA_nQaJPlsvswBM8hB4JI8dxZs81ZSPQoAH6GWqofZAOtQMM1zCc0QfkY09Xr5KIFEBCqCmhUVu5ChgTOYAxr4ffOtVcRD12_kDy6C1hvro8hmh1v9X5RJujN257BUd8bWpyfB-Vr-hN0WPgAHBUZSPIDoCDsETGB0xoOhIRlNe2UgH9uc-Kj' /><div dir="ltr"></div><div dir="ltr">I agree with Marc that a regular cadence of releases for Tcl and Tk is preferred. Let’s say that 9.1 ships in September 2025, 9.2 ships in September 2026, and so on. Whatever features aren’t ready just roll inside the next. To me that makes more sense than an aggressive schedule for Tk and no defined schedule for Tcl. </div><div dir="ltr"><br></div><div dir="ltr">8.6.0 was released in 2012. 8.6.15 was released in 2024. Surely we can do better than that with 9.x. </div><div dir="ltr"><br><blockquote type="cite">On Nov 11, 2024, at 8:40 PM, Marc Culler <cul...@gm...> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div dir="ltr">On Mon, Nov 11, 2024 at 7:59 AM Harald Oehlmann <<a href="mailto:har...@el...">har...@el...</a>> wrote:</div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Other points were postponed due to time lack and missing people:<br> - Tcl/Tk separation<br></blockquote><div><br></div><div>I have a comment about this issue, which I think means that Tcl releases and Tk releases would be allowed to happen on different schedules. </div><div>While I don't object to this, I also don't understand what problem it aims to solve. On the other hand there is something related to Tcl and Tk releases which I think would solve a real problem, especially for projects which package Tcl and Tk. That is for Tcl and Tk to have an announced release schedule. If it were announced that a new release of Tcl and Tk would be targeted to happen at regular intervals, say once a year in June for example, I think it would simplify the work of projects which have regular release schedules of their own and whose releases depend upon Tcl and Tk. I am thinking specifically of Python, but I imagine that this also applies to Ruby and Perl, at least.</div><div><br></div><div>- Marc <br></div><div> </div><div><br> </div></div></div> <span>_______________________________________________</span><br><span>Tcl-Core mailing list</span><br><span>Tcl...@li...</span><br><span>https://lists.sourceforge.net/lists/listinfo/tcl-core</span><br></div></blockquote></body></html> |