<html><body><div>I'm all for going to bb for issues and enhancement reqs.<div><br><br><span style="font-size:87%">- tim <br><br>(Sent from an Androd that dosnt autocorect as wel as an ipone) </span> </div><br><br><br>-------- Original message --------<br>Subject: Re: [MOAB-dev] Use of issues on BitBucket <br>From: "Vijay S. Mahadevan" <vijay.m@gmail.com> <br>To: Iulian Grindeanu <iulian@mcs.anl.gov> <br>CC: Andrew Davis <davisa@engr.wisc.edu>,moab-dev@mcs.anl.gov <br><br><br></div><br><div>Andrew, +1.
I think this BitBucket feature would be very useful for all the bug
reports and to track the progress of the corresponding fixes. Having
different email threads in the list for reporting bugs is intractable
in the longer run when the number of users increase. Feature
additions can be placed here too and there is a separate enhancement
tag applied to differentiate from bug reports.
Iulian, we should probably move the outstanding bugs in the trac page
and create tickets for them in fathom bitbucket repo. No point having
the same feature in two different places. Issues list are best placed
at the repo site.
Vijay
On Thu, Jun 20, 2013 at 1:08 PM, Iulian Grindeanu <iulian@mcs.anl.gov> wrote:
> Hello,
> We do not use yet bitbucket for that.
> the issues/tickets are still on the trac site
> http://trac.mcs.anl.gov/projects/ITAPS/wiki/MOAB
>
> We also have a confluence page (internal) for discussions. Confluence is
> offered by the same company (atlassian), as bitbucket
>
> I think we will move eventually to bitbucket
>
> Iulian
> ________________________________
>
> Hi
>
> Quick question regarding the use of issues on BitBucket, do we plan to use
> or not use this to track bugs and development goals?
>
> Thanks
>
> Andrew
>
>
</div></body></html>