Automating issue tracker update when a package is published

I know what I gonna hear, www.squeasource.com is already overloaded
and we can't,
but it would be super-nice if the Pharo issue tracker were updated
automagically when a slice is commited in the inbox.

Nicolas

On 22.03.2011 22:41, Nicolas Cellier wrote:
> I know what I gonna hear, www.squeasource.com is already overloaded
> and we can't,
> but it would be super-nice if the Pharo issue tracker were updated
> automagically when a slice is commited in the inbox.
>
> Nicolas
>
http://code.google.com/p/support/wiki/IssueTrackerAPI
I guess we at least need working SSL + some labour first :)

Cheers,
Henry

On 22 March 2011 22:41, Nicolas Cellier
<[hidden email]> wrote:
> I know what I gonna hear, www.squeasource.com is already overloaded
> and we can't,
> but it would be super-nice if the Pharo issue tracker were updated
> automagically when a slice is commited in the inbox.
>
Good idea :)

No need to put that load to squeaksource.com
SqS could just send regular emails to special [hidden email],
where you have a bot which parses incoming mail and do some extra
processing like one proposed by you.


> Nicolas
>
>



--
Best regards,
Igor Stasenko AKA sig.

this would be sooooo cooooool

Stef

On Mar 22, 2011, at 10:41 PM, Nicolas Cellier wrote:

> I know what I gonna hear, www.squeasource.com is already overloaded
> and we can't,
> but it would be super-nice if the Pharo issue tracker were updated
> automagically when a slice is commited in the inbox.
>
> Nicolas
>