Content-Type: multipart/alternative; boundary="----=_NextPart_001_00B9_01CF5D01.49F3AB10" ------=_NextPart_001_00B9_01CF5D01.49F3AB10 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Presumably in favour of moving it to a plugin? =20 Only reason I got to think about my question was from writing some basic = unit tests on the class file =20 =20 From: Victor Boctor [mailto:vboctor@outlook.com]=20 Sent: 21 April 2014 00:47 To: 'developer discussions' Subject: Re: [mantisbt-dev] Sponsorships =20 I think we should deprecate this feature.=20 --- Original Message --- From: "P Richards" > Sent: April 20, 2014 2:48 PM To: "'developer discussions'" > Subject: [mantisbt-dev] Sponsorships Different topic :) =20 I=E2=80=99ve noticed today that the sponsorship API seems very = =E2=80=98loose=E2=80=99 =E2=80=93 is that deliberate? =20 For example, at an API level, we allow Sponsorship Paid to be set to any = value. Logically, I=E2=80=99d expect it to track payment against the = initial amount sponsored. =20 i.e. if someone decides to pay more than their initial sponsorship, I = would kind of expect the sponsorship amount to either a) be updated when = paying, or b) need to be updated first. =20 Do we consider this to behaviour a bug, or a deliberate act on our part = as it=E2=80=99s there to loosely track and not as an invoicing system ? =20 Paul =20 =20 =20 =20 ------=_NextPart_001_00B9_01CF5D01.49F3AB10 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Presumably in favour of moving it to a = plugin?

 

Only reason I got to think about my = question was from writing some basic unit tests on the class = file

 

 

From: Victor = Boctor [mailto:vboctor@outlook.com]
Sent: 21 April 2014 = 00:47
To: 'developer discussions'
Subject: Re: = [mantisbt-dev] Sponsorships

 

I think we should deprecate this feature. =

--- Original Message ---

From: "P Richards" = <paul@mantisforge.org>
Sent= : April 20, 2014 2:48 PM
To: "'developer discussions'" = <mantisbt-dev@lists.sou= rceforge.net>
Subject: [mantisbt-dev] = Sponsorships

Different topic J

 

I=E2=80=99ve noticed today that the sponsorship API = seems very =E2=80=98loose=E2=80=99 =E2=80=93 is that = deliberate?

 

For example, at an API level, we allow Sponsorship = Paid to be set to any value. Logically, I=E2=80=99d expect it to track = payment against the initial amount sponsored.

 

i.e. if = someone decides to pay more than their initial sponsorship, I would kind = of expect the sponsorship amount to either a) be updated when paying, or = b) need to be updated first.

 

Do we = consider this to behaviour a bug, or a deliberate act on our part as = it=E2=80=99s there to loosely track and not as an invoicing system = ?

 

Paul

 

 

 

 

------=_NextPart_001_00B9_01CF5D01.49F3AB10--