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" <[email protected]> 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 <[email protected]>
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" <[email protected]> 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 <[email protected]> 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 <[email protected]>
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 <[email protected]>
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 <[email protected]>
wrote:
Hi all,
This meeting is happening now for anybody that wants to join.
Ed
On Sat, Feb 10, 2018 at 6:07 AM, Ed Cable <[email protected]>
wrote:
Hi all
Woule 1530GMT work on Sunday? Nazeer had a conflict on Saturday.
I'll
update the GoToTraining session.
Ed
On Thu, Feb 8, 2018 at 9:19 AM, Sendoro Juma
<[email protected]
wrote:
Hello Ed,
Just in case, same Saturday(s) but starting 15:30GMT!
if it is fine with Nazeer, then we will very much appreciate...
Sorry our request is based on the fact on belief/religious
related!
Cheers
Sendoro
----- Original Message -----
From: "Ed Cable" <[email protected]>
To: "dev" <[email protected]>
Cc: "Nazeer Hussain Shaik" <[email protected]>
Sent: Thursday, February 8, 2018 7:05:55 PM
Subject: Re: Meeting to Discuss Release Management Process
Hmm... We can reschedule to accommodate everyone. Weekdays
might
be
difficult for Nazeer with his new schedule.
Ed
On Thu, Feb 8, 2018 at 7:42 AM, Sendoro Juma
<[email protected]
wrote:
Hello Ed,
Hope you will record,
I see two members missing from our side because of that new
timing.
Cheers
Sendoro
----- Original Message -----
From: "Ed Cable" <[email protected]>
To: "dev" <[email protected]>
Cc: "Nazeer Hussain Shaik" <[email protected]>
Sent: Thursday, February 8, 2018 5:05:35 PM
Subject: Re: Meeting to Discuss Release Management Process
Hi all,
Nazeer is not available till Saturday for this meeting so I am
going
to
adjust the timing to Saturday at 1400GMT and will update the
GoToTraining
session accordingly.
Ed
On Thu, Feb 8, 2018 at 6:46 AM, Awasum Yannick <
[email protected]
wrote:
I already registered for it.
I hope it happens.
Thanks
Awasum
On Thu, Feb 8, 2018 at 1:23 PM, Nikhil Pawar <
[email protected]>
wrote:
Is this meeting happening?
I’ll be interested to participate.
Regards,
Nikhil
On Wed, Feb 7, 2018 at 10:54 AM Ed Cable <[email protected]
wrote:
Nazeer,
Per the other email thread, we'd like to set up a meeting
to
both
discuss
and improve our release management process and to transfer
knowledge
to
additional Apache Fineract committers who would like to
help
with the
release management process.
Hopefully after this meeting, we'll be able to update our
wiki
page
on
release management -
https://cwiki.apache.org/confluence/display/FINERACT/
Release+Management
- with these processes and have an expanded team of
release
managers
to
help the community release more consistently and more
often.
Would this Friday at 1400GMT work? I'll create a
GoToTraining
session
in
which others can register and join:
https://attendee.gototraining.com/r/2808817190976822274
Thanks,
Ed
--
*Ed Cable*
President/CEO, Mifos Initiative
[email protected] | 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
--
*Ed Cable*
President/CEO, Mifos Initiative
[email protected] | 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>
--
*Ed Cable*
President/CEO, Mifos Initiative
[email protected] | 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>
--
*Ed Cable*
President/CEO, Mifos Initiative
[email protected] | Skype: edcable | Mobile: +1.484.477.8649
<(484)%20477-8649>
*Collectively Creating a World of 3 Billion Maries | *
http://mifos.org
<http://facebook.com/mifos> <http://www.twitter.com/mifos>
--
*Ed Cable*
President/CEO, Mifos Initiative
[email protected] | Skype: edcable | Mobile: +1.484.477.8649
<(484)%20477-8649>
*Collectively Creating a World of 3 Billion Maries | *
http://mifos.org
<http://facebook.com/mifos> <http://www.twitter.com/mifos>
--
*Ed Cable*
President/CEO, Mifos Initiative
[email protected] | Skype: edcable | Mobile: +1.484.477.8649
<(484)%20477-8649>
*Collectively Creating a World of 3 Billion Maries | *
http://mifos.org
<http://facebook.com/mifos> <http://www.twitter.com/mifos>
--
*Ed Cable*
President/CEO, Mifos Initiative
[email protected] | 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>
