With the recent announcement of google code to shut down their public API I see
a major functionality gone for our project.
https://code.google.com/p/support/wiki/IssueTrackerAPI
I would like to extend the functionality of our monkey, so it will become more
intelligent:
- give co
On 8 February 2013 19:51, Camillo Bruni wrote:
> With the recent announcement of google code to shut down their public API I
> see
> a major functionality gone for our project.
>
> https://code.google.com/p/support/wiki/IssueTrackerAPI
>
> I would like to extend the functionality of our m
I would go for GitHub, its exposition is really good for the project.
But if file attachments (other than pictures) is a showstopper, then...
I would suggest:
* Mantis (PHP Based, but with a SOAP API) http://mantisbt.org/
We've been using it in our company since 7 years ago, and it has
proven to b
On 2013-02-08, at 21:19, Frank Shearar wrote:
> On 8 February 2013 19:51, Camillo Bruni wrote:
>> With the recent announcement of google code to shut down their public API I
>> see
>> a major functionality gone for our project.
>>
>>https://code.google.com/p/support/wiki/IssueTrackerA
On 2013-02-08, at 21:23, "Esteban A. Maringolo" wrote:
> I would go for GitHub, its exposition is really good for the project.
> But if file attachments (other than pictures) is a showstopper, then...
it is a show-stopper for now. A future development cycle might solve this, but
I don't want to
On Feb 8, 2013, at 9:47 PM, Camillo Bruni wrote:
>
> On 2013-02-08, at 21:23, "Esteban A. Maringolo" wrote:
>
>> I would go for GitHub, its exposition is really good for the project.
>> But if file attachments (other than pictures) is a showstopper, then...
>
> it is a show-stopper for now. A
(regarding Mantis)
2013/2/8 Stéphane Ducasse :
> we used it for squeak and I never liked it.
It is ugly as it gets, I don't like its appearance either. I won't
argue on that :)
But it is reliable, flexible and full of features.
We talked about migrating to JIRA, but we have ~12000 issues tracke
On 2013-02-08, at 21:58, "Esteban A. Maringolo" wrote:
> (regarding Mantis)
>
> 2013/2/8 Stéphane Ducasse :
>> we used it for squeak and I never liked it.
>
> It is ugly as it gets, I don't like its appearance either. I won't
> argue on that :)
>
> But it is reliable, flexible and full of fea
On Fri, Feb 8, 2013, at 04:04 PM, Camillo Bruni wrote:
>
> On 2013-02-08, at 21:58, "Esteban A. Maringolo"
> wrote:
>
> > (regarding Mantis)
> >
> > 2013/2/8 Stéphane Ducasse :
> >> we used it for squeak and I never liked it.
> >
> > It is ugly as it gets, I don't like its appearance either. I
On 2013-02-08, at 22:10, Benjamin Pollack wrote:
> On Fri, Feb 8, 2013, at 04:04 PM, Camillo Bruni wrote:
>>
>> On 2013-02-08, at 21:58, "Esteban A. Maringolo"
>> wrote:
>>
>>> (regarding Mantis)
>>>
>>> 2013/2/8 Stéphane Ducasse :
we used it for squeak and I never liked it.
>>>
>>> It
On Feb 8, 2013, at 10:00 PM, Esteban A. Maringolo wrote:
> (regarding Mantis)
>
> 2013/2/8 Stéphane Ducasse :
>> we used it for squeak and I never liked it.
>
> It is ugly as it gets, I don't like its appearance either. I won't
> argue on that :)
>
> But it is reliable, flexible and full of f
On Fri, Feb 8, 2013 at 2:22 PM, Marcus Denker wrote:
>
> On Feb 8, 2013, at 10:00 PM, Esteban A. Maringolo
> wrote:
>
> > (regarding Mantis)
> >
> > 2013/2/8 Stéphane Ducasse :
> >> we used it for squeak and I never liked it.
> >
> > It is ugly as it gets, I don't like its appearance either. I wo
On 2013-02-08, at 23:30, Eliot Miranda wrote:
> On Fri, Feb 8, 2013 at 2:22 PM, Marcus Denker wrote:
>
>>
>> On Feb 8, 2013, at 10:00 PM, Esteban A. Maringolo
>> wrote:
>>
>>> (regarding Mantis)
>>>
>>> 2013/2/8 Stéphane Ducasse :
we used it for squeak and I never liked it.
>>>
>>> It
On Feb 8, 2013, at 10:10 PM, Benjamin Pollack wrote:
>
>
> Fog Creek would be happy to provide all of you with a free FogBugz On
> Demand account. It has a good API, it has file attachments, it has
> custom workflows, triggers, and plugins, and we're about to release a
> version that's Gmail-l
On Feb 8, 2013, at 11:34 PM, Camillo Bruni wrote:
>>>
>>
>> That's not a valid comparison. In Squeak trunk bugs are getting fixed at a
>> much higher rate
Are you sure? The list that Craig showed at Fosdem was rather short.
Marcus
On Fri, Feb 8, 2013 at 2:41 PM, Marcus Denker wrote:
>
> On Feb 8, 2013, at 11:34 PM, Camillo Bruni wrote:
>
> >>>
> >>
> >> That's not a valid comparison. In Squeak trunk bugs are getting fixed
> at a
> >> much higher rate
>
> Are you sure? The list that Craig showed at Fosdem was rather short.
On 8 February 2013 22:41, Marcus Denker wrote:
>
> On Feb 8, 2013, at 11:34 PM, Camillo Bruni wrote:
>
>>>
>>> That's not a valid comparison. In Squeak trunk bugs are getting fixed at a
>>> much higher rate
>
> Are you sure? The list that Craig showed at Fosdem was rather short.
Well, obvi
On Feb 8, 2013, at 11:49 PM, Frank Shearar wrote:
> On 8 February 2013 22:41, Marcus Denker wrote:
>>
>> On Feb 8, 2013, at 11:34 PM, Camillo Bruni wrote:
>>
>
That's not a valid comparison. In Squeak trunk bugs are getting fixed at a
much higher rate
>>
>> Are you sur
On 08 Feb 2013, at 22:10, Benjamin Pollack wrote:
> On Fri, Feb 8, 2013, at 04:04 PM, Camillo Bruni wrote:
>>
>> On 2013-02-08, at 21:58, "Esteban A. Maringolo"
>> wrote:
>>
>>> (regarding Mantis)
>>>
>>> 2013/2/8 Stéphane Ducasse :
we used it for squeak and I never liked it.
>>>
>>> I
On 8 February 2013 22:51, Marcus Denker wrote:
>
> On Feb 8, 2013, at 11:49 PM, Frank Shearar wrote:
>
>> On 8 February 2013 22:41, Marcus Denker wrote:
>>>
>>> On Feb 8, 2013, at 11:34 PM, Camillo Bruni wrote:
>>>
>>
>
> That's not a valid comparison. In Squeak trunk bugs are gett
On Feb 8, 2013, at 11:59 PM, Sven Van Caekenberghe wrote:
>>
>> Fog Creek would be happy to provide all of you with a free FogBugz On
>> Demand account. It has a good API, it has file attachments, it has
>> custom workflows, triggers, and plugins, and we're about to release a
>> version that's
On Feb 9, 2013, at 12:01 AM, Frank Shearar wrote:
> On 8 February 2013 22:51, Marcus Denker wrote:
>>
>> On Feb 8, 2013, at 11:49 PM, Frank Shearar wrote:
>>
>>> On 8 February 2013 22:41, Marcus Denker wrote:
On Feb 8, 2013, at 11:34 PM, Camillo Bruni wrote:
>>>
>
I wanna play too :)
Ben
On Feb 9, 2013, at 12:05 AM, Marcus Denker wrote:
>
> On Feb 8, 2013, at 11:59 PM, Sven Van Caekenberghe wrote:
>>>
>>> Fog Creek would be happy to provide all of you with a free FogBugz On
>>> Demand account. It has a good API, it has file attachments, it has
>>> cu
in you are... ;)
On 2013-02-09, at 00:12, Benjamin wrote:
> I wanna play too :)
>
> Ben
>
> On Feb 9, 2013, at 12:05 AM, Marcus Denker wrote:
>
>>
>> On Feb 8, 2013, at 11:59 PM, Sven Van Caekenberghe wrote:
Fog Creek would be happy to provide all of you with a free FogBugz On
>
On Fri, Feb 8, 2013, at 06:14 PM, Camillo Bruni wrote:
> in you are... ;)
>
> On 2013-02-09, at 00:12, Benjamin
> wrote:
>
> > I wanna play too :)
> >
> > Ben
> >
> > On Feb 9, 2013, at 12:05 AM, Marcus Denker wrote:
> >
> >>
> >> On Feb 8, 2013, at 11:59 PM, Sven Van Caekenberghe wrote:
>
On 2013-02-09, at 00:24, Benjamin Pollack wrote:
> On Fri, Feb 8, 2013, at 06:14 PM, Camillo Bruni wrote:
>> in you are... ;)
>>
>> On 2013-02-09, at 00:12, Benjamin
>> wrote:
>>
>>> I wanna play too :)
>>>
>>> Ben
>>>
>>> On Feb 9, 2013, at 12:05 AM, Marcus Denker wrote:
>>>
O
I think we can all say a big thank you :)
Ben
On Feb 9, 2013, at 12:27 AM, Camillo Bruni wrote:
>
> On 2013-02-09, at 00:24, Benjamin Pollack wrote:
>
>> On Fri, Feb 8, 2013, at 06:14 PM, Camillo Bruni wrote:
>>> in you are... ;)
>>>
>>> On 2013-02-09, at 00:12, Benjamin
>>> wrote:
>>>
>>
On Fri, Feb 8, 2013 at 3:10 PM, Marcus Denker wrote:
>
> On Feb 9, 2013, at 12:01 AM, Frank Shearar
> wrote:
>
> > On 8 February 2013 22:51, Marcus Denker wrote:
> >>
> >> On Feb 8, 2013, at 11:49 PM, Frank Shearar
> wrote:
> >>
> >>> On 8 February 2013 22:41, Marcus Denker
> wrote:
>
> >
On Feb 9, 2013, at 1:06 AM, Eliot Miranda wrote:
>
>
> On Fri, Feb 8, 2013 at 3:10 PM, Marcus Denker wrote:
>
> On Feb 9, 2013, at 12:01 AM, Frank Shearar wrote:
>
> > On 8 February 2013 22:51, Marcus Denker wrote:
> >>
> >> On Feb 8, 2013, at 11:49 PM, Frank Shearar wrote:
> >>
> >>> On
Hi Ben,
please include the squeak list in this discussion It's clearly
relevant to the whole community.
On Fri, Feb 8, 2013 at 4:12 PM, Benjamin <
benjamin.vanryseghem.ph...@gmail.com> wrote:
>
> On Feb 9, 2013, at 1:06 AM, Eliot Miranda wrote:
>
>
>
> On Fri, Feb 8, 2013 at 3:10 PM, Marcu
Hi--
Eliot writes:
> That's not a valid comparison. In Squeak trunk bugs are getting
> fixed at a much higher rate
Marcus responds:
> Are you sure? The list that Craig showed at Fosdem was rather short.
Hey, I only showed the usual short list of highlights from the
Squeak 4.4
On Fri, Feb 8, 2013 at 11:49 PM, Frank Shearar wrote:
>
> Well, obviously Squeak is a rather smaller community, so that's hardly
> surprising.
>
What is cause and what is effect?
--
Marcus Denker -- den...@acm.org
http://www.marcusdenker.de
Benjamin Van Ryseghem-2 wrote
> I think we can all say a big thank you :)
Yes, thank you for this amazing gift :)
--
View this message in context:
http://forum.world.st/New-Issue-Tracker-tp4668700p4668799.html
Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
On 9 February 2013 00:40, Marcus Denker wrote:
> On Fri, Feb 8, 2013 at 11:49 PM, Frank Shearar
> wrote:
>
>>
>> Well, obviously Squeak is a rather smaller community, so that's hardly
>> surprising.
>>
>
> What is cause and what is effect?
I'm not going to dig up old history. It's clearly painf
thanks a lot ben.
I'm busy migrating on 10.7 to 10.8 on a new machine and bumping into well….
glitches :)
I will sync with the team monday.
Stef
On Feb 9, 2013, at 12:24 AM, Benjamin Pollack wrote:
> On Fri, Feb 8, 2013, at 06:14 PM, Camillo Bruni wrote:
>> in you are... ;)
>>
>> On 2013-02-0
Hello.
FYI, Redmine is a rewrite in Ruby of Trac (programmed in Python), with
several improvements. Later, some developers from Redmine made a fork of it
named ChiliProject, to go more faster in development. I recommend
ChiliProject over Redmine. ChiliProject have all characteristics that you
list
Attachment using Rest Api (and linking it to a new or previously existing
issue):
http://www.redmine.org/projects/redmine/wiki/Rest_api#Attaching-files
ChiliProject have a powerfull wiki syntax (usable too in issues, news,
message commits shown in repository view), with use TextTile and CodeRay:
h
On Sat, Feb 9, 2013, at 12:47 PM, stephane ducasse wrote:
> thanks a lot ben.
> I'm busy migrating on 10.7 to 10.8 on a new machine and bumping into
> well…. glitches :)
> I will sync with the team monday.
Good timing! The FogBugz team rolled pharo.fogbugz.com over to the beta
this morning. Each
Is there a way to have public access to issues?
I mean, read only access to see the backlog of issues, what's being done, etc.
With FogBugz all I see at pharo.fogbugz.com is a login page, whilst
with Google Issue Tracking I was able to see the milestones, etc.
Regards!
Esteban A. Maringolo
201
On 2013-02-11, at 16:47, Benjamin Pollack wrote:
> On Sat, Feb 9, 2013, at 12:47 PM, stephane ducasse wrote:
>> thanks a lot ben.
>> I'm busy migrating on 10.7 to 10.8 on a new machine and bumping into
>> well…. glitches :)
>> I will sync with the team monday.
>
> Good timing! The FogBugz team
On Feb 11, 2013, at 8:21 PM, Camillo Bruni wrote:
>
> On 2013-02-11, at 16:47, Benjamin Pollack wrote:
>
>> On Sat, Feb 9, 2013, at 12:47 PM, stephane ducasse wrote:
>>> thanks a lot ben.
>>> I'm busy migrating on 10.7 to 10.8 on a new machine and bumping into
>>> well…. glitches :)
>>> I wil
On Feb 11, 2013, at 4:59 PM, Esteban A. Maringolo wrote:
> Is there a way to have public access to issues?
> I mean, read only access to see the backlog of issues, what's being done, etc.
>
> With FogBugz all I see at pharo.fogbugz.com is a login page, whilst
> with Google Issue Tracking I was
After a discussion with Christophe which is in favor of JIRA ;) we decided to
put a
wiki page online where we should list all the requirements (not just the ones I
think
are important :P)
https://code.google.com/p/pharo/wiki/NewIssueTracker
I really don't like JIRA, I find it bloated, and I always lose myself
there. IMHO FogBugs seems *a lot* nicer to use.
Nico
Camillo Bruni writes:
> After a discussion with Christophe which is in favor of JIRA ;) we decided to
> put a
> wiki page online where we should list all the requirements
Hi all,
I quickly developed a basic importer (Google code => Jira) so that everyone
can play a bit with real data.
There is still a lot of missing stuff that we can import (ex: labels, author)
but I will only do that once we agree on the new bugtracker to choose.
So, we have a free Jira instan
thanks christophe :)
For me this would be ok.
Is there an API for scripting it?
Stef
> Hi all,
>
> I quickly developed a basic importer (Google code => Jira) so that everyone
> can play a bit with real data.
> There is still a lot of missing stuff that we can import (ex: labels, author)
> but
On Feb 20, 2013, at 8:16 PM, stephane ducasse wrote:
> thanks christophe :)
> For me this would be ok.
I still have a preference for fogbugz :)
> Is there an API for scripting it?
There is one but not yet implemented in Pharo :) (contrary to FogBugz ^^)
We ask people from the mailing to expr
Fogbugz is cool and for sure more fully featured.
But I do meet Jira more often in the field (about 80% of my clients
use that thing for better or worse).
But if we talk about such things, then let's have a look at Fossil. At
least, it is FOSS software.
Phil
2013/2/20 Benjamin :
> On Feb 20, 2
I'm unclear about how to change issue statuses in certain cases. For example,
https://pharo.fogbugz.com/default.asp?10178 has been integrated, but it's
still listed as "Fix to include". However, when I click "edit" there doesn't
seem to be a drop-down to change the status, and if I "reopen", I only
Because the current status is Fix To Include, but the current state is Closed
Basically you have 3 states (open, resolved, closed)
And when you go from Resolved to CLosed, the status is kept
Ben
On Mar 30, 2013, at 10:16 PM, "Sean P. DeNigris" wrote:
> I'm unclear about how to change issue stat
Benjamin Van Ryseghem-2 wrote
> And when you go from Resolved to CLosed, the status is kept
Okay, so we have to mark as integrated before closing, and if not, it has to
be reopened, then resolved, then marked integrated, and then closed again :)
-
Cheers,
Sean
--
View this message in contex
the thing is that we use to mix two steps in one with the previous issue
tracker.
The workflow is:
work needed (open) -> review needed (resolved) -> fix to include (resolved) ->
integrated (resolved) and here and only here, once it's integrated, you can
close the issue
:)
Ben
On Mar 31, 2013
52 matches
Mail list logo
