You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@fineract.apache.org by James Dailey <ja...@gmail.com> on 2022/09/08 14:38:15 UTC
Fineract Release registry
There is a register of releases at Apache
https://projects.apache.org/releases.html
It has releases for apache projects going back several years, but for
Fineract, I only see the last two releases 1.17 and 1.18.
So, is it fixed going forward?
(Obviously, the release list on fineract.apache.org of course has
everything 1.0 through 1.18. )
Re: Fineract Release registry
Posted by James Dailey <ja...@gmail.com>.
Thanks Aleks. That's good.
Nothing to do at this point. It's just a bit of minor housekeeping.
On Thu, Sep 8, 2022 at 10:07 AM Aleksandar Vidakovic <
cheetah@monkeysintown.com> wrote:
> I am doing entries there for every release I do... from the top of my head
> there should be entries for at least 1.6.0, 1.7.0 and 1.8.0... I was
> unavailable for 1.5.0 (Petri did that one... I would actually guess he did
> an entry there too... because the person doing the release gets an
> automatic email reminder from Apache); and for 1.4.0 (which was the first
> release I did) I don't remember anymore.
>
> This is a screenshot of the release report page from Apache:
>
> [image: image.png]
>
> ... as you can see all releases (that I know of since Mifos moved to
> Apache) are listed here... and that's the only page/tool that I am aware of
> where we are able to manage releases.
>
> Note: there is also a way to "archive" releases (behind the scenes the
> downloadable artifacts are moved to some kind of secondary servers)...
> maybe that has an influence if the releases are listed on that page you
> sent... I believe everything earlier than 1.6.0 is archived.
>
> Please let me know if you think there's something to do here....
>
> On Thu, Sep 8, 2022 at 4:38 PM James Dailey <ja...@gmail.com>
> wrote:
>
>> There is a register of releases at Apache
>> https://projects.apache.org/releases.html
>>
>> It has releases for apache projects going back several years, but for
>> Fineract, I only see the last two releases 1.17 and 1.18.
>>
>> So, is it fixed going forward?
>>
>> (Obviously, the release list on fineract.apache.org of course has
>> everything 1.0 through 1.18. )
>>
>>
>
Re: Fineract Release registry
Posted by Aleksandar Vidakovic <ch...@monkeysintown.com>.
Hi Avik,
... yup, that works... calendar invite is out... feel free to share with
anyone you think should attend.
Cheers,
Aleks
On Wed, Sep 21, 2022 at 9:09 AM Avik Ganguly <av...@fynarfin.io> wrote:
> Hi Aleks,
>
> Would this Friday 10AM GMT or 12PM GMT work for you?
>
> With best regards,
> Avik.
>
> On Mon, Sep 19, 2022 at 10:20 PM Aleksandar Vidakovic <
> cheetah@monkeysintown.com> wrote:
>
>> Hi Avik,
>>
>> ... I've created a release plugin and documented the steps... most of the
>> previously manual steps are now available as Gradle tasks... I have a few
>> left that need a bit more work (creating release pages and similar)... but
>> I'd say 90% is now doable via Gradle.
>>
>> The current documentation:
>> https://fineract.apache.org/docs/current/#_releases
>>
>> Can be of course improved... but overall this is already a lot easier
>> than it used to be.
>>
>> If you want we can arrange a Google Meet and I'll show you around...
>> there are one or two caveats to keep in mind (just in general to ensure
>> that the release doesn't go wrong... mostly because of the Git branch
>> structure we have).
>>
>> Let me know...
>>
>> Cheers,
>>
>> Aleks
>>
>> On Mon, Sep 19, 2022 at 4:47 PM Avik Ganguly <av...@fynarfin.io> wrote:
>>
>>> Hi Aleks,
>>>
>>> For the release artifact signing, publishing and minor housekeeping
>>> steps, do you happen to have a script that you have that I can use?
>>>
>>> With best regards,
>>> Avik.
>>>
>>> On Fri, Sep 9, 2022 at 12:01 AM Ed Cable <ed...@mifos.org> wrote:
>>>
>>>> I would leave it as is with 1.7 and 1.8 being currently recommended
>>>> releases especially given that's what Aleks had communicated around support
>>>> for hotfixes going back 2 releases (current and previous).
>>>>
>>>> Ed
>>>>
>>>> On Thu, Sep 8, 2022 at 11:07 AM James Dailey <ja...@gmail.com>
>>>> wrote:
>>>>
>>>>> Ah, Thanks Petri. Good to know!
>>>>>
>>>>> I think this relates to the idea of having a LTS (Long Term Support)
>>>>> version which would have backward compatibility.
>>>>> It could be useful for Fineract as we evolve rapidly.
>>>>>
>>>>> There may be a release (for example 1.16) that should be kept as a
>>>>> "current release" for some backward compatibility... or maybe some other
>>>>> release version.
>>>>>
>>>>> This also relates, I would guess, to the notion of point releases and
>>>>> gitActions for patches.
>>>>> Thus if we had 1.16 release as an active release, we would also have
>>>>> to manage patches for that active release, for at least a defined period of
>>>>> time.
>>>>>
>>>>> So, should we archive 1.17?
>>>>> +1 from me.
>>>>>
>>>>>
>>>>> James Dailey
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Sep 8, 2022 at 11:01 AM Petri Tuomola
>>>>> <pe...@tuomola.org.invalid> wrote:
>>>>>
>>>>>> Hi - that's correct: that site only lists "current recommended
>>>>>> releases" ie the releases that are on dist.apache.org. For us,
>>>>>> that's currently the last two versions 1.7 and 1.8.
>>>>>>
>>>>>> The older releases have been moved to archive.apache.org and hence
>>>>>> they don't appear.
>>>>>>
>>>>>> In fact we probably should archive 1.7 as well, as I don't think we
>>>>>> recommend people using older releases? Many other Apache projects seem to
>>>>>> include the last release only.
>>>>>>
>>>>>> Regards
>>>>>> Petri
>>>>>>
>>>>>>
>>>>>> On Fri, Sep 9, 2022, 01:07 Aleksandar Vidakovic <
>>>>>> cheetah@monkeysintown.com> wrote:
>>>>>>
>>>>>>> I am doing entries there for every release I do... from the top of
>>>>>>> my head there should be entries for at least 1.6.0, 1.7.0 and 1.8.0... I
>>>>>>> was unavailable for 1.5.0 (Petri did that one... I would actually guess he
>>>>>>> did an entry there too... because the person doing the release gets an
>>>>>>> automatic email reminder from Apache); and for 1.4.0 (which was the first
>>>>>>> release I did) I don't remember anymore.
>>>>>>>
>>>>>>> This is a screenshot of the release report page from Apache:
>>>>>>>
>>>>>>> [image: image.png]
>>>>>>>
>>>>>>> ... as you can see all releases (that I know of since Mifos moved to
>>>>>>> Apache) are listed here... and that's the only page/tool that I am aware of
>>>>>>> where we are able to manage releases.
>>>>>>>
>>>>>>> Note: there is also a way to "archive" releases (behind the scenes
>>>>>>> the downloadable artifacts are moved to some kind of secondary servers)...
>>>>>>> maybe that has an influence if the releases are listed on that page you
>>>>>>> sent... I believe everything earlier than 1.6.0 is archived.
>>>>>>>
>>>>>>> Please let me know if you think there's something to do here....
>>>>>>>
>>>>>>> On Thu, Sep 8, 2022 at 4:38 PM James Dailey <ja...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> There is a register of releases at Apache
>>>>>>>> https://projects.apache.org/releases.html
>>>>>>>>
>>>>>>>> It has releases for apache projects going back several years, but
>>>>>>>> for Fineract, I only see the last two releases 1.17 and 1.18.
>>>>>>>>
>>>>>>>> So, is it fixed going forward?
>>>>>>>>
>>>>>>>> (Obviously, the release list on fineract.apache.org of course has
>>>>>>>> everything 1.0 through 1.18. )
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>
>>>> --
>>>> *Ed Cable*
>>>> President/CEO, Mifos Initiative
>>>> edcable@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>>>>
>>>> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>>>> <http://facebook.com/mifos> <http://www.twitter.com/mifos>
>>>>
>>>>
>>> Disclaimer:
>>>
>>> Privileged & confidential information is contained in this message
>>> (including all attachments). If you are not an intended recipient of this
>>> message, please destroy this message immediately and kindly notify
>>> the sender by reply e-mail. Any unauthorised use or dissemination of
>>> this message in any manner whatsoever, in whole or in part, is strictly
>>> prohibited. This e-mail, including all attachments hereto, (i) is for
>>> discussion purposes only and shall not be deemed or construed to be a
>>> professional opinion unless expressly stated otherwise, and (ii) is not
>>> intended, written or sent to be used, and cannot and shall not be used, for
>>> any unlawful purpose. This communication, including any attachments, may
>>> not be free of viruses, interceptions or interference, and may not be
>>> compatible with your systems. You should carry out your own virus checks
>>> before opening any attachment to this e-mail. The sender of this e-mail and
>>> *Fynarfin Tech Private Limited* shall not be liable for any damage that
>>> you may sustain as a result of viruses, incompleteness of this message, a
>>> delay in receipt of this message or computer problems experienced.
>>>
>>
> Disclaimer:
>
> Privileged & confidential information is contained in this message
> (including all attachments). If you are not an intended recipient of this
> message, please destroy this message immediately and kindly notify
> the sender by reply e-mail. Any unauthorised use or dissemination of this
> message in any manner whatsoever, in whole or in part, is strictly
> prohibited. This e-mail, including all attachments hereto, (i) is for
> discussion purposes only and shall not be deemed or construed to be a
> professional opinion unless expressly stated otherwise, and (ii) is not
> intended, written or sent to be used, and cannot and shall not be used, for
> any unlawful purpose. This communication, including any attachments, may
> not be free of viruses, interceptions or interference, and may not be
> compatible with your systems. You should carry out your own virus checks
> before opening any attachment to this e-mail. The sender of this e-mail and
> *Fynarfin Tech Private Limited* shall not be liable for any damage that
> you may sustain as a result of viruses, incompleteness of this message, a
> delay in receipt of this message or computer problems experienced.
>
Re: Fineract Release registry
Posted by Avik Ganguly <av...@fynarfin.io>.
Hi Aleks,
Would this Friday 10AM GMT or 12PM GMT work for you?
With best regards,
Avik.
On Mon, Sep 19, 2022 at 10:20 PM Aleksandar Vidakovic <
cheetah@monkeysintown.com> wrote:
> Hi Avik,
>
> ... I've created a release plugin and documented the steps... most of the
> previously manual steps are now available as Gradle tasks... I have a few
> left that need a bit more work (creating release pages and similar)... but
> I'd say 90% is now doable via Gradle.
>
> The current documentation:
> https://fineract.apache.org/docs/current/#_releases
>
> Can be of course improved... but overall this is already a lot easier than
> it used to be.
>
> If you want we can arrange a Google Meet and I'll show you around... there
> are one or two caveats to keep in mind (just in general to ensure that the
> release doesn't go wrong... mostly because of the Git branch structure we
> have).
>
> Let me know...
>
> Cheers,
>
> Aleks
>
> On Mon, Sep 19, 2022 at 4:47 PM Avik Ganguly <av...@fynarfin.io> wrote:
>
>> Hi Aleks,
>>
>> For the release artifact signing, publishing and minor housekeeping
>> steps, do you happen to have a script that you have that I can use?
>>
>> With best regards,
>> Avik.
>>
>> On Fri, Sep 9, 2022 at 12:01 AM Ed Cable <ed...@mifos.org> wrote:
>>
>>> I would leave it as is with 1.7 and 1.8 being currently recommended
>>> releases especially given that's what Aleks had communicated around support
>>> for hotfixes going back 2 releases (current and previous).
>>>
>>> Ed
>>>
>>> On Thu, Sep 8, 2022 at 11:07 AM James Dailey <ja...@gmail.com>
>>> wrote:
>>>
>>>> Ah, Thanks Petri. Good to know!
>>>>
>>>> I think this relates to the idea of having a LTS (Long Term Support)
>>>> version which would have backward compatibility.
>>>> It could be useful for Fineract as we evolve rapidly.
>>>>
>>>> There may be a release (for example 1.16) that should be kept as a
>>>> "current release" for some backward compatibility... or maybe some other
>>>> release version.
>>>>
>>>> This also relates, I would guess, to the notion of point releases and
>>>> gitActions for patches.
>>>> Thus if we had 1.16 release as an active release, we would also have to
>>>> manage patches for that active release, for at least a defined period of
>>>> time.
>>>>
>>>> So, should we archive 1.17?
>>>> +1 from me.
>>>>
>>>>
>>>> James Dailey
>>>>
>>>>
>>>>
>>>> On Thu, Sep 8, 2022 at 11:01 AM Petri Tuomola <pe...@tuomola.org.invalid>
>>>> wrote:
>>>>
>>>>> Hi - that's correct: that site only lists "current recommended
>>>>> releases" ie the releases that are on dist.apache.org. For us, that's
>>>>> currently the last two versions 1.7 and 1.8.
>>>>>
>>>>> The older releases have been moved to archive.apache.org and hence
>>>>> they don't appear.
>>>>>
>>>>> In fact we probably should archive 1.7 as well, as I don't think we
>>>>> recommend people using older releases? Many other Apache projects seem to
>>>>> include the last release only.
>>>>>
>>>>> Regards
>>>>> Petri
>>>>>
>>>>>
>>>>> On Fri, Sep 9, 2022, 01:07 Aleksandar Vidakovic <
>>>>> cheetah@monkeysintown.com> wrote:
>>>>>
>>>>>> I am doing entries there for every release I do... from the top of my
>>>>>> head there should be entries for at least 1.6.0, 1.7.0 and 1.8.0... I was
>>>>>> unavailable for 1.5.0 (Petri did that one... I would actually guess he did
>>>>>> an entry there too... because the person doing the release gets an
>>>>>> automatic email reminder from Apache); and for 1.4.0 (which was the first
>>>>>> release I did) I don't remember anymore.
>>>>>>
>>>>>> This is a screenshot of the release report page from Apache:
>>>>>>
>>>>>> [image: image.png]
>>>>>>
>>>>>> ... as you can see all releases (that I know of since Mifos moved to
>>>>>> Apache) are listed here... and that's the only page/tool that I am aware of
>>>>>> where we are able to manage releases.
>>>>>>
>>>>>> Note: there is also a way to "archive" releases (behind the scenes
>>>>>> the downloadable artifacts are moved to some kind of secondary servers)...
>>>>>> maybe that has an influence if the releases are listed on that page you
>>>>>> sent... I believe everything earlier than 1.6.0 is archived.
>>>>>>
>>>>>> Please let me know if you think there's something to do here....
>>>>>>
>>>>>> On Thu, Sep 8, 2022 at 4:38 PM James Dailey <ja...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> There is a register of releases at Apache
>>>>>>> https://projects.apache.org/releases.html
>>>>>>>
>>>>>>> It has releases for apache projects going back several years, but
>>>>>>> for Fineract, I only see the last two releases 1.17 and 1.18.
>>>>>>>
>>>>>>> So, is it fixed going forward?
>>>>>>>
>>>>>>> (Obviously, the release list on fineract.apache.org of course has
>>>>>>> everything 1.0 through 1.18. )
>>>>>>>
>>>>>>>
>>>>>>
>>>
>>> --
>>> *Ed Cable*
>>> President/CEO, Mifos Initiative
>>> edcable@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>>>
>>> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>>> <http://facebook.com/mifos> <http://www.twitter.com/mifos>
>>>
>>>
>> Disclaimer:
>>
>> Privileged & confidential information is contained in this message
>> (including all attachments). If you are not an intended recipient of this
>> message, please destroy this message immediately and kindly notify
>> the sender by reply e-mail. Any unauthorised use or dissemination of this
>> message in any manner whatsoever, in whole or in part, is strictly
>> prohibited. This e-mail, including all attachments hereto, (i) is for
>> discussion purposes only and shall not be deemed or construed to be a
>> professional opinion unless expressly stated otherwise, and (ii) is not
>> intended, written or sent to be used, and cannot and shall not be used, for
>> any unlawful purpose. This communication, including any attachments, may
>> not be free of viruses, interceptions or interference, and may not be
>> compatible with your systems. You should carry out your own virus checks
>> before opening any attachment to this e-mail. The sender of this e-mail and
>> *Fynarfin Tech Private Limited* shall not be liable for any damage that
>> you may sustain as a result of viruses, incompleteness of this message, a
>> delay in receipt of this message or computer problems experienced.
>>
>
--
Disclaimer:
Privileged & confidential information is contained in this
message (including all attachments). If you are not an intended recipient
of this message, please destroy this message immediately and kindly notify
the sender by reply e-mail. Any unauthorised use or dissemination of this
message in any manner whatsoever, in whole or in part, is strictly
prohibited. This e-mail, including all attachments hereto, (i) is for
discussion purposes only and shall not be deemed or construed to be a
professional opinion unless expressly stated otherwise, and (ii) is not
intended, written or sent to be used, and cannot and shall not be used, for
any unlawful purpose. This communication, including any attachments, may
not be free of viruses, interceptions or interference, and may not be
compatible with your systems. You should carry out your own virus checks
before opening any attachment to this e-mail. The sender of this e-mail and
*Fynarfin Tech Private Limited* shall not be liable for any damage that
you may sustain as a result of viruses, incompleteness of this message, a
delay in receipt of this message or computer problems experienced.
Re: Fineract Release registry
Posted by Aleksandar Vidakovic <ch...@monkeysintown.com>.
Hi Avik,
... I've created a release plugin and documented the steps... most of the
previously manual steps are now available as Gradle tasks... I have a few
left that need a bit more work (creating release pages and similar)... but
I'd say 90% is now doable via Gradle.
The current documentation:
https://fineract.apache.org/docs/current/#_releases
Can be of course improved... but overall this is already a lot easier than
it used to be.
If you want we can arrange a Google Meet and I'll show you around... there
are one or two caveats to keep in mind (just in general to ensure that the
release doesn't go wrong... mostly because of the Git branch structure we
have).
Let me know...
Cheers,
Aleks
On Mon, Sep 19, 2022 at 4:47 PM Avik Ganguly <av...@fynarfin.io> wrote:
> Hi Aleks,
>
> For the release artifact signing, publishing and minor housekeeping steps,
> do you happen to have a script that you have that I can use?
>
> With best regards,
> Avik.
>
> On Fri, Sep 9, 2022 at 12:01 AM Ed Cable <ed...@mifos.org> wrote:
>
>> I would leave it as is with 1.7 and 1.8 being currently recommended
>> releases especially given that's what Aleks had communicated around support
>> for hotfixes going back 2 releases (current and previous).
>>
>> Ed
>>
>> On Thu, Sep 8, 2022 at 11:07 AM James Dailey <ja...@gmail.com>
>> wrote:
>>
>>> Ah, Thanks Petri. Good to know!
>>>
>>> I think this relates to the idea of having a LTS (Long Term Support)
>>> version which would have backward compatibility.
>>> It could be useful for Fineract as we evolve rapidly.
>>>
>>> There may be a release (for example 1.16) that should be kept as a
>>> "current release" for some backward compatibility... or maybe some other
>>> release version.
>>>
>>> This also relates, I would guess, to the notion of point releases and
>>> gitActions for patches.
>>> Thus if we had 1.16 release as an active release, we would also have to
>>> manage patches for that active release, for at least a defined period of
>>> time.
>>>
>>> So, should we archive 1.17?
>>> +1 from me.
>>>
>>>
>>> James Dailey
>>>
>>>
>>>
>>> On Thu, Sep 8, 2022 at 11:01 AM Petri Tuomola <pe...@tuomola.org.invalid>
>>> wrote:
>>>
>>>> Hi - that's correct: that site only lists "current recommended
>>>> releases" ie the releases that are on dist.apache.org. For us, that's
>>>> currently the last two versions 1.7 and 1.8.
>>>>
>>>> The older releases have been moved to archive.apache.org and hence
>>>> they don't appear.
>>>>
>>>> In fact we probably should archive 1.7 as well, as I don't think we
>>>> recommend people using older releases? Many other Apache projects seem to
>>>> include the last release only.
>>>>
>>>> Regards
>>>> Petri
>>>>
>>>>
>>>> On Fri, Sep 9, 2022, 01:07 Aleksandar Vidakovic <
>>>> cheetah@monkeysintown.com> wrote:
>>>>
>>>>> I am doing entries there for every release I do... from the top of my
>>>>> head there should be entries for at least 1.6.0, 1.7.0 and 1.8.0... I was
>>>>> unavailable for 1.5.0 (Petri did that one... I would actually guess he did
>>>>> an entry there too... because the person doing the release gets an
>>>>> automatic email reminder from Apache); and for 1.4.0 (which was the first
>>>>> release I did) I don't remember anymore.
>>>>>
>>>>> This is a screenshot of the release report page from Apache:
>>>>>
>>>>> [image: image.png]
>>>>>
>>>>> ... as you can see all releases (that I know of since Mifos moved to
>>>>> Apache) are listed here... and that's the only page/tool that I am aware of
>>>>> where we are able to manage releases.
>>>>>
>>>>> Note: there is also a way to "archive" releases (behind the scenes the
>>>>> downloadable artifacts are moved to some kind of secondary servers)...
>>>>> maybe that has an influence if the releases are listed on that page you
>>>>> sent... I believe everything earlier than 1.6.0 is archived.
>>>>>
>>>>> Please let me know if you think there's something to do here....
>>>>>
>>>>> On Thu, Sep 8, 2022 at 4:38 PM James Dailey <ja...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> There is a register of releases at Apache
>>>>>> https://projects.apache.org/releases.html
>>>>>>
>>>>>> It has releases for apache projects going back several years, but for
>>>>>> Fineract, I only see the last two releases 1.17 and 1.18.
>>>>>>
>>>>>> So, is it fixed going forward?
>>>>>>
>>>>>> (Obviously, the release list on fineract.apache.org of course has
>>>>>> everything 1.0 through 1.18. )
>>>>>>
>>>>>>
>>>>>
>>
>> --
>> *Ed Cable*
>> President/CEO, Mifos Initiative
>> edcable@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>>
>> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>> <http://facebook.com/mifos> <http://www.twitter.com/mifos>
>>
>>
> Disclaimer:
>
> Privileged & confidential information is contained in this message
> (including all attachments). If you are not an intended recipient of this
> message, please destroy this message immediately and kindly notify
> the sender by reply e-mail. Any unauthorised use or dissemination of this
> message in any manner whatsoever, in whole or in part, is strictly
> prohibited. This e-mail, including all attachments hereto, (i) is for
> discussion purposes only and shall not be deemed or construed to be a
> professional opinion unless expressly stated otherwise, and (ii) is not
> intended, written or sent to be used, and cannot and shall not be used, for
> any unlawful purpose. This communication, including any attachments, may
> not be free of viruses, interceptions or interference, and may not be
> compatible with your systems. You should carry out your own virus checks
> before opening any attachment to this e-mail. The sender of this e-mail and
> *Fynarfin Tech Private Limited* shall not be liable for any damage that
> you may sustain as a result of viruses, incompleteness of this message, a
> delay in receipt of this message or computer problems experienced.
>
Re: Fineract Release registry
Posted by Avik Ganguly <av...@fynarfin.io>.
Hi Aleks,
For the release artifact signing, publishing and minor housekeeping steps,
do you happen to have a script that you have that I can use?
With best regards,
Avik.
On Fri, Sep 9, 2022 at 12:01 AM Ed Cable <ed...@mifos.org> wrote:
> I would leave it as is with 1.7 and 1.8 being currently recommended
> releases especially given that's what Aleks had communicated around support
> for hotfixes going back 2 releases (current and previous).
>
> Ed
>
> On Thu, Sep 8, 2022 at 11:07 AM James Dailey <ja...@gmail.com>
> wrote:
>
>> Ah, Thanks Petri. Good to know!
>>
>> I think this relates to the idea of having a LTS (Long Term Support)
>> version which would have backward compatibility.
>> It could be useful for Fineract as we evolve rapidly.
>>
>> There may be a release (for example 1.16) that should be kept as a
>> "current release" for some backward compatibility... or maybe some other
>> release version.
>>
>> This also relates, I would guess, to the notion of point releases and
>> gitActions for patches.
>> Thus if we had 1.16 release as an active release, we would also have to
>> manage patches for that active release, for at least a defined period of
>> time.
>>
>> So, should we archive 1.17?
>> +1 from me.
>>
>>
>> James Dailey
>>
>>
>>
>> On Thu, Sep 8, 2022 at 11:01 AM Petri Tuomola <pe...@tuomola.org.invalid>
>> wrote:
>>
>>> Hi - that's correct: that site only lists "current recommended releases"
>>> ie the releases that are on dist.apache.org. For us, that's currently
>>> the last two versions 1.7 and 1.8.
>>>
>>> The older releases have been moved to archive.apache.org and hence they
>>> don't appear.
>>>
>>> In fact we probably should archive 1.7 as well, as I don't think we
>>> recommend people using older releases? Many other Apache projects seem to
>>> include the last release only.
>>>
>>> Regards
>>> Petri
>>>
>>>
>>> On Fri, Sep 9, 2022, 01:07 Aleksandar Vidakovic <
>>> cheetah@monkeysintown.com> wrote:
>>>
>>>> I am doing entries there for every release I do... from the top of my
>>>> head there should be entries for at least 1.6.0, 1.7.0 and 1.8.0... I was
>>>> unavailable for 1.5.0 (Petri did that one... I would actually guess he did
>>>> an entry there too... because the person doing the release gets an
>>>> automatic email reminder from Apache); and for 1.4.0 (which was the first
>>>> release I did) I don't remember anymore.
>>>>
>>>> This is a screenshot of the release report page from Apache:
>>>>
>>>> [image: image.png]
>>>>
>>>> ... as you can see all releases (that I know of since Mifos moved to
>>>> Apache) are listed here... and that's the only page/tool that I am aware of
>>>> where we are able to manage releases.
>>>>
>>>> Note: there is also a way to "archive" releases (behind the scenes the
>>>> downloadable artifacts are moved to some kind of secondary servers)...
>>>> maybe that has an influence if the releases are listed on that page you
>>>> sent... I believe everything earlier than 1.6.0 is archived.
>>>>
>>>> Please let me know if you think there's something to do here....
>>>>
>>>> On Thu, Sep 8, 2022 at 4:38 PM James Dailey <ja...@gmail.com>
>>>> wrote:
>>>>
>>>>> There is a register of releases at Apache
>>>>> https://projects.apache.org/releases.html
>>>>>
>>>>> It has releases for apache projects going back several years, but for
>>>>> Fineract, I only see the last two releases 1.17 and 1.18.
>>>>>
>>>>> So, is it fixed going forward?
>>>>>
>>>>> (Obviously, the release list on fineract.apache.org of course has
>>>>> everything 1.0 through 1.18. )
>>>>>
>>>>>
>>>>
>
> --
> *Ed Cable*
> President/CEO, Mifos Initiative
> edcable@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>
> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
> <http://facebook.com/mifos> <http://www.twitter.com/mifos>
>
>
--
Disclaimer:
Privileged & confidential information is contained in this
message (including all attachments). If you are not an intended recipient
of this message, please destroy this message immediately and kindly notify
the sender by reply e-mail. Any unauthorised use or dissemination of this
message in any manner whatsoever, in whole or in part, is strictly
prohibited. This e-mail, including all attachments hereto, (i) is for
discussion purposes only and shall not be deemed or construed to be a
professional opinion unless expressly stated otherwise, and (ii) is not
intended, written or sent to be used, and cannot and shall not be used, for
any unlawful purpose. This communication, including any attachments, may
not be free of viruses, interceptions or interference, and may not be
compatible with your systems. You should carry out your own virus checks
before opening any attachment to this e-mail. The sender of this e-mail and
*Fynarfin Tech Private Limited* shall not be liable for any damage that
you may sustain as a result of viruses, incompleteness of this message, a
delay in receipt of this message or computer problems experienced.
Re: Fineract Release registry
Posted by Ed Cable <ed...@mifos.org>.
I would leave it as is with 1.7 and 1.8 being currently recommended
releases especially given that's what Aleks had communicated around support
for hotfixes going back 2 releases (current and previous).
Ed
On Thu, Sep 8, 2022 at 11:07 AM James Dailey <ja...@gmail.com> wrote:
> Ah, Thanks Petri. Good to know!
>
> I think this relates to the idea of having a LTS (Long Term Support)
> version which would have backward compatibility.
> It could be useful for Fineract as we evolve rapidly.
>
> There may be a release (for example 1.16) that should be kept as a
> "current release" for some backward compatibility... or maybe some other
> release version.
>
> This also relates, I would guess, to the notion of point releases and
> gitActions for patches.
> Thus if we had 1.16 release as an active release, we would also have to
> manage patches for that active release, for at least a defined period of
> time.
>
> So, should we archive 1.17?
> +1 from me.
>
>
> James Dailey
>
>
>
> On Thu, Sep 8, 2022 at 11:01 AM Petri Tuomola <pe...@tuomola.org.invalid>
> wrote:
>
>> Hi - that's correct: that site only lists "current recommended releases"
>> ie the releases that are on dist.apache.org. For us, that's currently
>> the last two versions 1.7 and 1.8.
>>
>> The older releases have been moved to archive.apache.org and hence they
>> don't appear.
>>
>> In fact we probably should archive 1.7 as well, as I don't think we
>> recommend people using older releases? Many other Apache projects seem to
>> include the last release only.
>>
>> Regards
>> Petri
>>
>>
>> On Fri, Sep 9, 2022, 01:07 Aleksandar Vidakovic <
>> cheetah@monkeysintown.com> wrote:
>>
>>> I am doing entries there for every release I do... from the top of my
>>> head there should be entries for at least 1.6.0, 1.7.0 and 1.8.0... I was
>>> unavailable for 1.5.0 (Petri did that one... I would actually guess he did
>>> an entry there too... because the person doing the release gets an
>>> automatic email reminder from Apache); and for 1.4.0 (which was the first
>>> release I did) I don't remember anymore.
>>>
>>> This is a screenshot of the release report page from Apache:
>>>
>>> [image: image.png]
>>>
>>> ... as you can see all releases (that I know of since Mifos moved to
>>> Apache) are listed here... and that's the only page/tool that I am aware of
>>> where we are able to manage releases.
>>>
>>> Note: there is also a way to "archive" releases (behind the scenes the
>>> downloadable artifacts are moved to some kind of secondary servers)...
>>> maybe that has an influence if the releases are listed on that page you
>>> sent... I believe everything earlier than 1.6.0 is archived.
>>>
>>> Please let me know if you think there's something to do here....
>>>
>>> On Thu, Sep 8, 2022 at 4:38 PM James Dailey <ja...@gmail.com>
>>> wrote:
>>>
>>>> There is a register of releases at Apache
>>>> https://projects.apache.org/releases.html
>>>>
>>>> It has releases for apache projects going back several years, but for
>>>> Fineract, I only see the last two releases 1.17 and 1.18.
>>>>
>>>> So, is it fixed going forward?
>>>>
>>>> (Obviously, the release list on fineract.apache.org of course has
>>>> everything 1.0 through 1.18. )
>>>>
>>>>
>>>
--
*Ed Cable*
President/CEO, Mifos Initiative
edcable@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
*Collectively Creating a World of 3 Billion Maries | *http://mifos.org
<http://facebook.com/mifos> <http://www.twitter.com/mifos>
Re: Fineract Release registry
Posted by James Dailey <ja...@gmail.com>.
Ah, Thanks Petri. Good to know!
I think this relates to the idea of having a LTS (Long Term Support)
version which would have backward compatibility.
It could be useful for Fineract as we evolve rapidly.
There may be a release (for example 1.16) that should be kept as a "current
release" for some backward compatibility... or maybe some other release
version.
This also relates, I would guess, to the notion of point releases and
gitActions for patches.
Thus if we had 1.16 release as an active release, we would also have to
manage patches for that active release, for at least a defined period of
time.
So, should we archive 1.17?
+1 from me.
James Dailey
On Thu, Sep 8, 2022 at 11:01 AM Petri Tuomola <pe...@tuomola.org.invalid>
wrote:
> Hi - that's correct: that site only lists "current recommended releases"
> ie the releases that are on dist.apache.org. For us, that's currently the
> last two versions 1.7 and 1.8.
>
> The older releases have been moved to archive.apache.org and hence they
> don't appear.
>
> In fact we probably should archive 1.7 as well, as I don't think we
> recommend people using older releases? Many other Apache projects seem to
> include the last release only.
>
> Regards
> Petri
>
>
> On Fri, Sep 9, 2022, 01:07 Aleksandar Vidakovic <ch...@monkeysintown.com>
> wrote:
>
>> I am doing entries there for every release I do... from the top of my
>> head there should be entries for at least 1.6.0, 1.7.0 and 1.8.0... I was
>> unavailable for 1.5.0 (Petri did that one... I would actually guess he did
>> an entry there too... because the person doing the release gets an
>> automatic email reminder from Apache); and for 1.4.0 (which was the first
>> release I did) I don't remember anymore.
>>
>> This is a screenshot of the release report page from Apache:
>>
>> [image: image.png]
>>
>> ... as you can see all releases (that I know of since Mifos moved to
>> Apache) are listed here... and that's the only page/tool that I am aware of
>> where we are able to manage releases.
>>
>> Note: there is also a way to "archive" releases (behind the scenes the
>> downloadable artifacts are moved to some kind of secondary servers)...
>> maybe that has an influence if the releases are listed on that page you
>> sent... I believe everything earlier than 1.6.0 is archived.
>>
>> Please let me know if you think there's something to do here....
>>
>> On Thu, Sep 8, 2022 at 4:38 PM James Dailey <ja...@gmail.com>
>> wrote:
>>
>>> There is a register of releases at Apache
>>> https://projects.apache.org/releases.html
>>>
>>> It has releases for apache projects going back several years, but for
>>> Fineract, I only see the last two releases 1.17 and 1.18.
>>>
>>> So, is it fixed going forward?
>>>
>>> (Obviously, the release list on fineract.apache.org of course has
>>> everything 1.0 through 1.18. )
>>>
>>>
>>
Re: Fineract Release registry
Posted by Petri Tuomola <pe...@tuomola.org.INVALID>.
Hi - that's correct: that site only lists "current recommended releases" ie
the releases that are on dist.apache.org. For us, that's currently the last
two versions 1.7 and 1.8.
The older releases have been moved to archive.apache.org and hence they
don't appear.
In fact we probably should archive 1.7 as well, as I don't think we
recommend people using older releases? Many other Apache projects seem to
include the last release only.
Regards
Petri
On Fri, Sep 9, 2022, 01:07 Aleksandar Vidakovic <ch...@monkeysintown.com>
wrote:
> I am doing entries there for every release I do... from the top of my head
> there should be entries for at least 1.6.0, 1.7.0 and 1.8.0... I was
> unavailable for 1.5.0 (Petri did that one... I would actually guess he did
> an entry there too... because the person doing the release gets an
> automatic email reminder from Apache); and for 1.4.0 (which was the first
> release I did) I don't remember anymore.
>
> This is a screenshot of the release report page from Apache:
>
> [image: image.png]
>
> ... as you can see all releases (that I know of since Mifos moved to
> Apache) are listed here... and that's the only page/tool that I am aware of
> where we are able to manage releases.
>
> Note: there is also a way to "archive" releases (behind the scenes the
> downloadable artifacts are moved to some kind of secondary servers)...
> maybe that has an influence if the releases are listed on that page you
> sent... I believe everything earlier than 1.6.0 is archived.
>
> Please let me know if you think there's something to do here....
>
> On Thu, Sep 8, 2022 at 4:38 PM James Dailey <ja...@gmail.com>
> wrote:
>
>> There is a register of releases at Apache
>> https://projects.apache.org/releases.html
>>
>> It has releases for apache projects going back several years, but for
>> Fineract, I only see the last two releases 1.17 and 1.18.
>>
>> So, is it fixed going forward?
>>
>> (Obviously, the release list on fineract.apache.org of course has
>> everything 1.0 through 1.18. )
>>
>>
>
Re: Fineract Release registry
Posted by Aleksandar Vidakovic <ch...@monkeysintown.com>.
I am doing entries there for every release I do... from the top of my head
there should be entries for at least 1.6.0, 1.7.0 and 1.8.0... I was
unavailable for 1.5.0 (Petri did that one... I would actually guess he did
an entry there too... because the person doing the release gets an
automatic email reminder from Apache); and for 1.4.0 (which was the first
release I did) I don't remember anymore.
This is a screenshot of the release report page from Apache:
[image: image.png]
... as you can see all releases (that I know of since Mifos moved to
Apache) are listed here... and that's the only page/tool that I am aware of
where we are able to manage releases.
Note: there is also a way to "archive" releases (behind the scenes the
downloadable artifacts are moved to some kind of secondary servers)...
maybe that has an influence if the releases are listed on that page you
sent... I believe everything earlier than 1.6.0 is archived.
Please let me know if you think there's something to do here....
On Thu, Sep 8, 2022 at 4:38 PM James Dailey <ja...@gmail.com> wrote:
> There is a register of releases at Apache
> https://projects.apache.org/releases.html
>
> It has releases for apache projects going back several years, but for
> Fineract, I only see the last two releases 1.17 and 1.18.
>
> So, is it fixed going forward?
>
> (Obviously, the release list on fineract.apache.org of course has
> everything 1.0 through 1.18. )
>
>