Re: [mantisbt-dev] Preparing for 1.2.0a3 release

[Siebrand M. <s.m...@xs...>]

Hi Olegos,

Thank you for clarifying. Correct me if I'm wrong, but you should be able to
commit the fixes to the public Mantis GIT repo. More info at
http://mantisforge.org/development. For those core developers better
acquainted with Git, it should then be really easy to test and push the
change(s) to the master repo.

Some context from my side: I am not a PHP developer, but I am able to apply
and test patches if use cases, observed and expected behaviour are
documented properly in issue descriptions.

Cheers! Siebrand

-----Oorspronkelijk bericht-----
Van: Oleg O. [mailto:ole...@ol...] 
Verzonden: dinsdag 13 januari 2009 1:23
Aan: man...@li...
Onderwerp: Re: [mantisbt-dev] Preparing for 1.2.0a3 release

Hi Siebrand,

It probably wasn't apparent (I can't seem to get threading in this ML
right, at least according to the web archives), but I was replying to
John Reese's message, particularly this part:

> I would also like to ask community members and other developers to 
> propose any other issues for a3 that either:
> 
>  - break or prevent the use of important features
>  - have a simple fix
>  - have a posted patch for git master

The issues I've listed are 2 out of 3. I define "simple" approximately
as involving one or two lines of code where it's generally clear what
these lines need to do.  (Except #9827 which is not simple according
to this criteria, but I think is important and is still not too
complicated because it's exactly analogous to another bug that's
been fixed.)

By the way, I did attach patches to some other bugs; this list is
far from all the bugs I've submitted. I haven't been attaching
patches where I'm not too sure that my fix should be adopted
verbatim. Since I think that it should be reviewed by someone with
a better understanding of what's going on, and as these issues are
simple, I reasoned that it would be just as easy for such a person
to just fix the code... I did fix all these issues in my own
installation (again, except #9827, which I took care of in a different
way), so if you think my 1-line patches that I'm not very confident
about are going to help move things along, I can produce them.

  olegos


Siebrand Mazeland wrote:
> I checked out the four issues you mentioned. Even though you are the
> reporter, and state that the issues "all have simple fixes" you have not
> attached a patch on trunk for any of these issues, which would make it a
> magnitude easier to get them resolved. I admire your aspirations, and
share
> them, but please realise that everyone working on Mantis is a volunteer.
As
> soon as we start to get funding, priotities may shift - until them it is
> mostly fun for people to work on, and all open source projects need all
the
> help they can get - yours too. P.s. it is possible to pledge a certain sum
> of monery for getting issues fixed in our bug tracker.
> 
> Oh, another thing: As with beauty, simplicity is in the eye of the
> beholder.


----------------------------------------------------------------------------
--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
mantisbt-dev mailing list
man...@li...
https://lists.sourceforge.net/lists/listinfo/mantisbt-dev