brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Nalley <da...@gnsa.us>
Subject Re: Next release?
Date Wed, 02 Jul 2014 15:42:23 GMT
On Wed, Jul 2, 2014 at 7:20 AM, Richard Downer <richard@apache.org> wrote:
> I think it's a good idea, but I don't believe (correct me if I am
> wrong) that it is a requirement for a release.
>

That is correct. While there is general dislike for @author tags, it
isn't something that would block a release.

> OTOH, if we're having to touch every source file to add the ASF
> notice, then removing these tags immediately after would minimise the
> disruption (PR merge conflicts etc.)...
>

Yes, and ASF notice in source is a requirement.


> Richard.
>
> On 2 July 2014 12:15, Andrea Turli <andrea.turli@cloudsoftcorp.com> wrote:
>> Hi all,
>>
>> do we also need to remove the @author from javadoc as I've seen in other
>> apache projects?
>> http://mail-archives.apache.org/mod_mbox/jclouds-dev/201406.mbox/%3C20140605170609.GA3566%40sherlock%3E
>>
>> HTH,
>> Andrea
>>
>>
>> On 2 July 2014 12:58, Richard Downer <richard@apache.org> wrote:
>>
>>> Hi Aled,
>>>
>>> I'm working on that list at the moment. The first priority was the
>>> name of the release[1]
>>>
>>> Richard.
>>>
>>> [1]http://youtu.be/cywy4soWg2A
>>>
>>> On 2 July 2014 11:46, Aled Sage <aled.sage@gmail.com> wrote:
>>> > +1
>>> >
>>> > Richard, what is on the list of things we still need to do for an
>>> > Apache-compliant release?
>>> >
>>> > Aled
>>> >
>>> >
>>> >
>>> > On 02/07/2014 11:42, Alex Heneveld wrote:
>>> >>
>>> >>
>>> >> M2 ASAP and GA soon after.
>>> >>
>>> >> There are so many great new features!
>>> >>
>>> >> --A
>>> >>
>>> >>
>>> >> On 02/07/2014 11:33, Richard Downer wrote:
>>> >>>
>>> >>> We should start thinking about making a release. It's an important
>>> >>> milestone in incubation; there will also likely be quite a bit of
>>> >>> working involved in getting our codebase and our procedures compliant
>>> >>> to Apache standard, and will probably be one or two mis-steps along
>>> >>> the way. So I would like to start planning our next release as soon
as
>>> >>> possible. We have also added several major new features recently
and
>>> >>> it would be great to get these out of SNAPSHOTs and into something
>>> >>> that we can put on the front page of the website!
>>> >>>
>>> >>> The first question is what our next release would be. It could be
>>> >>> 0.7.0-M2-incubating - or it could be a GA version, 0.7.0-incubating.
>>> >>>
>>> >>> While we've collectively made great progress towards our goals for
a
>>> >>> 0.7.0 GA, it may be better to give ourselves a bit of breathing
space
>>> >>> and commence with an M2 release. This means we can concentrate on
>>> >>> getting a good Apache-compliant release, and save filling in the
>>> >>> missing GA-required features until afterwards.
>>> >>>
>>> >>> What are peoples thoughts?
>>> >>>
>>> >>> Richard.
>>> >>
>>> >>
>>> >
>>>

Mime
View raw message