You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bloodhound.apache.org by Greg Stein <gs...@gmail.com> on 2012/09/22 03:26:27 UTC
Re: [VOTE] Release Apache Bloodhound 0.1.0 (incubating) (RC1)
It's been about 8 weeks... time to stop fixing, and start rolling?
Cheers,
-g
ps. once it was announced, we've seen some new interest! round two? :-)
On Jul 25, 2012 1:19 PM, "Gary Martin" <ga...@wandisco.com> wrote:
> Hi everyone,
>
> I hope that this is not premature but as the conversation on the related
> [PROPOSAL] thread has died down, I would like to initiate the vote for
> releasing Apache Bloodhound 0.1.0 (incubating). If successful this will be
> the first release of the project and is an important step that I hope will
> generate interest in the project and help the community to grow.
>
> The release candidate this vote relates to provides:
>
> * A patched version of Trac
> * A new dashboard view with the dashboard style unifying views of
> tickets, milestones and the user's dashboard.
> * A re-theming of the interface to use bootstrap
> * Preliminary multi-product support as a step towards allowing the
> tracking of multiple distinct products (or projects) in a single
> environment
> * Simplified installation with the inclusion of a number of plugins as
> standard.
>
> As an initial release, of particular importance is that we have taken
> proper notice of licensing of code produced as part of this project and the
> proper acknowledgement of external work packaged with it.
>
> The release candidate artifacts consist of source release as a tar.gz
> archive along with the associated MD5 and GPG signature. These can be found
> at: https://dist.apache.org/repos/**dist/dev/incubator/bloodhound/<https://dist.apache.org/repos/dist/dev/incubator/bloodhound/>
>
> Please vote:
> [ ] +1 Release this package as Apache Bloodhound 0.1.0
> [ ] +0 Don't care
> [ ] -1 Do not release this package (please explain)
>
> The vote is open for 72 hours and, if successful, will be followed by a
> vote on general@incubator for a further 72 hours.
>
Re: [VOTE] Release Apache Bloodhound 0.1.0 (incubating) (RC1)
Posted by Greg Stein <gs...@gmail.com>.
Anybody with commit access can be an RM. People on the PPMC will vote on
their results.
Cheers,
-g
On Sep 24, 2012 5:21 AM, "Gary Martin" <ga...@wandisco.com> wrote:
> I agree too. I will check for anything that is obviously blocking though.
> Would anyone consider volunteering for release manager duties this time
> (Bloodhound PPMC member only I believe).
>
> Cheers,
> Gary
>
>
> On 09/23/2012 02:39 PM, Joe Dreimann wrote:
>
>> I'm with Greg on this. We should release every month in my opinion.
>>
>> - Joe
>>
>> ________________________
>> @jdreimann - Twitter
>> Sent from my phone
>>
>> On 23 Sep 2012, at 07:29, Greg Stein <gs...@gmail.com> wrote:
>>
>> On Sep 23, 2012 12:05 AM, "Olemis Lang" <ol...@gmail.com> wrote:
>>>
>>>> On 9/21/12, Greg Stein <gs...@gmail.com> wrote:
>>>>
>>>>> It's been about 8 weeks... time to stop fixing, and start rolling?
>>>>>
>>>> There are some patches in the issue tracker , pending for commit .
>>>> Especially these tickets I consider important as they add some value
>>>> to what we shall propose , mainly regarding the UI .
>>>>
>>>> #203 , #53 , #138 , #139 , #201 , #45 , #174
>>>>
>>>> Beyond that , maybe we can postpone #146 and other tickets scheduled
>>>> for Release 2 , yet pending , for a forthcoming 0.2.1 , 0.3.0 , ...
>>>> whatever other release number it might be .
>>>>
>>> There are always future releases. IMO, no problem pushing changes out to
>>> the next one. This new release is better than the last, so you're in good
>>> shape.
>>>
>>> Further, if those patches in the tickets have not yet been applied, then
>>> maybe it is because they need some review, some testing, or whatever.
>>> They
>>> haven't (yet) been applied for some reason... so why delay further to
>>> wait
>>> for those reasons to be resolved? They'll hopefully be applied for the
>>> next-next release.
>>>
>>> (another happy benefit would be clearing out the IPMC concerns from the
>>> last release)
>>>
>>> Cheers,
>>> -g
>>>
>>
>
Re: [VOTE] Release Apache Bloodhound 0.1.0 (incubating) (RC1)
Posted by Gary Martin <ga...@wandisco.com>.
I agree too. I will check for anything that is obviously blocking
though. Would anyone consider volunteering for release manager duties
this time (Bloodhound PPMC member only I believe).
Cheers,
Gary
On 09/23/2012 02:39 PM, Joe Dreimann wrote:
> I'm with Greg on this. We should release every month in my opinion.
>
> - Joe
>
> ________________________
> @jdreimann - Twitter
> Sent from my phone
>
> On 23 Sep 2012, at 07:29, Greg Stein <gs...@gmail.com> wrote:
>
>> On Sep 23, 2012 12:05 AM, "Olemis Lang" <ol...@gmail.com> wrote:
>>> On 9/21/12, Greg Stein <gs...@gmail.com> wrote:
>>>> It's been about 8 weeks... time to stop fixing, and start rolling?
>>> There are some patches in the issue tracker , pending for commit .
>>> Especially these tickets I consider important as they add some value
>>> to what we shall propose , mainly regarding the UI .
>>>
>>> #203 , #53 , #138 , #139 , #201 , #45 , #174
>>>
>>> Beyond that , maybe we can postpone #146 and other tickets scheduled
>>> for Release 2 , yet pending , for a forthcoming 0.2.1 , 0.3.0 , ...
>>> whatever other release number it might be .
>> There are always future releases. IMO, no problem pushing changes out to
>> the next one. This new release is better than the last, so you're in good
>> shape.
>>
>> Further, if those patches in the tickets have not yet been applied, then
>> maybe it is because they need some review, some testing, or whatever. They
>> haven't (yet) been applied for some reason... so why delay further to wait
>> for those reasons to be resolved? They'll hopefully be applied for the
>> next-next release.
>>
>> (another happy benefit would be clearing out the IPMC concerns from the
>> last release)
>>
>> Cheers,
>> -g
Re: [VOTE] Release Apache Bloodhound 0.1.0 (incubating) (RC1)
Posted by Joe Dreimann <jo...@wandisco.com>.
I'm with Greg on this. We should release every month in my opinion.
- Joe
________________________
@jdreimann - Twitter
Sent from my phone
On 23 Sep 2012, at 07:29, Greg Stein <gs...@gmail.com> wrote:
> On Sep 23, 2012 12:05 AM, "Olemis Lang" <ol...@gmail.com> wrote:
>>
>> On 9/21/12, Greg Stein <gs...@gmail.com> wrote:
>>> It's been about 8 weeks... time to stop fixing, and start rolling?
>>
>> There are some patches in the issue tracker , pending for commit .
>> Especially these tickets I consider important as they add some value
>> to what we shall propose , mainly regarding the UI .
>>
>> #203 , #53 , #138 , #139 , #201 , #45 , #174
>>
>> Beyond that , maybe we can postpone #146 and other tickets scheduled
>> for Release 2 , yet pending , for a forthcoming 0.2.1 , 0.3.0 , ...
>> whatever other release number it might be .
>
> There are always future releases. IMO, no problem pushing changes out to
> the next one. This new release is better than the last, so you're in good
> shape.
>
> Further, if those patches in the tickets have not yet been applied, then
> maybe it is because they need some review, some testing, or whatever. They
> haven't (yet) been applied for some reason... so why delay further to wait
> for those reasons to be resolved? They'll hopefully be applied for the
> next-next release.
>
> (another happy benefit would be clearing out the IPMC concerns from the
> last release)
>
> Cheers,
> -g
Re: [VOTE] Release Apache Bloodhound 0.1.0 (incubating) (RC1)
Posted by Greg Stein <gs...@gmail.com>.
On Sep 23, 2012 12:05 AM, "Olemis Lang" <ol...@gmail.com> wrote:
>
> On 9/21/12, Greg Stein <gs...@gmail.com> wrote:
> > It's been about 8 weeks... time to stop fixing, and start rolling?
> >
>
> There are some patches in the issue tracker , pending for commit .
> Especially these tickets I consider important as they add some value
> to what we shall propose , mainly regarding the UI .
>
> #203 , #53 , #138 , #139 , #201 , #45 , #174
>
> Beyond that , maybe we can postpone #146 and other tickets scheduled
> for Release 2 , yet pending , for a forthcoming 0.2.1 , 0.3.0 , ...
> whatever other release number it might be .
There are always future releases. IMO, no problem pushing changes out to
the next one. This new release is better than the last, so you're in good
shape.
Further, if those patches in the tickets have not yet been applied, then
maybe it is because they need some review, some testing, or whatever. They
haven't (yet) been applied for some reason... so why delay further to wait
for those reasons to be resolved? They'll hopefully be applied for the
next-next release.
(another happy benefit would be clearing out the IPMC concerns from the
last release)
Cheers,
-g
Re: [VOTE] Release Apache Bloodhound 0.1.0 (incubating) (RC1)
Posted by Olemis Lang <ol...@gmail.com>.
On 9/21/12, Greg Stein <gs...@gmail.com> wrote:
> It's been about 8 weeks... time to stop fixing, and start rolling?
>
There are some patches in the issue tracker , pending for commit .
Especially these tickets I consider important as they add some value
to what we shall propose , mainly regarding the UI .
#203 , #53 , #138 , #139 , #201 , #45 , #174
Beyond that , maybe we can postpone #146 and other tickets scheduled
for Release 2 , yet pending , for a forthcoming 0.2.1 , 0.3.0 , ...
whatever other release number it might be .
;)
>
> ps. once it was announced, we've seen some new interest! round two? :-)
fwiw ... +1
--
Regards,
Olemis.
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article: