Re: Planning Apache Fineract 1.2 Release

2018-02-27 Thread Ed Cable 
Myrle,

Thanks for adding that clarity as my initial email was probably confusing.
We are moving to time-driven releases and the initial planning period I
mentioned was to determine which features or work was ready to be
integrated and could be included in the cut-off date for that time-driven
release.

I have set up a scrum board and requested karma to grant Robert access so
he can assist in planning out the next release, Apache Fineract 1.2

Ed

On Wed, Feb 14, 2018 at 4:01 AM, Sendoro Juma <sendoro@singo.africa> wrote:

> Dear Myrle,
>
> I see your point:
>
> I think primarily we should agree that it is time-driven:
>
> Features listed or to be listed should be taken only as way of making
> focus and pushing for tasks to be completed in-time as per release
> schedule, should they fall short of time... we should move on... with our
> primary commitment which is time.
>
> How about that?
>
> Best Regards
> Sendoro
>
>
>
> - Original Message -
> From: "Myrle Krantz" <my...@apache.org>
> To: "dev" <dev@fineract.apache.org>
> Sent: Wednesday, February 14, 2018 1:55:03 PM
> Subject: Re: Planning Apache Fineract 1.2 Release
>
> Our release can either be feature-driven or time-driven.  Not both.
> If it's feature-driven, we don't release until the features are in
> there.  If it's time-driven, we release on a certain date, based on
> what's made it in.
>
> Are we in agreement that we wish to make a time-driven release?  Then
> we should be adding a feature to the list for a given release when
> that feature is integrated, and not before.
>
> Best Regards,
> Myrle
>
>
> On Wed, Feb 14, 2018 at 12:41 PM, Sendoro Juma <sendoro@singo.africa>
> wrote:
> > Hello Ed,
> >
> > +1 on all you mentioned!
> >
> > I would propose additional point which you have kind of mention it
> already on item related to API Swagger, but just as emphasize
> >
> > - APIs related issues/Enhancements that has been discovered by Mobile or
> Web client application side.
> >
> > This is so,  because we might take longer in addressing issues already
> known from client application side; buy just because of missing visibility;
> > So having this branch in Wiki page will remind us.
> >
> >
> > Best Regards
> >
> > ----- Original Message -
> > From: "Sendoro Juma" <sendoro@singo.africa>
> > To: "dev" <dev@fineract.apache.org>
> > Cc: "robertjakech Jakech" <robertjak...@gmail.com>
> > Sent: Wednesday, February 14, 2018 1:38:01 PM
> > Subject: Re: Planning Apache Fineract 1.2 Release
> >
> > Hello Ed,
> >
> > +1 on all mentioned!
> >
> > I would propose additional point which you have kind of mention already
> on API Swagger it, but just as emphasize
> >
> > - APIs related issues/Enhancements that has been discovered by Mobile or
> Web Client Application side.
> >
> > This is so,  because we might take longer in addressing should known
> from client application side by juts because of missing visibility;
> > So having this branch in Wiki page will remind us.
> >
> >
> > Best Regards
> > Sendoro
> >
> >
> >
> > - Original Message -
> > From: "Ed Cable" <edca...@mifos.org>
> > To: "dev" <dev@fineract.apache.org>, "robertjakech Jakech" <
> robertjak...@gmail.com>
> > Sent: Wednesday, February 14, 2018 9:41:07 AM
> > Subject: Planning Apache Fineract 1.2 Release
> >
> > That is a great suggestion Phil and of course any synchronous meeting
> would
> > only complement the discussion on the list and collaboraton on the wiki
> > that we'll be having.
> >
> > Taking up Phil's suggestion, let's begin the discussion on this new
> thread
> > for planning what should goi into Apache Fineract 1.2. To assist in that
> > I've set up a wiki page at
> > https://cwiki.apache.org/confluence/display/FINERACT/1.
> 2.0+-+Apache+Fineract
> >
> > Based on what I know others have been working on, here's my take on some
> of
> > the work that could be included in the release.
> >
> >- GSIM/GLIM Work from Nikhil as part of GSOC
> >- Swagger APIs work done by Sanyam and Chirag
> >- Apache Fineract tasks completed by GCI students.
> >- Changes contributed by Partners including:
> >   - BOWPI Enhancements
> >- Stellar/Fineract integration
> >- Bug Fixes and Minor Enhancements.
> >- PRs from the backlog
> >
> >
> > Let's drive this discussion f

Re: Planning Apache Fineract 1.2 Release

2018-02-27 Thread Ed Cable 
Hello Pari,

Thanks for your email. You can browse the list of project that the Mifos
Initiative mentors will be overseeing for Google Summer of Code at
https://mifosforge.jira.com/wiki/spaces/RES/pages/
225411076/Google+Summer+of+Code+2018+Ideas

It will include both project that are related to the Apache Fineract
platform as well as projects related to the Mifos X web and mobile apps.

Please browse that list there which has links to all the repos and issue
trackers.

For good beginners issues related to Apache Fineract, please browse:
https://goo.gl/f5NgHy

Welcome!

Ed

On Mon, Feb 19, 2018 at 8:34 AM, Pari Tiwari <tiwaripari13...@gmail.com>
wrote:

> Hello,
> Myself Pari Tiwari
> So actually I am very new to Mifos initiative  and it's projects. So can
> you please tell me what I can do for mifos initiative and how can I learn
> about all the tasks and projects of mifos.
> Eager to learn.
> Kindly reply
> Thank you
>
> On 19 Feb 2018 8:53 p.m., "Sendoro Juma" <sendoro@singo.africa> wrote:
>
> > Hello Sharan,
> >
> > +1
> > The JIRA voting system should be fully be utilized by us as community! As
> > part even of raising criticality!
> >
> > Cheers
> > Sendoro
> >
> > - Original Message -
> > From: "Sharan F" <sha...@apache.org>
> > To: "dev" <dev@fineract.apache.org>
> > Sent: Monday, February 19, 2018 4:25:38 PM
> > Subject: Re: Planning Apache Fineract 1.2 Release
> >
> > Hi All
> >
> > I know that in Jira you can vote for an issue (so can keep a tally of
> > which issues people see as important or want the project to implement).
> > In the existing JIra default setup there is a task type called 'Wish' so
> > maybe that could be used to capture ideas or wishes.
> >
> > Thanks
> > Sharan
> >
> > I know that Jira is setup to allow people to vote on specific issues
> >
> > On 19/02/18 14:44, Ed Cable wrote:
> > > Thanks Myrle for sharing those links to clarify the Apache tools
> > available
> > > and helping get Robert the karma to configure the necessary boards.
> > Robert,
> > > that would be a super valuable contribution that you could make
> > leveraging
> > > your skillset  and expertise around agile development to assist the
> > > community with releases of Fineract 1.x and roadmapping for Fineract
> CN.
> > >
> > > Myrle and others, do you know if Apache offers any tools for idea
> > tracking
> > > and voting like https://www.aha.io/product/features/ideas#tour-nav. In
> > > conversations for some other volunteers, we thought this might be a
> nice
> > > lightweight tool to capture high level and gauge input from a broad
> range
> > > of stakeholders to feed into a roadmap.
> > >
> > > Ed
> > >
> > > On Feb 19, 2018 03:52, "Myrle Krantz" <my...@apache.org> wrote:
> > >
> > >> Hey Robert,
> > >>
> > >> We have a jira project for Fineract and for Fineract CN
> > >>
> > >> here:
> > >> https://issues.apache.org/jira/browse/FINERACT
> > >>
> > >> and here:
> > >> https://issues.apache.org/jira/browse/FINCN
> > >>
> > >> If you want to put in the effort to create a board for one of these
> > >> two projects, I'll put in the leg work to figure out what karma you
> > >> need and how to get it for you.
> > >>
> > >> Best Regards,
> > >> Myrle
> > >>
> > >>
> > >>
> > >> On Thu, Feb 15, 2018 at 9:52 AM, robert jakech <
> robertjak...@gmail.com>
> > >> wrote:
> > >>> Do we have issue tracker wall i.e story board to track progress of
> each
> > >>> task and their statuses?
> > >>>
> > >>> On 15 Feb. 2018 6:01 pm, "Nikhil Pawar" <nickr...@gmail.com> wrote:
> > >>>
> > >>>> Hello Devs,
> > >>>>
> > >>>> The GLIM/GSIM module which was developed during GSOC 2017 will be
> sent
> > >> as
> > >>>> a new PR by this Sunday.
> > >>>> I would like to mention that this was developed under guidance of
> > Salton
> > >>>> Massally from iDT labs.
> > >>>>
> > >>>> The PR is open for evaluation by community and feedback/comments are
> > >> more
> > >>>> than welcomed!
> > >>>>
> > >>>

Re: Planning Apache Fineract 1.2 Release

2018-02-19 Thread Pari Tiwari 
Hello,
Myself Pari Tiwari
So actually I am very new to Mifos initiative  and it's projects. So can
you please tell me what I can do for mifos initiative and how can I learn
about all the tasks and projects of mifos.
Eager to learn.
Kindly reply
Thank you

On 19 Feb 2018 8:53 p.m., "Sendoro Juma" <sendoro@singo.africa> wrote:

> Hello Sharan,
>
> +1
> The JIRA voting system should be fully be utilized by us as community! As
> part even of raising criticality!
>
> Cheers
> Sendoro
>
> - Original Message -
> From: "Sharan F" <sha...@apache.org>
> To: "dev" <dev@fineract.apache.org>
> Sent: Monday, February 19, 2018 4:25:38 PM
> Subject: Re: Planning Apache Fineract 1.2 Release
>
> Hi All
>
> I know that in Jira you can vote for an issue (so can keep a tally of
> which issues people see as important or want the project to implement).
> In the existing JIra default setup there is a task type called 'Wish' so
> maybe that could be used to capture ideas or wishes.
>
> Thanks
> Sharan
>
> I know that Jira is setup to allow people to vote on specific issues
>
> On 19/02/18 14:44, Ed Cable wrote:
> > Thanks Myrle for sharing those links to clarify the Apache tools
> available
> > and helping get Robert the karma to configure the necessary boards.
> Robert,
> > that would be a super valuable contribution that you could make
> leveraging
> > your skillset  and expertise around agile development to assist the
> > community with releases of Fineract 1.x and roadmapping for Fineract CN.
> >
> > Myrle and others, do you know if Apache offers any tools for idea
> tracking
> > and voting like https://www.aha.io/product/features/ideas#tour-nav. In
> > conversations for some other volunteers, we thought this might be a nice
> > lightweight tool to capture high level and gauge input from a broad range
> > of stakeholders to feed into a roadmap.
> >
> > Ed
> >
> > On Feb 19, 2018 03:52, "Myrle Krantz" <my...@apache.org> wrote:
> >
> >> Hey Robert,
> >>
> >> We have a jira project for Fineract and for Fineract CN
> >>
> >> here:
> >> https://issues.apache.org/jira/browse/FINERACT
> >>
> >> and here:
> >> https://issues.apache.org/jira/browse/FINCN
> >>
> >> If you want to put in the effort to create a board for one of these
> >> two projects, I'll put in the leg work to figure out what karma you
> >> need and how to get it for you.
> >>
> >> Best Regards,
> >> Myrle
> >>
> >>
> >>
> >> On Thu, Feb 15, 2018 at 9:52 AM, robert jakech <robertjak...@gmail.com>
> >> wrote:
> >>> Do we have issue tracker wall i.e story board to track progress of each
> >>> task and their statuses?
> >>>
> >>> On 15 Feb. 2018 6:01 pm, "Nikhil Pawar" <nickr...@gmail.com> wrote:
> >>>
> >>>> Hello Devs,
> >>>>
> >>>> The GLIM/GSIM module which was developed during GSOC 2017 will be sent
> >> as
> >>>> a new PR by this Sunday.
> >>>> I would like to mention that this was developed under guidance of
> Salton
> >>>> Massally from iDT labs.
> >>>>
> >>>> The PR is open for evaluation by community and feedback/comments are
> >> more
> >>>> than welcomed!
> >>>>
> >>>> Regards,
> >>>> Nikhil
> >>>>
> >>>> On Wed, Feb 14, 2018 at 1:41 AM, Ed Cable <edca...@mifos.org> wrote:
> >>>>
> >>>>> That is a great suggestion Phil and of course any synchronous meeting
> >>>>> would
> >>>>> only complement the discussion on the list and collaboraton on the
> wiki
> >>>>> that we'll be having.
> >>>>>
> >>>>> Taking up Phil's suggestion, let's begin the discussion on this new
> >> thread
> >>>>> for planning what should goi into Apache Fineract 1.2. To assist in
> >> that
> >>>>> I've set up a wiki page at
> >>>>> https://cwiki.apache.org/confluence/display/FINERACT/1.2.0+-
> >>>>> +Apache+Fineract
> >>>>>
> >>>>> Based on what I know others have been working on, here's my take on
> >> some
> >>>>> of
> >>>>> the work that could be included in the release.
> >>>>>
> >>>>> - GSIM/GL

Re: Planning Apache Fineract 1.2 Release

2018-02-19 Thread Sendoro Juma 
Hello Sharan,

+1
The JIRA voting system should be fully be utilized by us as community! As part 
even of raising criticality! 

Cheers
Sendoro

- Original Message -
From: "Sharan F" <sha...@apache.org>
To: "dev" <dev@fineract.apache.org>
Sent: Monday, February 19, 2018 4:25:38 PM
Subject: Re: Planning Apache Fineract 1.2 Release

Hi All

I know that in Jira you can vote for an issue (so can keep a tally of 
which issues people see as important or want the project to implement). 
In the existing JIra default setup there is a task type called 'Wish' so 
maybe that could be used to capture ideas or wishes.

Thanks
Sharan

I know that Jira is setup to allow people to vote on specific issues

On 19/02/18 14:44, Ed Cable wrote:
> Thanks Myrle for sharing those links to clarify the Apache tools available
> and helping get Robert the karma to configure the necessary boards. Robert,
> that would be a super valuable contribution that you could make leveraging
> your skillset  and expertise around agile development to assist the
> community with releases of Fineract 1.x and roadmapping for Fineract CN.
>
> Myrle and others, do you know if Apache offers any tools for idea tracking
> and voting like https://www.aha.io/product/features/ideas#tour-nav. In
> conversations for some other volunteers, we thought this might be a nice
> lightweight tool to capture high level and gauge input from a broad range
> of stakeholders to feed into a roadmap.
>
> Ed
>
> On Feb 19, 2018 03:52, "Myrle Krantz" <my...@apache.org> wrote:
>
>> Hey Robert,
>>
>> We have a jira project for Fineract and for Fineract CN
>>
>> here:
>> https://issues.apache.org/jira/browse/FINERACT
>>
>> and here:
>> https://issues.apache.org/jira/browse/FINCN
>>
>> If you want to put in the effort to create a board for one of these
>> two projects, I'll put in the leg work to figure out what karma you
>> need and how to get it for you.
>>
>> Best Regards,
>> Myrle
>>
>>
>>
>> On Thu, Feb 15, 2018 at 9:52 AM, robert jakech <robertjak...@gmail.com>
>> wrote:
>>> Do we have issue tracker wall i.e story board to track progress of each
>>> task and their statuses?
>>>
>>> On 15 Feb. 2018 6:01 pm, "Nikhil Pawar" <nickr...@gmail.com> wrote:
>>>
>>>> Hello Devs,
>>>>
>>>> The GLIM/GSIM module which was developed during GSOC 2017 will be sent
>> as
>>>> a new PR by this Sunday.
>>>> I would like to mention that this was developed under guidance of Salton
>>>> Massally from iDT labs.
>>>>
>>>> The PR is open for evaluation by community and feedback/comments are
>> more
>>>> than welcomed!
>>>>
>>>> Regards,
>>>> Nikhil
>>>>
>>>> On Wed, Feb 14, 2018 at 1:41 AM, Ed Cable <edca...@mifos.org> wrote:
>>>>
>>>>> That is a great suggestion Phil and of course any synchronous meeting
>>>>> would
>>>>> only complement the discussion on the list and collaboraton on the wiki
>>>>> that we'll be having.
>>>>>
>>>>> Taking up Phil's suggestion, let's begin the discussion on this new
>> thread
>>>>> for planning what should goi into Apache Fineract 1.2. To assist in
>> that
>>>>> I've set up a wiki page at
>>>>> https://cwiki.apache.org/confluence/display/FINERACT/1.2.0+-
>>>>> +Apache+Fineract
>>>>>
>>>>> Based on what I know others have been working on, here's my take on
>> some
>>>>> of
>>>>> the work that could be included in the release.
>>>>>
>>>>> - GSIM/GLIM Work from Nikhil as part of GSOC
>>>>> - Swagger APIs work done by Sanyam and Chirag
>>>>> - Apache Fineract tasks completed by GCI students.
>>>>> - Changes contributed by Partners including:
>>>>>- BOWPI Enhancements
>>>>> - Stellar/Fineract integration
>>>>> - Bug Fixes and Minor Enhancements.
>>>>> - PRs from the backlog
>>>>>
>>>>>
>>>>> Let's drive this discussion forward and then a have a synchronous
>> meeting
>>>>> later to hammer out details.
>>>>>
>>>>> Ed
>>>>>
>>>>> On Mon, Feb 12, 2018 at 3:39 PM, Phil Steitz <phil.ste...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>&

Re: Planning Apache Fineract 1.2 Release

2018-02-19 Thread Sharan F 

Hi All

I know that in Jira you can vote for an issue (so can keep a tally of 
which issues people see as important or want the project to implement). 
In the existing JIra default setup there is a task type called 'Wish' so 
maybe that could be used to capture ideas or wishes.


Thanks
Sharan

I know that Jira is setup to allow people to vote on specific issues

On 19/02/18 14:44, Ed Cable wrote:

Thanks Myrle for sharing those links to clarify the Apache tools available
and helping get Robert the karma to configure the necessary boards. Robert,
that would be a super valuable contribution that you could make leveraging
your skillset  and expertise around agile development to assist the
community with releases of Fineract 1.x and roadmapping for Fineract CN.

Myrle and others, do you know if Apache offers any tools for idea tracking
and voting like https://www.aha.io/product/features/ideas#tour-nav. In
conversations for some other volunteers, we thought this might be a nice
lightweight tool to capture high level and gauge input from a broad range
of stakeholders to feed into a roadmap.

Ed

On Feb 19, 2018 03:52, "Myrle Krantz"  wrote:


Hey Robert,

We have a jira project for Fineract and for Fineract CN

here:
https://issues.apache.org/jira/browse/FINERACT

and here:
https://issues.apache.org/jira/browse/FINCN

If you want to put in the effort to create a board for one of these
two projects, I'll put in the leg work to figure out what karma you
need and how to get it for you.

Best Regards,
Myrle



On Thu, Feb 15, 2018 at 9:52 AM, robert jakech 
wrote:

Do we have issue tracker wall i.e story board to track progress of each
task and their statuses?

On 15 Feb. 2018 6:01 pm, "Nikhil Pawar"  wrote:


Hello Devs,

The GLIM/GSIM module which was developed during GSOC 2017 will be sent

as

a new PR by this Sunday.
I would like to mention that this was developed under guidance of Salton
Massally from iDT labs.

The PR is open for evaluation by community and feedback/comments are

more

than welcomed!

Regards,
Nikhil

On Wed, Feb 14, 2018 at 1:41 AM, Ed Cable  wrote:


That is a great suggestion Phil and of course any synchronous meeting
would
only complement the discussion on the list and collaboraton on the wiki
that we'll be having.

Taking up Phil's suggestion, let's begin the discussion on this new

thread

for planning what should goi into Apache Fineract 1.2. To assist in

that

I've set up a wiki page at
https://cwiki.apache.org/confluence/display/FINERACT/1.2.0+-
+Apache+Fineract

Based on what I know others have been working on, here's my take on

some

of
the work that could be included in the release.

- GSIM/GLIM Work from Nikhil as part of GSOC
- Swagger APIs work done by Sanyam and Chirag
- Apache Fineract tasks completed by GCI students.
- Changes contributed by Partners including:
   - BOWPI Enhancements
- Stellar/Fineract integration
- Bug Fixes and Minor Enhancements.
- PRs from the backlog


Let's drive this discussion forward and then a have a synchronous

meeting

later to hammer out details.

Ed

On Mon, Feb 12, 2018 at 3:39 PM, Phil Steitz 
wrote:


On 2/12/18 9:32 AM, Ed Cable wrote:

Here's the link to screencast from the discussion:
https://youtu.be/xnTGf4R2s5k

Ed

On Mon, Feb 12, 2018 at 6:32 AM, Ed Cable 

wrote:

Hi all,

Thanks to Nazeer for leading this session and the sizeable group

that

attended. Based on the process, we can clearly use the assistance

of

other

community members in the planning process and committers in the

release

process so happy we had such good attendance.

Based on the discussion, here's a proposal of how timing might

look

for

monthly release cycles with planning (a new phase) starting out

six

months

prior to the release date.

Screencast of session will be posted soon.

Please comment on the notes in the table and here's proposed

timing

for

the next 1.2 release:

Plans for Release Apache Fineract 1.2

Planning Release - Start with a Meeting on Feb 14

How about starting with a discussion on this list?  Relying on
synchronous meetings cuts out people who can't attend due to time
zones / other commitments.

Phil

Announce Release - Feb 28

QA - Feb 28 - March 14

Publish Release Notes - March 14

Vote on Release - March 21

Target release date - March 28

Stage

Description

Proposed Length

How Far in Advance of Release (Proposed)

How Far in Advance of Release (Currently)

Planning of Next Release

Discuss with community what would like to ship in next release and

what

people could work on.

Create fix version on JIRA to assign to.

Action: modify existing email template to open up planning

process,

schedule a meeting to discuss and set a tentative branching date

(i.e. 2

weeks later, if release date is a month past that).

.

1 week

6 weeks

Doesn’t Exist

Announcement of

Re: Planning Apache Fineract 1.2 Release

2018-02-19 Thread Ed Cable 
Thanks Myrle for sharing those links to clarify the Apache tools available
and helping get Robert the karma to configure the necessary boards. Robert,
that would be a super valuable contribution that you could make leveraging
your skillset  and expertise around agile development to assist the
community with releases of Fineract 1.x and roadmapping for Fineract CN.

Myrle and others, do you know if Apache offers any tools for idea tracking
and voting like https://www.aha.io/product/features/ideas#tour-nav. In
conversations for some other volunteers, we thought this might be a nice
lightweight tool to capture high level and gauge input from a broad range
of stakeholders to feed into a roadmap.

Ed

On Feb 19, 2018 03:52, "Myrle Krantz"  wrote:

> Hey Robert,
>
> We have a jira project for Fineract and for Fineract CN
>
> here:
> https://issues.apache.org/jira/browse/FINERACT
>
> and here:
> https://issues.apache.org/jira/browse/FINCN
>
> If you want to put in the effort to create a board for one of these
> two projects, I'll put in the leg work to figure out what karma you
> need and how to get it for you.
>
> Best Regards,
> Myrle
>
>
>
> On Thu, Feb 15, 2018 at 9:52 AM, robert jakech 
> wrote:
> > Do we have issue tracker wall i.e story board to track progress of each
> > task and their statuses?
> >
> > On 15 Feb. 2018 6:01 pm, "Nikhil Pawar"  wrote:
> >
> >> Hello Devs,
> >>
> >> The GLIM/GSIM module which was developed during GSOC 2017 will be sent
> as
> >> a new PR by this Sunday.
> >> I would like to mention that this was developed under guidance of Salton
> >> Massally from iDT labs.
> >>
> >> The PR is open for evaluation by community and feedback/comments are
> more
> >> than welcomed!
> >>
> >> Regards,
> >> Nikhil
> >>
> >> On Wed, Feb 14, 2018 at 1:41 AM, Ed Cable  wrote:
> >>
> >>> That is a great suggestion Phil and of course any synchronous meeting
> >>> would
> >>> only complement the discussion on the list and collaboraton on the wiki
> >>> that we'll be having.
> >>>
> >>> Taking up Phil's suggestion, let's begin the discussion on this new
> thread
> >>> for planning what should goi into Apache Fineract 1.2. To assist in
> that
> >>> I've set up a wiki page at
> >>> https://cwiki.apache.org/confluence/display/FINERACT/1.2.0+-
> >>> +Apache+Fineract
> >>>
> >>> Based on what I know others have been working on, here's my take on
> some
> >>> of
> >>> the work that could be included in the release.
> >>>
> >>>- GSIM/GLIM Work from Nikhil as part of GSOC
> >>>- Swagger APIs work done by Sanyam and Chirag
> >>>- Apache Fineract tasks completed by GCI students.
> >>>- Changes contributed by Partners including:
> >>>   - BOWPI Enhancements
> >>>- Stellar/Fineract integration
> >>>- Bug Fixes and Minor Enhancements.
> >>>- PRs from the backlog
> >>>
> >>>
> >>> Let's drive this discussion forward and then a have a synchronous
> meeting
> >>> later to hammer out details.
> >>>
> >>> Ed
> >>>
> >>> On Mon, Feb 12, 2018 at 3:39 PM, Phil Steitz 
> >>> wrote:
> >>>
> >>> > On 2/12/18 9:32 AM, Ed Cable wrote:
> >>> > > Here's the link to screencast from the discussion:
> >>> > > https://youtu.be/xnTGf4R2s5k
> >>> > >
> >>> > > Ed
> >>> > >
> >>> > > On Mon, Feb 12, 2018 at 6:32 AM, Ed Cable 
> wrote:
> >>> > >
> >>> > >> Hi all,
> >>> > >>
> >>> > >> Thanks to Nazeer for leading this session and the sizeable group
> that
> >>> > >> attended. Based on the process, we can clearly use the assistance
> of
> >>> > other
> >>> > >> community members in the planning process and committers in the
> >>> release
> >>> > >> process so happy we had such good attendance.
> >>> > >>
> >>> > >> Based on the discussion, here's a proposal of how timing might
> look
> >>> for
> >>> > >> monthly release cycles with planning (a new phase) starting out
> six
> >>> > months
> >>> > >> prior to the release date.
> >>> > >>
> >>> > >> Screencast of session will be posted soon.
> >>> > >>
> >>> > >> Please comment on the notes in the table and here's proposed
> timing
> >>> for
> >>> > >> the next 1.2 release:
> >>> > >>
> >>> > >> Plans for Release Apache Fineract 1.2
> >>> > >>
> >>> > >> Planning Release - Start with a Meeting on Feb 14
> >>> >
> >>> > How about starting with a discussion on this list?  Relying on
> >>> > synchronous meetings cuts out people who can't attend due to time
> >>> > zones / other commitments.
> >>> >
> >>> > Phil
> >>> > >>
> >>> > >> Announce Release - Feb 28
> >>> > >>
> >>> > >> QA - Feb 28 - March 14
> >>> > >>
> >>> > >> Publish Release Notes - March 14
> >>> > >>
> >>> > >> Vote on Release - March 21
> >>> > >>
> >>> > >> Target release date - March 28
> >>> > >>
> >>> > >> Stage
> >>> > >>
> >>> > >> Description
> >>> > >>
> >>> > >> Proposed Length
> >>> > >>
> >>> > >> How Far in Advance of Release (Proposed)
> >>> > >>
> >>> > >>

Re: Planning Apache Fineract 1.2 Release

2018-02-15 Thread Nikhil Pawar 
Hello Devs,

The GLIM/GSIM module which was developed during GSOC 2017 will be sent as a
new PR by this Sunday.
I would like to mention that this was developed under guidance of Salton
Massally from iDT labs.

The PR is open for evaluation by community and feedback/comments are more
than welcomed!

Regards,
Nikhil

On Wed, Feb 14, 2018 at 1:41 AM, Ed Cable  wrote:

> That is a great suggestion Phil and of course any synchronous meeting would
> only complement the discussion on the list and collaboraton on the wiki
> that we'll be having.
>
> Taking up Phil's suggestion, let's begin the discussion on this new thread
> for planning what should goi into Apache Fineract 1.2. To assist in that
> I've set up a wiki page at
> https://cwiki.apache.org/confluence/display/FINERACT/1.
> 2.0+-+Apache+Fineract
>
> Based on what I know others have been working on, here's my take on some of
> the work that could be included in the release.
>
>- GSIM/GLIM Work from Nikhil as part of GSOC
>- Swagger APIs work done by Sanyam and Chirag
>- Apache Fineract tasks completed by GCI students.
>- Changes contributed by Partners including:
>   - BOWPI Enhancements
>- Stellar/Fineract integration
>- Bug Fixes and Minor Enhancements.
>- PRs from the backlog
>
>
> Let's drive this discussion forward and then a have a synchronous meeting
> later to hammer out details.
>
> Ed
>
> On Mon, Feb 12, 2018 at 3:39 PM, Phil Steitz 
> wrote:
>
> > On 2/12/18 9:32 AM, Ed Cable wrote:
> > > Here's the link to screencast from the discussion:
> > > https://youtu.be/xnTGf4R2s5k
> > >
> > > Ed
> > >
> > > On Mon, Feb 12, 2018 at 6:32 AM, Ed Cable  wrote:
> > >
> > >> Hi all,
> > >>
> > >> Thanks to Nazeer for leading this session and the sizeable group that
> > >> attended. Based on the process, we can clearly use the assistance of
> > other
> > >> community members in the planning process and committers in the
> release
> > >> process so happy we had such good attendance.
> > >>
> > >> Based on the discussion, here's a proposal of how timing might look
> for
> > >> monthly release cycles with planning (a new phase) starting out six
> > months
> > >> prior to the release date.
> > >>
> > >> Screencast of session will be posted soon.
> > >>
> > >> Please comment on the notes in the table and here's proposed timing
> for
> > >> the next 1.2 release:
> > >>
> > >> Plans for Release Apache Fineract 1.2
> > >>
> > >> Planning Release - Start with a Meeting on Feb 14
> >
> > How about starting with a discussion on this list?  Relying on
> > synchronous meetings cuts out people who can't attend due to time
> > zones / other commitments.
> >
> > Phil
> > >>
> > >> Announce Release - Feb 28
> > >>
> > >> QA - Feb 28 - March 14
> > >>
> > >> Publish Release Notes - March 14
> > >>
> > >> Vote on Release - March 21
> > >>
> > >> Target release date - March 28
> > >>
> > >> Stage
> > >>
> > >> Description
> > >>
> > >> Proposed Length
> > >>
> > >> How Far in Advance of Release (Proposed)
> > >>
> > >> How Far in Advance of Release (Currently)
> > >>
> > >> Planning of Next Release
> > >>
> > >> Discuss with community what would like to ship in next release and
> what
> > >> people could work on.
> > >>
> > >> Create fix version on JIRA to assign to.
> > >>
> > >> Action: modify existing email template to open up planning process,
> > >> schedule a meeting to discuss and set a tentative branching date
> (i.e. 2
> > >> weeks later, if release date is a month past that).
> > >>
> > >> .
> > >>
> > >> 1 week
> > >>
> > >> 6 weeks
> > >>
> > >> Doesn’t Exist
> > >>
> > >> Announcement of Release
> > >>
> > >> Announce what is going to come in the release (should be 80% done at
> > >> least).
> > >>
> > >> Cut a release branch and freeze release branch and then develop branch
> > can
> > >> still have active work on it but only in rare cases might anything
> > >> additional from develop
> > >>
> > >> Email out sharing release branch details
> > >>
> > >> 4 weeks prior
> > >>
> > >> 1 - 2 months
> > >>
> > >> QA
> > >>
> > >> QA begins on the release branch - staging Server setup
> > >>
> > >> Might fix some regression issues
> > >>
> > >> 1 - 2 weeks
> > >>
> > >> 4 weeks prior
> > >>
> > >> JIRA Sanitization/Publish RElease Notes
> > >>
> > >> Sanitize release documentation
> > >>
> > >> Create release notes and email community release information with
> links.
> > >>
> > >>
> > >> 2 weeks prior
> > >>
> > >> Vote
> > >>
> > >> Create artifacts, sign release, etc. Open up votes
> > >>
> > >> 1 week prior
> > >>
> > >> Release
> > >>
> > >> Tally up votes, announce, update websites and infrastructure with new
> > >> release artifacts.
> > >>
> > >> Release date
> > >>
> > >>
> > >>
> > >>
> > >> On Sun, Feb 11, 2018 at 7:40 AM, Ed Cable  wrote:
> > >>
> > >>> Hi all,
> > >>>
> > >>> This meeting is happening now for anybody that wants to join.
> > >>>
> >

Re: Planning Apache Fineract 1.2 Release

2018-02-14 Thread Sendoro Juma 
Dear Myrle,

I see your point:

I think primarily we should agree that it is time-driven:

Features listed or to be listed should be taken only as way of making focus and 
pushing for tasks to be completed in-time as per release schedule, should they 
fall short of time... we should move on... with our primary commitment which is 
time.

How about that?

Best Regards
Sendoro



- Original Message -
From: "Myrle Krantz" <my...@apache.org>
To: "dev" <dev@fineract.apache.org>
Sent: Wednesday, February 14, 2018 1:55:03 PM
Subject: Re: Planning Apache Fineract 1.2 Release

Our release can either be feature-driven or time-driven.  Not both.
If it's feature-driven, we don't release until the features are in
there.  If it's time-driven, we release on a certain date, based on
what's made it in.

Are we in agreement that we wish to make a time-driven release?  Then
we should be adding a feature to the list for a given release when
that feature is integrated, and not before.

Best Regards,
Myrle


On Wed, Feb 14, 2018 at 12:41 PM, Sendoro Juma <sendoro@singo.africa> wrote:
> Hello Ed,
>
> +1 on all you mentioned!
>
> I would propose additional point which you have kind of mention it already on 
> item related to API Swagger, but just as emphasize
>
> - APIs related issues/Enhancements that has been discovered by Mobile or Web 
> client application side.
>
> This is so,  because we might take longer in addressing issues already known 
> from client application side; buy just because of missing visibility;
> So having this branch in Wiki page will remind us.
>
>
> Best Regards
>
> - Original Message -
> From: "Sendoro Juma" <sendoro@singo.africa>
> To: "dev" <dev@fineract.apache.org>
> Cc: "robertjakech Jakech" <robertjak...@gmail.com>
> Sent: Wednesday, February 14, 2018 1:38:01 PM
> Subject: Re: Planning Apache Fineract 1.2 Release
>
> Hello Ed,
>
> +1 on all mentioned!
>
> I would propose additional point which you have kind of mention already on 
> API Swagger it, but just as emphasize
>
> - APIs related issues/Enhancements that has been discovered by Mobile or Web 
> Client Application side.
>
> This is so,  because we might take longer in addressing should known from 
> client application side by juts because of missing visibility;
> So having this branch in Wiki page will remind us.
>
>
> Best Regards
> Sendoro
>
>
>
> - Original Message -
> From: "Ed Cable" <edca...@mifos.org>
> To: "dev" <dev@fineract.apache.org>, "robertjakech Jakech" 
> <robertjak...@gmail.com>
> Sent: Wednesday, February 14, 2018 9:41:07 AM
> Subject: Planning Apache Fineract 1.2 Release
>
> That is a great suggestion Phil and of course any synchronous meeting would
> only complement the discussion on the list and collaboraton on the wiki
> that we'll be having.
>
> Taking up Phil's suggestion, let's begin the discussion on this new thread
> for planning what should goi into Apache Fineract 1.2. To assist in that
> I've set up a wiki page at
> https://cwiki.apache.org/confluence/display/FINERACT/1.2.0+-+Apache+Fineract
>
> Based on what I know others have been working on, here's my take on some of
> the work that could be included in the release.
>
>- GSIM/GLIM Work from Nikhil as part of GSOC
>- Swagger APIs work done by Sanyam and Chirag
>- Apache Fineract tasks completed by GCI students.
>- Changes contributed by Partners including:
>   - BOWPI Enhancements
>- Stellar/Fineract integration
>- Bug Fixes and Minor Enhancements.
>- PRs from the backlog
>
>
> Let's drive this discussion forward and then a have a synchronous meeting
> later to hammer out details.
>
> Ed
>
> On Mon, Feb 12, 2018 at 3:39 PM, Phil Steitz <phil.ste...@gmail.com> wrote:
>
>> On 2/12/18 9:32 AM, Ed Cable wrote:
>> > Here's the link to screencast from the discussion:
>> > https://youtu.be/xnTGf4R2s5k
>> >
>> > Ed
>> >
>> > On Mon, Feb 12, 2018 at 6:32 AM, Ed Cable <edca...@mifos.org> wrote:
>> >
>> >> Hi all,
>> >>
>> >> Thanks to Nazeer for leading this session and the sizeable group that
>> >> attended. Based on the process, we can clearly use the assistance of
>> other
>> >> community members in the planning process and committers in the release
>> >> process so happy we had such good attendance.
>> >>
>> >> Based on the discussion, here's a proposal of how timing might look for
>> >> monthly release cycles with planning (a new phase) starting o

Re: Planning Apache Fineract 1.2 Release

2018-02-14 Thread Myrle Krantz 
Our release can either be feature-driven or time-driven.  Not both.
If it's feature-driven, we don't release until the features are in
there.  If it's time-driven, we release on a certain date, based on
what's made it in.

Are we in agreement that we wish to make a time-driven release?  Then
we should be adding a feature to the list for a given release when
that feature is integrated, and not before.

Best Regards,
Myrle


On Wed, Feb 14, 2018 at 12:41 PM, Sendoro Juma <sendoro@singo.africa> wrote:
> Hello Ed,
>
> +1 on all you mentioned!
>
> I would propose additional point which you have kind of mention it already on 
> item related to API Swagger, but just as emphasize
>
> - APIs related issues/Enhancements that has been discovered by Mobile or Web 
> client application side.
>
> This is so,  because we might take longer in addressing issues already known 
> from client application side; buy just because of missing visibility;
> So having this branch in Wiki page will remind us.
>
>
> Best Regards
>
> - Original Message -
> From: "Sendoro Juma" <sendoro@singo.africa>
> To: "dev" <dev@fineract.apache.org>
> Cc: "robertjakech Jakech" <robertjak...@gmail.com>
> Sent: Wednesday, February 14, 2018 1:38:01 PM
> Subject: Re: Planning Apache Fineract 1.2 Release
>
> Hello Ed,
>
> +1 on all mentioned!
>
> I would propose additional point which you have kind of mention already on 
> API Swagger it, but just as emphasize
>
> - APIs related issues/Enhancements that has been discovered by Mobile or Web 
> Client Application side.
>
> This is so,  because we might take longer in addressing should known from 
> client application side by juts because of missing visibility;
> So having this branch in Wiki page will remind us.
>
>
> Best Regards
> Sendoro
>
>
>
> - Original Message -
> From: "Ed Cable" <edca...@mifos.org>
> To: "dev" <dev@fineract.apache.org>, "robertjakech Jakech" 
> <robertjak...@gmail.com>
> Sent: Wednesday, February 14, 2018 9:41:07 AM
> Subject: Planning Apache Fineract 1.2 Release
>
> That is a great suggestion Phil and of course any synchronous meeting would
> only complement the discussion on the list and collaboraton on the wiki
> that we'll be having.
>
> Taking up Phil's suggestion, let's begin the discussion on this new thread
> for planning what should goi into Apache Fineract 1.2. To assist in that
> I've set up a wiki page at
> https://cwiki.apache.org/confluence/display/FINERACT/1.2.0+-+Apache+Fineract
>
> Based on what I know others have been working on, here's my take on some of
> the work that could be included in the release.
>
>- GSIM/GLIM Work from Nikhil as part of GSOC
>- Swagger APIs work done by Sanyam and Chirag
>- Apache Fineract tasks completed by GCI students.
>- Changes contributed by Partners including:
>   - BOWPI Enhancements
>- Stellar/Fineract integration
>- Bug Fixes and Minor Enhancements.
>- PRs from the backlog
>
>
> Let's drive this discussion forward and then a have a synchronous meeting
> later to hammer out details.
>
> Ed
>
> On Mon, Feb 12, 2018 at 3:39 PM, Phil Steitz <phil.ste...@gmail.com> wrote:
>
>> On 2/12/18 9:32 AM, Ed Cable wrote:
>> > Here's the link to screencast from the discussion:
>> > https://youtu.be/xnTGf4R2s5k
>> >
>> > Ed
>> >
>> > On Mon, Feb 12, 2018 at 6:32 AM, Ed Cable <edca...@mifos.org> wrote:
>> >
>> >> Hi all,
>> >>
>> >> Thanks to Nazeer for leading this session and the sizeable group that
>> >> attended. Based on the process, we can clearly use the assistance of
>> other
>> >> community members in the planning process and committers in the release
>> >> process so happy we had such good attendance.
>> >>
>> >> Based on the discussion, here's a proposal of how timing might look for
>> >> monthly release cycles with planning (a new phase) starting out six
>> months
>> >> prior to the release date.
>> >>
>> >> Screencast of session will be posted soon.
>> >>
>> >> Please comment on the notes in the table and here's proposed timing for
>> >> the next 1.2 release:
>> >>
>> >> Plans for Release Apache Fineract 1.2
>> >>
>> >> Planning Release - Start with a Meeting on Feb 14
>>
>> How about starting with a discussion on this list?  Relying on
>> synchronous meetings cuts out people who can't attend due to time
>>

Re: Planning Apache Fineract 1.2 Release

2018-02-14 Thread Sendoro Juma 
Hello Ed,

+1 on all you mentioned!

I would propose additional point which you have kind of mention it already on 
item related to API Swagger, but just as emphasize

- APIs related issues/Enhancements that has been discovered by Mobile or Web 
client application side.

This is so,  because we might take longer in addressing issues already known 
from client application side; buy just because of missing visibility; 
So having this branch in Wiki page will remind us.


Best Regards

- Original Message -
From: "Sendoro Juma" <sendoro@singo.africa>
To: "dev" <dev@fineract.apache.org>
Cc: "robertjakech Jakech" <robertjak...@gmail.com>
Sent: Wednesday, February 14, 2018 1:38:01 PM
Subject: Re: Planning Apache Fineract 1.2 Release

Hello Ed,

+1 on all mentioned!

I would propose additional point which you have kind of mention already on API 
Swagger it, but just as emphasize

- APIs related issues/Enhancements that has been discovered by Mobile or Web 
Client Application side.

This is so,  because we might take longer in addressing should known from 
client application side by juts because of missing visibility; 
So having this branch in Wiki page will remind us.


Best Regards
Sendoro 



- Original Message -
From: "Ed Cable" <edca...@mifos.org>
To: "dev" <dev@fineract.apache.org>, "robertjakech Jakech" 
<robertjak...@gmail.com>
Sent: Wednesday, February 14, 2018 9:41:07 AM
Subject: Planning Apache Fineract 1.2 Release

That is a great suggestion Phil and of course any synchronous meeting would
only complement the discussion on the list and collaboraton on the wiki
that we'll be having.

Taking up Phil's suggestion, let's begin the discussion on this new thread
for planning what should goi into Apache Fineract 1.2. To assist in that
I've set up a wiki page at
https://cwiki.apache.org/confluence/display/FINERACT/1.2.0+-+Apache+Fineract

Based on what I know others have been working on, here's my take on some of
the work that could be included in the release.

   - GSIM/GLIM Work from Nikhil as part of GSOC
   - Swagger APIs work done by Sanyam and Chirag
   - Apache Fineract tasks completed by GCI students.
   - Changes contributed by Partners including:
  - BOWPI Enhancements
   - Stellar/Fineract integration
   - Bug Fixes and Minor Enhancements.
   - PRs from the backlog


Let's drive this discussion forward and then a have a synchronous meeting
later to hammer out details.

Ed

On Mon, Feb 12, 2018 at 3:39 PM, Phil Steitz <phil.ste...@gmail.com> wrote:

> On 2/12/18 9:32 AM, Ed Cable wrote:
> > Here's the link to screencast from the discussion:
> > https://youtu.be/xnTGf4R2s5k
> >
> > Ed
> >
> > On Mon, Feb 12, 2018 at 6:32 AM, Ed Cable <edca...@mifos.org> wrote:
> >
> >> Hi all,
> >>
> >> Thanks to Nazeer for leading this session and the sizeable group that
> >> attended. Based on the process, we can clearly use the assistance of
> other
> >> community members in the planning process and committers in the release
> >> process so happy we had such good attendance.
> >>
> >> Based on the discussion, here's a proposal of how timing might look for
> >> monthly release cycles with planning (a new phase) starting out six
> months
> >> prior to the release date.
> >>
> >> Screencast of session will be posted soon.
> >>
> >> Please comment on the notes in the table and here's proposed timing for
> >> the next 1.2 release:
> >>
> >> Plans for Release Apache Fineract 1.2
> >>
> >> Planning Release - Start with a Meeting on Feb 14
>
> How about starting with a discussion on this list?  Relying on
> synchronous meetings cuts out people who can't attend due to time
> zones / other commitments.
>
> Phil
> >>
> >> Announce Release - Feb 28
> >>
> >> QA - Feb 28 - March 14
> >>
> >> Publish Release Notes - March 14
> >>
> >> Vote on Release - March 21
> >>
> >> Target release date - March 28
> >>
> >> Stage
> >>
> >> Description
> >>
> >> Proposed Length
> >>
> >> How Far in Advance of Release (Proposed)
> >>
> >> How Far in Advance of Release (Currently)
> >>
> >> Planning of Next Release
> >>
> >> Discuss with community what would like to ship in next release and what
> >> people could work on.
> >>
> >> Create fix version on JIRA to assign to.
> >>
> >> Action: modify existing email template to open up planning process,
> >> schedule a meeting to discuss and set a tentative branching date (

Re: Planning Apache Fineract 1.2 Release

2018-02-14 Thread Sendoro Juma 
Hello Ed,

+1 on all mentioned!

I would propose additional point which you have kind of mention already on API 
Swagger it, but just as emphasize

- APIs related issues/Enhancements that has been discovered by Mobile or Web 
Client Application side.

This is so,  because we might take longer in addressing should known from 
client application side by juts because of missing visibility; 
So having this branch in Wiki page will remind us.


Best Regards
Sendoro 



- Original Message -
From: "Ed Cable" 
To: "dev" , "robertjakech Jakech" 

Sent: Wednesday, February 14, 2018 9:41:07 AM
Subject: Planning Apache Fineract 1.2 Release

That is a great suggestion Phil and of course any synchronous meeting would
only complement the discussion on the list and collaboraton on the wiki
that we'll be having.

Taking up Phil's suggestion, let's begin the discussion on this new thread
for planning what should goi into Apache Fineract 1.2. To assist in that
I've set up a wiki page at
https://cwiki.apache.org/confluence/display/FINERACT/1.2.0+-+Apache+Fineract

Based on what I know others have been working on, here's my take on some of
the work that could be included in the release.

   - GSIM/GLIM Work from Nikhil as part of GSOC
   - Swagger APIs work done by Sanyam and Chirag
   - Apache Fineract tasks completed by GCI students.
   - Changes contributed by Partners including:
  - BOWPI Enhancements
   - Stellar/Fineract integration
   - Bug Fixes and Minor Enhancements.
   - PRs from the backlog


Let's drive this discussion forward and then a have a synchronous meeting
later to hammer out details.

Ed

On Mon, Feb 12, 2018 at 3:39 PM, Phil Steitz  wrote:

> On 2/12/18 9:32 AM, Ed Cable wrote:
> > Here's the link to screencast from the discussion:
> > https://youtu.be/xnTGf4R2s5k
> >
> > Ed
> >
> > On Mon, Feb 12, 2018 at 6:32 AM, Ed Cable  wrote:
> >
> >> Hi all,
> >>
> >> Thanks to Nazeer for leading this session and the sizeable group that
> >> attended. Based on the process, we can clearly use the assistance of
> other
> >> community members in the planning process and committers in the release
> >> process so happy we had such good attendance.
> >>
> >> Based on the discussion, here's a proposal of how timing might look for
> >> monthly release cycles with planning (a new phase) starting out six
> months
> >> prior to the release date.
> >>
> >> Screencast of session will be posted soon.
> >>
> >> Please comment on the notes in the table and here's proposed timing for
> >> the next 1.2 release:
> >>
> >> Plans for Release Apache Fineract 1.2
> >>
> >> Planning Release - Start with a Meeting on Feb 14
>
> How about starting with a discussion on this list?  Relying on
> synchronous meetings cuts out people who can't attend due to time
> zones / other commitments.
>
> Phil
> >>
> >> Announce Release - Feb 28
> >>
> >> QA - Feb 28 - March 14
> >>
> >> Publish Release Notes - March 14
> >>
> >> Vote on Release - March 21
> >>
> >> Target release date - March 28
> >>
> >> Stage
> >>
> >> Description
> >>
> >> Proposed Length
> >>
> >> How Far in Advance of Release (Proposed)
> >>
> >> How Far in Advance of Release (Currently)
> >>
> >> Planning of Next Release
> >>
> >> Discuss with community what would like to ship in next release and what
> >> people could work on.
> >>
> >> Create fix version on JIRA to assign to.
> >>
> >> Action: modify existing email template to open up planning process,
> >> schedule a meeting to discuss and set a tentative branching date (i.e. 2
> >> weeks later, if release date is a month past that).
> >>
> >> .
> >>
> >> 1 week
> >>
> >> 6 weeks
> >>
> >> Doesn’t Exist
> >>
> >> Announcement of Release
> >>
> >> Announce what is going to come in the release (should be 80% done at
> >> least).
> >>
> >> Cut a release branch and freeze release branch and then develop branch
> can
> >> still have active work on it but only in rare cases might anything
> >> additional from develop
> >>
> >> Email out sharing release branch details
> >>
> >> 4 weeks prior
> >>
> >> 1 - 2 months
> >>
> >> QA
> >>
> >> QA begins on the release branch - staging Server setup
> >>
> >> Might fix some regression issues
> >>
> >> 1 - 2 weeks
> >>
> >> 4 weeks prior
> >>
> >> JIRA Sanitization/Publish RElease Notes
> >>
> >> Sanitize release documentation
> >>
> >> Create release notes and email community release information with links.
> >>
> >>
> >> 2 weeks prior
> >>
> >> Vote
> >>
> >> Create artifacts, sign release, etc. Open up votes
> >>
> >> 1 week prior
> >>
> >> Release
> >>
> >> Tally up votes, announce, update websites and infrastructure with new
> >> release artifacts.
> >>
> >> Release date
> >>
> >>
> >>
> >>
> >> On Sun, Feb 11, 2018 at 7:40 AM, Ed Cable  wrote:
> >>
> >>> Hi all,
> >>>
> >>> This meeting is happening now for anybody that wants to join.
> >>>
> >>> Ed