Hi all,
I've been studying the release document and wading knee-deep through
signing and licensing and all the other requirements and have come up
with a checklist that needs to be done. Whilst it looks big i'm sure
it'll be reduced next time around once we've sorted everything out a
bit more. If a
Hi
I think that would be great!
As Ali already mentioned - there's a WIki on the subject -
http://incubator.apache.org/guides/releasemanagement.html
The preferable way to release it - would be by creating a debian package -
similar to what was done at kune.cc (which is Apache Wave fork) -
https://g
Hi,
I've been a lurker on this list ever since Wave came to Apache. I've been
following it since the sandbox days and have been interested the whole way.
Once it went open source I found I couldn't really contribute as java isn't
really my forte. This looks like a perfect opportunity though and i'l
El 12/09/12 11:54, Yuri Z escribió:
> Probably just a tar. But I ll check if we can create a debian package -
> similar to kune.cc.
>
I can help with the package. Probably our debian package can be a good
start point:
https://gitorious.org/kune/trunk/trees/master/debian
BR,
Vicente
Probably just a tar. But I ll check if we can create a debian package -
similar to kune.cc.
On Wed, Sep 12, 2012 at 10:56 AM, Ali Lown wrote:
> It looks like they started writing a document here:
> http://incubator.apache.org/guides/releasemanagement.html
>
> How do you propose releasing WIAB? D
It looks like they started writing a document here:
http://incubator.apache.org/guides/releasemanagement.html
How do you propose releasing WIAB? Do we just want to tar the compiled
code, rather than trying to produce any particular distro's package format?
On 12 Sep 2012 07:28, "Yuri Z" wrote:
>
Well, I guess you are right, and release will be a good move.
I can take on the role of release manager. Now where can I find what are
the responsibilities?
On Wed, Sep 12, 2012 at 9:15 AM, Upayavira wrote:
> So, are we discussing? We *need* to start discussing this, as we cannot
> stay still in
So, are we discussing? We *need* to start discussing this, as we cannot
stay still in the incubator forever.
Any thoughts?
Note, you don't need to be a committer to be a release manager. Maybe
this is your chance to get more involved.
Upayavira
On Mon, Sep 10, 2012, at 01:28 PM, Upayavira wrote
Thanks. Now that we've said to the board that we're discussing what it
takes to make a release, perhaps we'd better do it :-)
Is anyone prepared to take on the job of release manager?
Note, code quality is of no consequence in relation to releasing in the
incubator. What's needed is to show that
I updated the Wiki for Sep 2012 report. Please feel free to add/edit.
On Sun, Sep 9, 2012 at 4:55 PM, Max pane wrote:
> Hello,
>
> Even i would like to involve in Administration,Under michael,
>
> Regards
> Jack
>
> On Sun, Sep 9, 2012 at 2:51 PM, Upayavira wrote:
>
> > IIRC, the June report fo
Hello,
Even i would like to involve in Administration,Under michael,
Regards
Jack
On Sun, Sep 9, 2012 at 2:51 PM, Upayavira wrote:
> IIRC, the June report focused more on development issues than on
> community/graduation issues, and it is the latter that the incubator PMC
> and board are inter
IIRC, the June report focused more on development issues than on
community/graduation issues, and it is the latter that the incubator PMC
and board are interested in,
Regarding releases, we can release now. Call it alpha-0.0.1. The point
of releasing is twofold: to show that all licensing issues h
uri Z
Reply-To:
Date: Saturday, September 8, 2012 2:10 PM
To:
Subject: Re: Board report
Yep, we can just copy paste most of the contents from the previous report.
The report is just added to the wiki page and can be edited later, so it's
not a problem to write a draft version first and t
Yep, we can just copy paste most of the contents from the previous report.
The report is just added to the wiki page and can be edited later, so it's
not a problem to write a draft version first and then fix if needed.
On Sun, Sep 9, 2012 at 12:02 AM, Ali Lown wrote:
> Looking at the June report
Looking at the June report, we can copy-paste most of the contents for
the September report.
The items listed as 'most important issues' are still relevant, as are
the 'more developments not yet finished but in progress'.
To address 'Ross Gardlers's comments, it is probably worth noting that
I wa
Done. If other PMC want to make changes please go ahead - that was just the
first thing I came up with.
A.
On 12 January 2011 21:55, Upayavira wrote:
> Looks good - can you add it to the wiki page?
>
> Thanks for a speedy response.
>
> Upayavira
>
> On Wed, 12 Jan 2011 21:40 +1100, "Alex North"
Looks good - can you add it to the wiki page?
Thanks for a speedy response.
Upayavira
On Wed, 12 Jan 2011 21:40 +1100, "Alex North" wrote:
> Eek. Ok, let me try:
>
> Wave
>
> Wave a real-time communication and collaboration tool
>
> Wave entered incubation on December 12, 2010.
>
> We're cu
Eek. Ok, let me try:
Wave
Wave a real-time communication and collaboration tool
Wave entered incubation on December 12, 2010.
We're currently in the process of moving to Apache infrastructure. Mailing
lists and continuous build have moved, source, issues and documentation has
not. On the techni
18 matches
Mail list logo
