The release has been published to the Maven Central repo [1] and to the
Apache Distribution repo [2].  There is a new tag for 2.5.0-beta5 in JIRA.
 I will send out a release email tomorrow so everything have a chance to
sync across all the mirrors.

[1]
https://repository.apache.org/content/repositories/releases/org/apache/shindig/
[2] https://dist.apache.org/repos/dist/release/shindig/2.5.0-beta4/

-Ryan

On Sun, Sep 9, 2012 at 5:09 PM, Ryan Baxter <[email protected]> wrote:

> +1 from me as well I will start publishing the release.
>
>
> On Sun, Sep 9, 2012 at 4:42 PM, Ryan Baxter <[email protected]> wrote:
>
>> Thanks guys!
>>
>> This query should be better:
>>
>> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+SHINDIG+AND+resolution+%3D+Fixed+AND+status+in+%28Resolved%2C+Closed%29+AND+resolved+%3E%3D+2012-07-31+AND+resolved+%3C%3D+2012-08-30
>>
>>
>> On Sat, Sep 8, 2012 at 9:53 AM, Stanton Sievers <[email protected]>wrote:
>>
>>> +1 from me.
>>>
>>> Ryan, it looks like your query is picking up 3 JIRAs that were fixed
>>> post-beta4.  1859, 1861, 1865.
>>>
>>> On Fri, Sep 7, 2012 at 6:32 PM, Henry Saputra <[email protected]
>>> >wrote:
>>>
>>> > +1 for common, gadget, features, social-api artifacts
>>> > +1 for signatures of the execution binaries (I didnt check the doc and
>>> > sources)
>>> >
>>> > So +1 from me.
>>> >
>>> > - Henry
>>> >
>>> > On Thu, Aug 30, 2012 at 5:33 AM, Ryan Baxter <[email protected]>
>>> wrote:
>>> > > Hi, it is that time of the month again, time for a release.
>>> > >
>>> > > We solved 9 issues:
>>> > >
>>> >
>>> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+SHINDIG+AND+resolution+%3D+Fixed+AND+status+in+%28Resolved%2C+Closed%29+AND+resolved+%3E%3D+2012-07-31
>>> > >
>>> > >
>>> > > Staging repo:
>>> > >
>>> https://repository.apache.org/content/repositories/orgapacheshindig-023/
>>> > >
>>> > >
>>> > > Vote open for 72 hours.
>>> > >
>>> > > [ ] +1
>>> > > [ ] +0
>>> > > [ ] -1
>>> >
>>>
>>
>>
>

Reply via email to