Releasing Fluo incubating 1.0.0

[Keith Turner <ke...@deenlo.com>]

IMO Fluo is ready for a 1.0.0 release.   It really nice that we can now do
this with Apache package names and Maven coordinates.  I am trying to
brainstorm what needs to be done before releasing 1.0.0.  I feel like we
are in limbo waiting on INFRA, but I would like to get the ball rolling on
working towards putting a 1.0.0 release up for a vote.  Here is my quick
list of things to do, what else needs to be added?

 * Rename packages and make any needed documentation updates
 * Run Fluo stress test on EC2
 * Legal stuff??
 * Triage any issues that we want fixed before 1.0.0
 * Having an Apache web site for Fluo is a prerequisite
 * Make pom updates for doing a release.

Re: Releasing Fluo incubating 1.0.0

[Keith Turner <ke...@deenlo.com>]

I am not sure why infra does not answer our questions on the issue.

On Tue, Jun 7, 2016 at 6:31 PM, Christopher <ct...@apache.org> wrote:

> I haven't had time to follow up yet. Sorry. And I might be busy this week
> to do it. If somebody else wants to facilitate the conversation, I can
> grant the infra user access. (Keith or Mike could do it, too)
>
> On Tue, Jun 7, 2016 at 5:30 PM Josh Elser <jo...@gmail.com> wrote:
>
> > Any progress?
> >
> > Christopher wrote:
> > > I commented in HipChat #asfinfra yesterday asking for help with our git
> > > setup:
> > >
> > > [9:36 PM] Christopher Tubbs (ctubbsii): Is anybody available to assist
> > with
> > > INFRA-11901? Basically, we just need to transfer the GitHub repos over
> to
> > > ASF land so the GitHub issues and existing code history go with it.
> > > Essentially, same thing Pony did. I can grant ownership temporarily to
> > our
> > > existing GitHub org so an INFRA member can do the transfer/rename/etc.
> > > [9:37 PM] Christopher Tubbs (ctubbsii): If not, no big deal. I can
> check
> > > back tomorrow (earlier in the day).
> > >
> > > , but nobody was around that late. I meant to try again today, but got
> > > distracted with other stuffs. I can try again on Monday... or maybe
> over
> > > the weekend (not likely over the weekend, though).
> > >
> > > On Fri, Jun 3, 2016 at 3:43 PM Keith Turner<ke...@deenlo.com>  wrote:
> > >
> > >> IMO Fluo is ready for a 1.0.0 release.   It really nice that we can
> now
> > do
> > >> this with Apache package names and Maven coordinates.  I am trying to
> > >> brainstorm what needs to be done before releasing 1.0.0.  I feel like
> we
> > >> are in limbo waiting on INFRA, but I would like to get the ball
> rolling
> > on
> > >> working towards putting a 1.0.0 release up for a vote.  Here is my
> quick
> > >> list of things to do, what else needs to be added?
> > >>
> > >>   * Rename packages and make any needed documentation updates
> > >>   * Run Fluo stress test on EC2
> > >>   * Legal stuff??
> > >>   * Triage any issues that we want fixed before 1.0.0
> > >>   * Having an Apache web site for Fluo is a prerequisite
> > >>   * Make pom updates for doing a release.
> > >>
> > >
> >
>

Re: Releasing Fluo incubating 1.0.0

[Keith Turner <ke...@deenlo.com>]

I will see if I can ask someone in infra chat tomorrow.

On Tue, Jun 7, 2016 at 6:31 PM, Christopher <ct...@apache.org> wrote:

> I haven't had time to follow up yet. Sorry. And I might be busy this week
> to do it. If somebody else wants to facilitate the conversation, I can
> grant the infra user access. (Keith or Mike could do it, too)
>
> On Tue, Jun 7, 2016 at 5:30 PM Josh Elser <jo...@gmail.com> wrote:
>
> > Any progress?
> >
> > Christopher wrote:
> > > I commented in HipChat #asfinfra yesterday asking for help with our git
> > > setup:
> > >
> > > [9:36 PM] Christopher Tubbs (ctubbsii): Is anybody available to assist
> > with
> > > INFRA-11901? Basically, we just need to transfer the GitHub repos over
> to
> > > ASF land so the GitHub issues and existing code history go with it.
> > > Essentially, same thing Pony did. I can grant ownership temporarily to
> > our
> > > existing GitHub org so an INFRA member can do the transfer/rename/etc.
> > > [9:37 PM] Christopher Tubbs (ctubbsii): If not, no big deal. I can
> check
> > > back tomorrow (earlier in the day).
> > >
> > > , but nobody was around that late. I meant to try again today, but got
> > > distracted with other stuffs. I can try again on Monday... or maybe
> over
> > > the weekend (not likely over the weekend, though).
> > >
> > > On Fri, Jun 3, 2016 at 3:43 PM Keith Turner<ke...@deenlo.com>  wrote:
> > >
> > >> IMO Fluo is ready for a 1.0.0 release.   It really nice that we can
> now
> > do
> > >> this with Apache package names and Maven coordinates.  I am trying to
> > >> brainstorm what needs to be done before releasing 1.0.0.  I feel like
> we
> > >> are in limbo waiting on INFRA, but I would like to get the ball
> rolling
> > on
> > >> working towards putting a 1.0.0 release up for a vote.  Here is my
> quick
> > >> list of things to do, what else needs to be added?
> > >>
> > >>   * Rename packages and make any needed documentation updates
> > >>   * Run Fluo stress test on EC2
> > >>   * Legal stuff??
> > >>   * Triage any issues that we want fixed before 1.0.0
> > >>   * Having an Apache web site for Fluo is a prerequisite
> > >>   * Make pom updates for doing a release.
> > >>
> > >
> >
>

Re: Releasing Fluo incubating 1.0.0

[Christopher <ct...@apache.org>]

I haven't had time to follow up yet. Sorry. And I might be busy this week
to do it. If somebody else wants to facilitate the conversation, I can
grant the infra user access. (Keith or Mike could do it, too)

On Tue, Jun 7, 2016 at 5:30 PM Josh Elser <jo...@gmail.com> wrote:

> Any progress?
>
> Christopher wrote:
> > I commented in HipChat #asfinfra yesterday asking for help with our git
> > setup:
> >
> > [9:36 PM] Christopher Tubbs (ctubbsii): Is anybody available to assist
> with
> > INFRA-11901? Basically, we just need to transfer the GitHub repos over to
> > ASF land so the GitHub issues and existing code history go with it.
> > Essentially, same thing Pony did. I can grant ownership temporarily to
> our
> > existing GitHub org so an INFRA member can do the transfer/rename/etc.
> > [9:37 PM] Christopher Tubbs (ctubbsii): If not, no big deal. I can check
> > back tomorrow (earlier in the day).
> >
> > , but nobody was around that late. I meant to try again today, but got
> > distracted with other stuffs. I can try again on Monday... or maybe over
> > the weekend (not likely over the weekend, though).
> >
> > On Fri, Jun 3, 2016 at 3:43 PM Keith Turner<ke...@deenlo.com>  wrote:
> >
> >> IMO Fluo is ready for a 1.0.0 release.   It really nice that we can now
> do
> >> this with Apache package names and Maven coordinates.  I am trying to
> >> brainstorm what needs to be done before releasing 1.0.0.  I feel like we
> >> are in limbo waiting on INFRA, but I would like to get the ball rolling
> on
> >> working towards putting a 1.0.0 release up for a vote.  Here is my quick
> >> list of things to do, what else needs to be added?
> >>
> >>   * Rename packages and make any needed documentation updates
> >>   * Run Fluo stress test on EC2
> >>   * Legal stuff??
> >>   * Triage any issues that we want fixed before 1.0.0
> >>   * Having an Apache web site for Fluo is a prerequisite
> >>   * Make pom updates for doing a release.
> >>
> >
>

Re: Releasing Fluo incubating 1.0.0

[Josh Elser <jo...@gmail.com>]

Any progress?

Christopher wrote:
> I commented in HipChat #asfinfra yesterday asking for help with our git
> setup:
>
> [9:36 PM] Christopher Tubbs (ctubbsii): Is anybody available to assist with
> INFRA-11901? Basically, we just need to transfer the GitHub repos over to
> ASF land so the GitHub issues and existing code history go with it.
> Essentially, same thing Pony did. I can grant ownership temporarily to our
> existing GitHub org so an INFRA member can do the transfer/rename/etc.
> [9:37 PM] Christopher Tubbs (ctubbsii): If not, no big deal. I can check
> back tomorrow (earlier in the day).
>
> , but nobody was around that late. I meant to try again today, but got
> distracted with other stuffs. I can try again on Monday... or maybe over
> the weekend (not likely over the weekend, though).
>
> On Fri, Jun 3, 2016 at 3:43 PM Keith Turner<ke...@deenlo.com>  wrote:
>
>> IMO Fluo is ready for a 1.0.0 release.   It really nice that we can now do
>> this with Apache package names and Maven coordinates.  I am trying to
>> brainstorm what needs to be done before releasing 1.0.0.  I feel like we
>> are in limbo waiting on INFRA, but I would like to get the ball rolling on
>> working towards putting a 1.0.0 release up for a vote.  Here is my quick
>> list of things to do, what else needs to be added?
>>
>>   * Rename packages and make any needed documentation updates
>>   * Run Fluo stress test on EC2
>>   * Legal stuff??
>>   * Triage any issues that we want fixed before 1.0.0
>>   * Having an Apache web site for Fluo is a prerequisite
>>   * Make pom updates for doing a release.
>>
>

Re: Releasing Fluo incubating 1.0.0

[Christopher <ct...@apache.org>]

I commented in HipChat #asfinfra yesterday asking for help with our git
setup:

[9:36 PM] Christopher Tubbs (ctubbsii): Is anybody available to assist with
INFRA-11901? Basically, we just need to transfer the GitHub repos over to
ASF land so the GitHub issues and existing code history go with it.
Essentially, same thing Pony did. I can grant ownership temporarily to our
existing GitHub org so an INFRA member can do the transfer/rename/etc.
[9:37 PM] Christopher Tubbs (ctubbsii): If not, no big deal. I can check
back tomorrow (earlier in the day).

, but nobody was around that late. I meant to try again today, but got
distracted with other stuffs. I can try again on Monday... or maybe over
the weekend (not likely over the weekend, though).

On Fri, Jun 3, 2016 at 3:43 PM Keith Turner <ke...@deenlo.com> wrote:

> IMO Fluo is ready for a 1.0.0 release.   It really nice that we can now do
> this with Apache package names and Maven coordinates.  I am trying to
> brainstorm what needs to be done before releasing 1.0.0.  I feel like we
> are in limbo waiting on INFRA, but I would like to get the ball rolling on
> working towards putting a 1.0.0 release up for a vote.  Here is my quick
> list of things to do, what else needs to be added?
>
>  * Rename packages and make any needed documentation updates
>  * Run Fluo stress test on EC2
>  * Legal stuff??
>  * Triage any issues that we want fixed before 1.0.0
>  * Having an Apache web site for Fluo is a prerequisite
>  * Make pom updates for doing a release.
>

Re: Releasing Fluo incubating 1.0.0

[Josh Elser <jo...@gmail.com>]

Keith Turner wrote:
> IMO Fluo is ready for a 1.0.0 release.   It really nice that we can now do
> this with Apache package names and Maven coordinates.  I am trying to
> brainstorm what needs to be done before releasing 1.0.0.  I feel like we
> are in limbo waiting on INFRA, but I would like to get the ball rolling on
> working towards putting a 1.0.0 release up for a vote.  Here is my quick
> list of things to do, what else needs to be added?
>
>   * Rename packages and make any needed documentation updates
>   * Run Fluo stress test on EC2
>   * Legal stuff??

As far as IP, I can't imagine there are any issues. Individuals should 
been owning the code they contributed (and are cool assigning copyright 
to the ASF).

There will be a necessary pass of all dependencies to make sure that 
they're compatible with the ASLv2. Should make a pass over the source 
code to make sure there are no copy-pastes from other projects (which 
would require a NOTICE update). If we're only doing a src release, we're 
pretty much done there. If we do a bin release too, we'll have to deal 
with the special L&N's for that bin release (the bundled jars).

>   * Triage any issues that we want fixed before 1.0.0
>   * Having an Apache web site for Fluo is a prerequisite

I was just thinking about this one after seeing your blog post. Would be 
nice to get these hosted at the ASF. I guess we're blocked on INFRA to 
get the repos transferred over though. At least Christopher's work on 
Accumulo's website will make this less painful.

>   * Make pom updates for doing a release.
>