Do we need a vote for both proposal? Regarding the EOL Policy: do we want to wait and see if the new release window works before declaring an official policy?
Regards, Alessandro > -----Messaggio originale----- > Da: Sijie Guo <guosi...@gmail.com> > Inviato: martedì 3 dicembre 2019 08:19 > A: Bookkeeper-Dev <dev@bookkeeper.apache.org> > Oggetto: Re: Website update after 4.10, Time Based Release plan and EOL > > Yes. We can probably relax the release window to be every 6 months. If the > growth of development increases again, we can revert it back to every 3 > months. > > Regarding EOL policy, we haven't really discussed how to proceed it. Most of > the systems I know are already using newer versions than 4.7.0. I think we > can consider deprecating the versions older than 4.7.0. > > Thanks, > Sijie > > On Wed, Nov 20, 2019 at 5:49 AM Alessandro Luccaroni - Diennea < > alessandro.luccar...@diennea.com> wrote: > > > Hi BookKeepers, > > after the 4.10 release I see that the > > https://bookkeeper.apache.org/community/releases/ page needs some > care. > > We are still listing 4.10 as the next feature release and we have > > skipped > > 3 release windows. > > > > I can see on Github that since the early 2019 the rate of contribution > > have slowed down a bit, so I think we should relax the Time Based > > Release Plan (new release every 6 month?). > > > > Apart from that, do we have an official EOL Policy for BookKeeper? On > > the website I see that we list all the version of BK back to v4.0.0 > > (2011) Many of these older version had very little usage, but since we > > are starting to see many project using BK downstream maybe we should > > clarify the full lifecycle of BK > > > > Alessandro Luccaroni > > Platform Manager @ Diennea - MagNews > > Tel.: (+39) 0546 066100 Int. 924 - Mob.: (+39) 393 7273519 Viale > > G.Marconi 30/14 - 48018 Faenza (RA) - Italy > > > > > > ________________________________ > > > > CONFIDENTIALITY & PRIVACY NOTICE > > This e-mail (including any attachments) is strictly confidential and > > may also contain privileged information. If you are not the intended > > recipient you are not authorised to read, print, save, process or > > disclose this message. If you have received this message by mistake, > > please inform the sender immediately and destroy this e-mail, its > attachments and any copies. > > Any use, distribution, reproduction or disclosure by any person other > > than the intended recipient is strictly prohibited and the person > > responsible may incur in penalties. > > The use of this e-mail is only for professional purposes; there is no > > guarantee that the correspondence towards this e-mail will be read > > only by the recipient, because, under certain circumstances, there may > > be a need to access this email by third subjects belonging to the Company. > > ________________________________ CONFIDENTIALITY & PRIVACY NOTICE This e-mail (including any attachments) is strictly confidential and may also contain privileged information. If you are not the intended recipient you are not authorised to read, print, save, process or disclose this message. If you have received this message by mistake, please inform the sender immediately and destroy this e-mail, its attachments and any copies. Any use, distribution, reproduction or disclosure by any person other than the intended recipient is strictly prohibited and the person responsible may incur in penalties. The use of this e-mail is only for professional purposes; there is no guarantee that the correspondence towards this e-mail will be read only by the recipient, because, under certain circumstances, there may be a need to access this email by third subjects belonging to the Company.
