You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by Andrew Bayer <an...@gmail.com> on 2011/08/02 00:25:11 UTC
What do we need to do for release 0.1?
(I wanted to get this on the wiki but I don't yet have wiki write access, so
here's an email!)
What exactly do we need to do in order to push out a first release, based on
the current code? Here's what I know of, but I'm fairly sure there's more
that I'm not as clear on:
- Get the license headers in place for every pertinent file -
https://issues.apache.org/jira/browse/BIGTOP-2 is for this, and assigned to
me. I'll get this dealt with in the next couple days.
- Define exactly what it is we're releasing for the first release - what
platforms do we support?
- Some general code cleanup - e.g.,
https://issues.apache.org/jira/browse/BIGTOP-3 for removing .gitignore
files.
- ...I honestly don't know what else we need to do. =)
This is my first Apache project/release, so I don't know what other checkbox
issues need to be dealt with besides the license headers.
Suggestions/pointers/etc would be helpful.
Once I've got wiki write access, I'll put this up on the wiki and let
everyone know where it is, so that we can update it communally.
A.
Re: What do we need to do for release 0.1?
Posted by Patrick Hunt <ph...@apache.org>.
btw, you might request git access be enabled for your svn repo:
http://git.apache.org/
here's an example:
https://issues.apache.org/jira/browse/INFRA-3819
Patrick
On Wed, Aug 3, 2011 at 9:58 AM, Patrick Hunt <ph...@apache.org> wrote:
> Awesome.
>
> Take a look at the incubator release guide:
> http://incubator.apache.org/guides/releasemanagement.html
>
> Also look at your incubator status page:
> http://incubator.apache.org/projects/bigtop.html
> you need to work through the work items. You all (committers) are
> responsible for keeping this page up to date. If you've completed some
> of these items please do edit the content of this page, which you can
> do here:
> https://svn.apache.org/repos/asf/incubator/public/trunk
> (see the instructions in that directory)
>
> Patrick
>
> On Tue, Aug 2, 2011 at 11:09 AM, Andrew Bayer <an...@gmail.com> wrote:
>> I've created a wiki page for tracking what we need to do for 0.1.0 to get
>> released -
>> https://cwiki.apache.org/confluence/display/BIGTOP/Release+0.1.0+Roadmap
>>
>> I've also added a version for 0.1.0 to JIRA, as well as General, Debian and
>> RPM components. And hey, I'll volunteer to be the release manager for 0.1.0
>> while I'm at it. =)
>>
>> A.
>>
>> On Tue, Aug 2, 2011 at 8:05 AM, Andrew Bayer <an...@gmail.com> wrote:
>>
>>> Reading through all that now...I'm wondering what else beyond the process
>>> stuff we need to do in order to get Bigtop to a state where we're
>>> comfortable releasing it. That is - how much code cleanup do we need, etc?
>>>
>>> A.
>>>
>>>
>>> On Mon, Aug 1, 2011 at 5:33 PM, Patrick Hunt <ph...@apache.org> wrote:
>>>
>>>> Looking at someone else's release process might also provide insights.
>>>> Whirr is a pretty good one imo.
>>>> https://cwiki.apache.org/WHIRR/how-to-release.html
>>>>
>>>> Patrick
>>>>
>>>> On Mon, Aug 1, 2011 at 4:10 PM, Andrei Savu <sa...@gmail.com>
>>>> wrote:
>>>> > We should probably follow the best practices listed in the following
>>>> guide:
>>>> >
>>>> > http://incubator.apache.org/guides/releasemanagement.html
>>>> >
>>>> > From my experience we will need to go through a few RCs in order to
>>>> > fix all the licensing issues.
>>>> >
>>>> > -- Andrei
>>>> >
>>>> > On Mon, Aug 1, 2011 at 3:25 PM, Andrew Bayer <an...@gmail.com>
>>>> wrote:
>>>> >> (I wanted to get this on the wiki but I don't yet have wiki write
>>>> access, so
>>>> >> here's an email!)
>>>> >>
>>>> >> What exactly do we need to do in order to push out a first release,
>>>> based on
>>>> >> the current code? Here's what I know of, but I'm fairly sure there's
>>>> more
>>>> >> that I'm not as clear on:
>>>> >>
>>>> >> - Get the license headers in place for every pertinent file -
>>>> >> https://issues.apache.org/jira/browse/BIGTOP-2 is for this, and
>>>> assigned to
>>>> >> me. I'll get this dealt with in the next couple days.
>>>> >> - Define exactly what it is we're releasing for the first release -
>>>> what
>>>> >> platforms do we support?
>>>> >> - Some general code cleanup - e.g.,
>>>> >> https://issues.apache.org/jira/browse/BIGTOP-3 for removing .gitignore
>>>> >> files.
>>>> >> - ...I honestly don't know what else we need to do. =)
>>>> >>
>>>> >> This is my first Apache project/release, so I don't know what other
>>>> checkbox
>>>> >> issues need to be dealt with besides the license headers.
>>>> >> Suggestions/pointers/etc would be helpful.
>>>> >>
>>>> >> Once I've got wiki write access, I'll put this up on the wiki and let
>>>> >> everyone know where it is, so that we can update it communally.
>>>> >>
>>>> >> A.
>>>> >>
>>>> >
>>>>
>>>
>>>
>>
>
Re: What do we need to do for release 0.1?
Posted by Andrew Bayer <an...@gmail.com>.
I'll go through that and update anything that is completed today.
A.
On Wed, Aug 3, 2011 at 9:58 AM, Patrick Hunt <ph...@apache.org> wrote:
> Awesome.
>
> Take a look at the incubator release guide:
> http://incubator.apache.org/guides/releasemanagement.html
>
> Also look at your incubator status page:
> http://incubator.apache.org/projects/bigtop.html
> you need to work through the work items. You all (committers) are
> responsible for keeping this page up to date. If you've completed some
> of these items please do edit the content of this page, which you can
> do here:
> https://svn.apache.org/repos/asf/incubator/public/trunk
> (see the instructions in that directory)
>
> Patrick
>
> On Tue, Aug 2, 2011 at 11:09 AM, Andrew Bayer <an...@gmail.com>
> wrote:
> > I've created a wiki page for tracking what we need to do for 0.1.0 to get
> > released -
> > https://cwiki.apache.org/confluence/display/BIGTOP/Release+0.1.0+Roadmap
> >
> > I've also added a version for 0.1.0 to JIRA, as well as General, Debian
> and
> > RPM components. And hey, I'll volunteer to be the release manager for
> 0.1.0
> > while I'm at it. =)
> >
> > A.
> >
> > On Tue, Aug 2, 2011 at 8:05 AM, Andrew Bayer <an...@gmail.com>
> wrote:
> >
> >> Reading through all that now...I'm wondering what else beyond the
> process
> >> stuff we need to do in order to get Bigtop to a state where we're
> >> comfortable releasing it. That is - how much code cleanup do we need,
> etc?
> >>
> >> A.
> >>
> >>
> >> On Mon, Aug 1, 2011 at 5:33 PM, Patrick Hunt <ph...@apache.org> wrote:
> >>
> >>> Looking at someone else's release process might also provide insights.
> >>> Whirr is a pretty good one imo.
> >>> https://cwiki.apache.org/WHIRR/how-to-release.html
> >>>
> >>> Patrick
> >>>
> >>> On Mon, Aug 1, 2011 at 4:10 PM, Andrei Savu <sa...@gmail.com>
> >>> wrote:
> >>> > We should probably follow the best practices listed in the following
> >>> guide:
> >>> >
> >>> > http://incubator.apache.org/guides/releasemanagement.html
> >>> >
> >>> > From my experience we will need to go through a few RCs in order to
> >>> > fix all the licensing issues.
> >>> >
> >>> > -- Andrei
> >>> >
> >>> > On Mon, Aug 1, 2011 at 3:25 PM, Andrew Bayer <andrew.bayer@gmail.com
> >
> >>> wrote:
> >>> >> (I wanted to get this on the wiki but I don't yet have wiki write
> >>> access, so
> >>> >> here's an email!)
> >>> >>
> >>> >> What exactly do we need to do in order to push out a first release,
> >>> based on
> >>> >> the current code? Here's what I know of, but I'm fairly sure there's
> >>> more
> >>> >> that I'm not as clear on:
> >>> >>
> >>> >> - Get the license headers in place for every pertinent file -
> >>> >> https://issues.apache.org/jira/browse/BIGTOP-2 is for this, and
> >>> assigned to
> >>> >> me. I'll get this dealt with in the next couple days.
> >>> >> - Define exactly what it is we're releasing for the first release -
> >>> what
> >>> >> platforms do we support?
> >>> >> - Some general code cleanup - e.g.,
> >>> >> https://issues.apache.org/jira/browse/BIGTOP-3 for removing
> .gitignore
> >>> >> files.
> >>> >> - ...I honestly don't know what else we need to do. =)
> >>> >>
> >>> >> This is my first Apache project/release, so I don't know what other
> >>> checkbox
> >>> >> issues need to be dealt with besides the license headers.
> >>> >> Suggestions/pointers/etc would be helpful.
> >>> >>
> >>> >> Once I've got wiki write access, I'll put this up on the wiki and
> let
> >>> >> everyone know where it is, so that we can update it communally.
> >>> >>
> >>> >> A.
> >>> >>
> >>> >
> >>>
> >>
> >>
> >
>
Re: What do we need to do for release 0.1?
Posted by Patrick Hunt <ph...@apache.org>.
Awesome.
Take a look at the incubator release guide:
http://incubator.apache.org/guides/releasemanagement.html
Also look at your incubator status page:
http://incubator.apache.org/projects/bigtop.html
you need to work through the work items. You all (committers) are
responsible for keeping this page up to date. If you've completed some
of these items please do edit the content of this page, which you can
do here:
https://svn.apache.org/repos/asf/incubator/public/trunk
(see the instructions in that directory)
Patrick
On Tue, Aug 2, 2011 at 11:09 AM, Andrew Bayer <an...@gmail.com> wrote:
> I've created a wiki page for tracking what we need to do for 0.1.0 to get
> released -
> https://cwiki.apache.org/confluence/display/BIGTOP/Release+0.1.0+Roadmap
>
> I've also added a version for 0.1.0 to JIRA, as well as General, Debian and
> RPM components. And hey, I'll volunteer to be the release manager for 0.1.0
> while I'm at it. =)
>
> A.
>
> On Tue, Aug 2, 2011 at 8:05 AM, Andrew Bayer <an...@gmail.com> wrote:
>
>> Reading through all that now...I'm wondering what else beyond the process
>> stuff we need to do in order to get Bigtop to a state where we're
>> comfortable releasing it. That is - how much code cleanup do we need, etc?
>>
>> A.
>>
>>
>> On Mon, Aug 1, 2011 at 5:33 PM, Patrick Hunt <ph...@apache.org> wrote:
>>
>>> Looking at someone else's release process might also provide insights.
>>> Whirr is a pretty good one imo.
>>> https://cwiki.apache.org/WHIRR/how-to-release.html
>>>
>>> Patrick
>>>
>>> On Mon, Aug 1, 2011 at 4:10 PM, Andrei Savu <sa...@gmail.com>
>>> wrote:
>>> > We should probably follow the best practices listed in the following
>>> guide:
>>> >
>>> > http://incubator.apache.org/guides/releasemanagement.html
>>> >
>>> > From my experience we will need to go through a few RCs in order to
>>> > fix all the licensing issues.
>>> >
>>> > -- Andrei
>>> >
>>> > On Mon, Aug 1, 2011 at 3:25 PM, Andrew Bayer <an...@gmail.com>
>>> wrote:
>>> >> (I wanted to get this on the wiki but I don't yet have wiki write
>>> access, so
>>> >> here's an email!)
>>> >>
>>> >> What exactly do we need to do in order to push out a first release,
>>> based on
>>> >> the current code? Here's what I know of, but I'm fairly sure there's
>>> more
>>> >> that I'm not as clear on:
>>> >>
>>> >> - Get the license headers in place for every pertinent file -
>>> >> https://issues.apache.org/jira/browse/BIGTOP-2 is for this, and
>>> assigned to
>>> >> me. I'll get this dealt with in the next couple days.
>>> >> - Define exactly what it is we're releasing for the first release -
>>> what
>>> >> platforms do we support?
>>> >> - Some general code cleanup - e.g.,
>>> >> https://issues.apache.org/jira/browse/BIGTOP-3 for removing .gitignore
>>> >> files.
>>> >> - ...I honestly don't know what else we need to do. =)
>>> >>
>>> >> This is my first Apache project/release, so I don't know what other
>>> checkbox
>>> >> issues need to be dealt with besides the license headers.
>>> >> Suggestions/pointers/etc would be helpful.
>>> >>
>>> >> Once I've got wiki write access, I'll put this up on the wiki and let
>>> >> everyone know where it is, so that we can update it communally.
>>> >>
>>> >> A.
>>> >>
>>> >
>>>
>>
>>
>
Re: What do we need to do for release 0.1?
Posted by Andrew Bayer <an...@gmail.com>.
I've created a wiki page for tracking what we need to do for 0.1.0 to get
released -
https://cwiki.apache.org/confluence/display/BIGTOP/Release+0.1.0+Roadmap
I've also added a version for 0.1.0 to JIRA, as well as General, Debian and
RPM components. And hey, I'll volunteer to be the release manager for 0.1.0
while I'm at it. =)
A.
On Tue, Aug 2, 2011 at 8:05 AM, Andrew Bayer <an...@gmail.com> wrote:
> Reading through all that now...I'm wondering what else beyond the process
> stuff we need to do in order to get Bigtop to a state where we're
> comfortable releasing it. That is - how much code cleanup do we need, etc?
>
> A.
>
>
> On Mon, Aug 1, 2011 at 5:33 PM, Patrick Hunt <ph...@apache.org> wrote:
>
>> Looking at someone else's release process might also provide insights.
>> Whirr is a pretty good one imo.
>> https://cwiki.apache.org/WHIRR/how-to-release.html
>>
>> Patrick
>>
>> On Mon, Aug 1, 2011 at 4:10 PM, Andrei Savu <sa...@gmail.com>
>> wrote:
>> > We should probably follow the best practices listed in the following
>> guide:
>> >
>> > http://incubator.apache.org/guides/releasemanagement.html
>> >
>> > From my experience we will need to go through a few RCs in order to
>> > fix all the licensing issues.
>> >
>> > -- Andrei
>> >
>> > On Mon, Aug 1, 2011 at 3:25 PM, Andrew Bayer <an...@gmail.com>
>> wrote:
>> >> (I wanted to get this on the wiki but I don't yet have wiki write
>> access, so
>> >> here's an email!)
>> >>
>> >> What exactly do we need to do in order to push out a first release,
>> based on
>> >> the current code? Here's what I know of, but I'm fairly sure there's
>> more
>> >> that I'm not as clear on:
>> >>
>> >> - Get the license headers in place for every pertinent file -
>> >> https://issues.apache.org/jira/browse/BIGTOP-2 is for this, and
>> assigned to
>> >> me. I'll get this dealt with in the next couple days.
>> >> - Define exactly what it is we're releasing for the first release -
>> what
>> >> platforms do we support?
>> >> - Some general code cleanup - e.g.,
>> >> https://issues.apache.org/jira/browse/BIGTOP-3 for removing .gitignore
>> >> files.
>> >> - ...I honestly don't know what else we need to do. =)
>> >>
>> >> This is my first Apache project/release, so I don't know what other
>> checkbox
>> >> issues need to be dealt with besides the license headers.
>> >> Suggestions/pointers/etc would be helpful.
>> >>
>> >> Once I've got wiki write access, I'll put this up on the wiki and let
>> >> everyone know where it is, so that we can update it communally.
>> >>
>> >> A.
>> >>
>> >
>>
>
>
Re: What do we need to do for release 0.1?
Posted by Andrew Bayer <an...@gmail.com>.
Reading through all that now...I'm wondering what else beyond the process
stuff we need to do in order to get Bigtop to a state where we're
comfortable releasing it. That is - how much code cleanup do we need, etc?
A.
On Mon, Aug 1, 2011 at 5:33 PM, Patrick Hunt <ph...@apache.org> wrote:
> Looking at someone else's release process might also provide insights.
> Whirr is a pretty good one imo.
> https://cwiki.apache.org/WHIRR/how-to-release.html
>
> Patrick
>
> On Mon, Aug 1, 2011 at 4:10 PM, Andrei Savu <sa...@gmail.com> wrote:
> > We should probably follow the best practices listed in the following
> guide:
> >
> > http://incubator.apache.org/guides/releasemanagement.html
> >
> > From my experience we will need to go through a few RCs in order to
> > fix all the licensing issues.
> >
> > -- Andrei
> >
> > On Mon, Aug 1, 2011 at 3:25 PM, Andrew Bayer <an...@gmail.com>
> wrote:
> >> (I wanted to get this on the wiki but I don't yet have wiki write
> access, so
> >> here's an email!)
> >>
> >> What exactly do we need to do in order to push out a first release,
> based on
> >> the current code? Here's what I know of, but I'm fairly sure there's
> more
> >> that I'm not as clear on:
> >>
> >> - Get the license headers in place for every pertinent file -
> >> https://issues.apache.org/jira/browse/BIGTOP-2 is for this, and
> assigned to
> >> me. I'll get this dealt with in the next couple days.
> >> - Define exactly what it is we're releasing for the first release - what
> >> platforms do we support?
> >> - Some general code cleanup - e.g.,
> >> https://issues.apache.org/jira/browse/BIGTOP-3 for removing .gitignore
> >> files.
> >> - ...I honestly don't know what else we need to do. =)
> >>
> >> This is my first Apache project/release, so I don't know what other
> checkbox
> >> issues need to be dealt with besides the license headers.
> >> Suggestions/pointers/etc would be helpful.
> >>
> >> Once I've got wiki write access, I'll put this up on the wiki and let
> >> everyone know where it is, so that we can update it communally.
> >>
> >> A.
> >>
> >
>
Re: What do we need to do for release 0.1?
Posted by Patrick Hunt <ph...@apache.org>.
Looking at someone else's release process might also provide insights.
Whirr is a pretty good one imo.
https://cwiki.apache.org/WHIRR/how-to-release.html
Patrick
On Mon, Aug 1, 2011 at 4:10 PM, Andrei Savu <sa...@gmail.com> wrote:
> We should probably follow the best practices listed in the following guide:
>
> http://incubator.apache.org/guides/releasemanagement.html
>
> From my experience we will need to go through a few RCs in order to
> fix all the licensing issues.
>
> -- Andrei
>
> On Mon, Aug 1, 2011 at 3:25 PM, Andrew Bayer <an...@gmail.com> wrote:
>> (I wanted to get this on the wiki but I don't yet have wiki write access, so
>> here's an email!)
>>
>> What exactly do we need to do in order to push out a first release, based on
>> the current code? Here's what I know of, but I'm fairly sure there's more
>> that I'm not as clear on:
>>
>> - Get the license headers in place for every pertinent file -
>> https://issues.apache.org/jira/browse/BIGTOP-2 is for this, and assigned to
>> me. I'll get this dealt with in the next couple days.
>> - Define exactly what it is we're releasing for the first release - what
>> platforms do we support?
>> - Some general code cleanup - e.g.,
>> https://issues.apache.org/jira/browse/BIGTOP-3 for removing .gitignore
>> files.
>> - ...I honestly don't know what else we need to do. =)
>>
>> This is my first Apache project/release, so I don't know what other checkbox
>> issues need to be dealt with besides the license headers.
>> Suggestions/pointers/etc would be helpful.
>>
>> Once I've got wiki write access, I'll put this up on the wiki and let
>> everyone know where it is, so that we can update it communally.
>>
>> A.
>>
>
Re: What do we need to do for release 0.1?
Posted by Andrei Savu <sa...@gmail.com>.
We should probably follow the best practices listed in the following guide:
http://incubator.apache.org/guides/releasemanagement.html
>From my experience we will need to go through a few RCs in order to
fix all the licensing issues.
-- Andrei
On Mon, Aug 1, 2011 at 3:25 PM, Andrew Bayer <an...@gmail.com> wrote:
> (I wanted to get this on the wiki but I don't yet have wiki write access, so
> here's an email!)
>
> What exactly do we need to do in order to push out a first release, based on
> the current code? Here's what I know of, but I'm fairly sure there's more
> that I'm not as clear on:
>
> - Get the license headers in place for every pertinent file -
> https://issues.apache.org/jira/browse/BIGTOP-2 is for this, and assigned to
> me. I'll get this dealt with in the next couple days.
> - Define exactly what it is we're releasing for the first release - what
> platforms do we support?
> - Some general code cleanup - e.g.,
> https://issues.apache.org/jira/browse/BIGTOP-3 for removing .gitignore
> files.
> - ...I honestly don't know what else we need to do. =)
>
> This is my first Apache project/release, so I don't know what other checkbox
> issues need to be dealt with besides the license headers.
> Suggestions/pointers/etc would be helpful.
>
> Once I've got wiki write access, I'll put this up on the wiki and let
> everyone know where it is, so that we can update it communally.
>
> A.
>