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 <a...@lown.me.uk> wrote: > 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" <vega...@gmail.com> 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 <u...@odoko.co.uk> wrote: > > > > > 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 licensing/etc is all handled > > > > correctly. If folks don't want to make a release public, it can be > > > > produced, vetted by the incubator PMC, and then dropped rather than > > > > published. Having said that, I consider it to be worth while to > release > > > > an alpha version of the code even if it isn't complete, as it may > help > > > > draw in additional developers to help fill in the missing features. > > > > > > > > Thoughts? > > > > > > > > Upayavira > > > > > > > > On Mon, Sep 10, 2012, at 08:21 AM, Yuri Z wrote: > > > > > 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 <your...@gmail.com> > wrote: > > > > > > > > > > > Hello, > > > > > > > > > > > > Even i would like to involve in Administration,Under michael, > > > > > > > > > > > > Regards > > > > > > Jack > > > > > > > > > > > > On Sun, Sep 9, 2012 at 2:51 PM, Upayavira <u...@odoko.co.uk> > 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 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 have > > > been > > > > > > > resolved (reviews undertaken by yourselves and incubator PMC > > before > > > > > > > artifacts are released) and to draw in new developers. Folks > > like. > > > > > > > Having a concrete baseline to work against. Also, two open > source > > > maxims > > > > > > > to consider: release early, release often. This encourages us > to > > > get our > > > > > > > stuff out there early, we'll get better feedback that way. > > Another > > > one I > > > > > > > like is "great ideas and bad code builds community". That is, > > when > > > > > > > developers see incomplete code, their response is often to help > > if > > > x it. > > > > > > > Showing folks the current state of wave code, flaws and all, > > might > > > > > > > actually have the eft of bringing more people to the project. > > > > > > > > > > > > > > We're I to write a report, it would be something like: > > > > > > > > > > > > > > "One new committee added. Discussions (somewhat stalled) on > > > additional > > > > > > > committers. The next major milestone regarding graduation is to > > > make a > > > > > > > release. The current codebase is not considered mature enough > > for a > > > > > > > useful release, however, the community is discussing what is > > > required to > > > > > > > make one, both to better understand the licensing status of our > > > > > > > codebase, and as a means to draw in additional developers and > > thus > > > speed > > > > > > > up development." > > > > > > > > > > > > > > Upayavira > > > > > > > > > > > > > > On Sat, Sep 8, 2012, at 10:02 PM, Ali Lown wrote: > > > > > > > > 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 was voted in to the project. > > > > > > > > > > > > > > > > The WIAB server hardly seems stable enough yet to produce an > > > actual > > > > > > > > release (which seems to be the main thing missing for us to > > > graduate > > > > > > > > from my understanding). > > > > > > > > > > > > > > > > @Michael: as project lead (according to Jira), it is probably > > > best to > > > > > > > > leave liaising with the board (via the reports) to you. > > > > > > > > > > > > > > > > Ali > > > > > > > > > > > > > > > > On 8 September 2012 21:39, Upayavira <u...@odoko.co.uk> wrote: > > > > > > > > > Wave folks, > > > > > > > > > > > > > > > > > > We're overdue with our three-monthly incubator/board > report, > > > it was > > > > > > due > > > > > > > > > last Wednesday (6 Sept). > > > > > > > > > > > > > > > > > > Do we have a volunteer to write one, and soon? > > > > > > > > > > > > > > > > > > Remember, it should be focused on what Wave needs to do to > > > graduate, > > > > > > > > > rather than on technical matters. > > > > > > > > > > > > > > > > > > Thanks, > > > > > > > > > > > > > > > > > > Upayavira > > > > > > > > > > > > > > > > > > >
