[
https://issues.apache.org/jira/browse/CLEREZZA-509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033014#comment-13033014
]
Reto Bachmann-Gmür commented on CLEREZZA-509:
---------------------------------------------
please explain why? Consider the problems if there is a -1 on an issue (which
can come till 3 days after closing an means the changes have to be rolled back)
and the resolution of other issues already depend on what has to be rolled
back. If you come with another consistent process proposal please discuss it
on the mailing list.
The policy at the beginning was stricter where we only resolved an issue while
it was till in an issue branch and only when the reviewer closed it got merged
into trunk. I think it's good to have more flexibility, but we must make sure
the code in the trunk satisfies some quality standards, one of them is that you
can follow back to the motivating issue for every commit.
> enable pingback protocol
> ------------------------
>
> Key: CLEREZZA-509
> URL: https://issues.apache.org/jira/browse/CLEREZZA-509
> Project: Clerezza
> Issue Type: New Feature
> Reporter: Henry Story
> Assignee: Henry Story
>
> The Pingback protocol is an extreemly simple version of the XMLRPC pingback
> protocol that was used to notify people of changes in blogs. Pingback is an
> improvement in that it is
> - RESTful
> - uses simple forms
> (and a tiny bit of rdf)
> http://www.w3.org/wiki/Pingback
> This can be used to ping people when you have added them as friends without
> them needing to publish their email addresses.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
