You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by "Davies,Douglas" <da...@oclc.org> on 2014/11/07 15:26:30 UTC
2.5.2 release?
It's been about 8 months since the last release. I see there are only about 6 out of the 25 tickets that have been resolved for 2.5.2. What is the roadmap for releasing 2.5.2? Is it determined by timeframe or bugs fixed? I have a patch I contributed that we'd really like to get into our project, but I don't want to cause anyone unnecessary time to do a build if it's not time.
Thanks,
Doug
Re: 2.5.2 release?
Posted by "Davies,Douglas" <da...@oclc.org>.
Thanks Ryan!
On Nov 10, 2014, at 9:43 AM, Ryan Baxter <rb...@gmail.com> wrote:
> I have no problem doing a release whenever. The problem is always
> trying to find some time to do them ;) I will try to kick one off
> this week.
>
> On Sat, Nov 8, 2014 at 12:26 PM, Stanton Sievers <ss...@apache.org> wrote:
>> Hi Doug,
>>
>> There's no set time frame on the 2.5.2 release. If we think there are
>> enough fixed items to warrant a release then it's worth discussing. As you
>> mentioned, there are 6 items fixed in 2.5.2 right now [1].
>>
>> Personally, I think the mindset should be if we are in doubt whether or not
>> it's time to cut a release then cut a release. It doesn't hurt to get
>> fixes out there, IMO.
>>
>> What does everyone else think?
>>
>> Thanks,
>> -Stanton
>>
>> [1]
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SHINDIG%20AND%20fixVersion%20%3D%202.5.2%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20priority%20DESC
>>
>> On Fri, Nov 7, 2014 at 9:26 AM, Davies,Douglas <da...@oclc.org> wrote:
>>
>>> It's been about 8 months since the last release. I see there are only
>>> about 6 out of the 25 tickets that have been resolved for 2.5.2. What is
>>> the roadmap for releasing 2.5.2? Is it determined by timeframe or bugs
>>> fixed? I have a patch I contributed that we'd really like to get into our
>>> project, but I don't want to cause anyone unnecessary time to do a build if
>>> it's not time.
>>>
>>> Thanks,
>>> Doug
>>>
AW: 2.5.2 release?
Posted by René Peinl <re...@hof-university.de>.
Would this be a good time to include our neo4j patch?
https://issues.apache.org/jira/browse/SHINDIG-1911
https://reviews.apache.org/r/9773/
-----Ursprüngliche Nachricht-----
Von: Ryan Baxter [mailto:rbaxter85@gmail.com]
Gesendet: Montag, 10. November 2014 15:44
An: dev@shindig.apache.org
Betreff: Re: 2.5.2 release?
I have no problem doing a release whenever. The problem is always trying to find some time to do them ;) I will try to kick one off this week.
On Sat, Nov 8, 2014 at 12:26 PM, Stanton Sievers <ss...@apache.org> wrote:
> Hi Doug,
>
> There's no set time frame on the 2.5.2 release. If we think there are
> enough fixed items to warrant a release then it's worth discussing.
> As you mentioned, there are 6 items fixed in 2.5.2 right now [1].
>
> Personally, I think the mindset should be if we are in doubt whether
> or not it's time to cut a release then cut a release. It doesn't hurt
> to get fixes out there, IMO.
>
> What does everyone else think?
>
> Thanks,
> -Stanton
>
> [1]
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SHINDIG%20A
> ND%20fixVersion%20%3D%202.5.2%20AND%20status%20%3D%20Resolved%20ORDER%
> 20BY%20priority%20DESC
>
> On Fri, Nov 7, 2014 at 9:26 AM, Davies,Douglas <da...@oclc.org> wrote:
>
>> It's been about 8 months since the last release. I see there are
>> only about 6 out of the 25 tickets that have been resolved for 2.5.2.
>> What is the roadmap for releasing 2.5.2? Is it determined by
>> timeframe or bugs fixed? I have a patch I contributed that we'd
>> really like to get into our project, but I don't want to cause anyone
>> unnecessary time to do a build if it's not time.
>>
>> Thanks,
>> Doug
>>
Re: 2.5.2 release?
Posted by Ryan Baxter <rb...@gmail.com>.
I have no problem doing a release whenever. The problem is always
trying to find some time to do them ;) I will try to kick one off
this week.
On Sat, Nov 8, 2014 at 12:26 PM, Stanton Sievers <ss...@apache.org> wrote:
> Hi Doug,
>
> There's no set time frame on the 2.5.2 release. If we think there are
> enough fixed items to warrant a release then it's worth discussing. As you
> mentioned, there are 6 items fixed in 2.5.2 right now [1].
>
> Personally, I think the mindset should be if we are in doubt whether or not
> it's time to cut a release then cut a release. It doesn't hurt to get
> fixes out there, IMO.
>
> What does everyone else think?
>
> Thanks,
> -Stanton
>
> [1]
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SHINDIG%20AND%20fixVersion%20%3D%202.5.2%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20priority%20DESC
>
> On Fri, Nov 7, 2014 at 9:26 AM, Davies,Douglas <da...@oclc.org> wrote:
>
>> It's been about 8 months since the last release. I see there are only
>> about 6 out of the 25 tickets that have been resolved for 2.5.2. What is
>> the roadmap for releasing 2.5.2? Is it determined by timeframe or bugs
>> fixed? I have a patch I contributed that we'd really like to get into our
>> project, but I don't want to cause anyone unnecessary time to do a build if
>> it's not time.
>>
>> Thanks,
>> Doug
>>
Re: 2.5.2 release?
Posted by Stanton Sievers <ss...@apache.org>.
Hi Doug,
There's no set time frame on the 2.5.2 release. If we think there are
enough fixed items to warrant a release then it's worth discussing. As you
mentioned, there are 6 items fixed in 2.5.2 right now [1].
Personally, I think the mindset should be if we are in doubt whether or not
it's time to cut a release then cut a release. It doesn't hurt to get
fixes out there, IMO.
What does everyone else think?
Thanks,
-Stanton
[1]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20SHINDIG%20AND%20fixVersion%20%3D%202.5.2%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20priority%20DESC
On Fri, Nov 7, 2014 at 9:26 AM, Davies,Douglas <da...@oclc.org> wrote:
> It's been about 8 months since the last release. I see there are only
> about 6 out of the 25 tickets that have been resolved for 2.5.2. What is
> the roadmap for releasing 2.5.2? Is it determined by timeframe or bugs
> fixed? I have a patch I contributed that we'd really like to get into our
> project, but I don't want to cause anyone unnecessary time to do a build if
> it's not time.
>
> Thanks,
> Doug
>