Re: Release

2014-07-18 Thread Yuri Z
Ok, the suggested release is here - https://dist.apache.org/repos/dist/dev/incubator/wave/0.5-incubating/ Please review the changes for rc 0.5 at https://github.com/apache/incubator-wave/pull/3 On Fri, Jul 18, 2014 at 12:42 PM, Yuri Z wrote: > Thanks > Anyway, I created an issue for infra to c

Re: Release

2014-07-18 Thread Yuri Z
Thanks Anyway, I created an issue for infra to create release folders for Wave in the https://dist.apache.org/repos/dist/release and https://dist.apache.org/repos/dist/dev https://www.apache.org/dev/release.html#upload-ci On Fri, Jul 18, 2014 at 12:27 PM, Ali Lown wrote: > The people.apache.org

Re: Release

2014-07-18 Thread Ali Lown
The people.apache.org space I was using is just my 'personal' webspace. You can put things in your public_html folder on that machine. (Ssh in as you would expect). Regards, Ali On 18 Jul 2014 10:23, "Yuri Z" wrote: > @Ali another question - you mentioned that it is possible to put a file > int

Re: Release

2014-07-18 Thread Yuri Z
@Ali another question - you mentioned that it is possible to put a file into a folder at people.apache.org and make it available for other via web interface. Is there some guide how to do this? On Thu, Jul 17, 2014 at 7:43 PM, Yuri Zelikov wrote: > Ok > On Jul 17, 2014, at 7:42 PM, Ali Lown wr

Re: Release

2014-07-17 Thread Yuri Zelikov
Ok On Jul 17, 2014, at 7:42 PM, Ali Lown wrote: > I ran it a while back, but things have changed, so I would suggest > rerunning. > > Ali > On 17 Jul 2014 17:40, "Yuri Zelikov" wrote: > >> Do you think we should run it or we already got it covered? >> On Jul 17, 2014, at 7:38 PM, Ali Lown wro

Re: Release

2014-07-17 Thread Ali Lown
I ran it a while back, but things have changed, so I would suggest rerunning. Ali On 17 Jul 2014 17:40, "Yuri Zelikov" wrote: > Do you think we should run it or we already got it covered? > On Jul 17, 2014, at 7:38 PM, Ali Lown wrote: > > > RAT, but it can be a bit overly sensitive. > > > > Ali

Re: Release

2014-07-17 Thread Yuri Zelikov
Do you think we should run it or we already got it covered? On Jul 17, 2014, at 7:38 PM, Ali Lown wrote: > RAT, but it can be a bit overly sensitive. > > Ali > On 17 Jul 2014 17:37, "Yuri Z" wrote: > >> Is there some tool to verify that all files have the licences? >> >> >> On Sat, Jul 12, 2

Re: Release

2014-07-17 Thread Ali Lown
RAT, but it can be a bit overly sensitive. Ali On 17 Jul 2014 17:37, "Yuri Z" wrote: > Is there some tool to verify that all files have the licences? > > > On Sat, Jul 12, 2014 at 5:18 PM, Michael MacFadden < > michael.macfad...@gmail.com> wrote: > > > All, > > > > Although I have been dormant.

Re: Release

2014-07-17 Thread Yuri Z
Is there some tool to verify that all files have the licences? On Sat, Jul 12, 2014 at 5:18 PM, Michael MacFadden < michael.macfad...@gmail.com> wrote: > All, > > Although I have been dormant. I am willing to help out with the release > in any way possible. If you need some one to go through t

Re: Release

2014-07-12 Thread Michael MacFadden
All, Although I have been dormant. I am willing to help out with the release in any way possible. If you need some one to go through the release and test it. Or post it up to he web site once we have it ready let me know. I haven¹t helped out in a while, so I would love to contribute. ~Michael

Re: Release

2014-07-12 Thread Ali Lown
Yuri, AFAIK both of these can be TODOs can be removed now. Thanks, Ali On 12 July 2014 14:01, Yuri Z wrote: > Ok, great. This is a great Wiki. I ll try to go the steps and later to add > a release job to jenkins so the release process will be automated. Off > course if someone want to help with

Re: Release

2014-07-12 Thread Yuri Z
Ok, great. This is a great Wiki. I ll try to go the steps and later to add a release job to jenkins so the release process will be automated. Off course if someone want to help with release stuff - it would be great :) The wiki contains two todos: 1. ODO: Do we need Extension-Name, Implementation-V

Re: Release

2014-07-12 Thread Ali Lown
Yuri, I started writing up the 'procedure' here: https://cwiki.apache.org/confluence/display/WAVE/Release+Procedure It needs updating now that we use git rather than svn. If we could get jenkins building the releases that would be great! (wave-artifacts doesn't seem to be generating the src relea

Re: Release

2014-07-12 Thread Yuri Z
Thanks for update Ali. I think the release is important to show that we handled all the copyright issues, so I would prefer just to release as is and then add the patch later. Anyway, let's try to do the release stuff for rc 05. Are there any scripts that should be run? What is the procedure? By th

Re: Release

2014-07-12 Thread Ali Lown
RC4 was merged back in to master around January, and development has continued in master from there.. I don't recall any major show stoppers with RC4. A look at the vote thread suggests that the only problems left to discuss were the images in thumbnail_patterns, for which we could find no copyrig

Re: Release

2014-07-12 Thread Yuri Z
I think I merged the rc 0.4 into master a while ago. But I don't remember what were the issues that prevented from us to release rc 0.4. @Ali, so you remember what were the issues? On Sat, Jul 12, 2014 at 2:27 PM, Christian Grobmeier wrote: > Hi folks, > > before quite a while, we were discussi

Re: Release planning

2013-05-31 Thread Upayavira
On Fri, May 31, 2013, at 09:46 PM, Ali Lown wrote: > Today's update: > - Created a wave-0.4-release branch > - Created CHANGES > - Written RELEASE-NOTES > - Ensured they are in new builds > - Ensured version number is correct > - Tagged wave-0.4-rc1. > > So, we are now even closer... ;) Yay. Ge

Re: Release planning

2013-05-31 Thread Ali Lown
Today's update: - Created a wave-0.4-release branch - Created CHANGES - Written RELEASE-NOTES - Ensured they are in new builds - Ensured version number is correct - Tagged wave-0.4-rc1. So, we are now even closer... ;) Ali

Re: Release planning

2013-05-31 Thread Upayavira
Anything under 1.0. Could be 0.4.0 if that makes semver fans happier :-) Upayavira On Fri, May 31, 2013, at 03:10 PM, John Blossom - Shore Communications Inc. wrote: > You can argue it either way, it really comes down to how you want to > position the new architecture. If Yuri's comfortable with

Re: Release planning

2013-05-31 Thread John Blossom - Shore Communications Inc.
You can argue it either way, it really comes down to how you want to position the new architecture. If Yuri's comfortable with 0.4, then I am. J

Re: Release planning

2013-05-31 Thread Bruno Gonzalez
Since we are having a discussion about what specific version number the release should be, I think we are not using semantic version at the moment. Semantic versioning does not depend on political or cultural issues, just on API retrocompatibility, which is not subject to opinions. Following semver

Re: Release planning

2013-05-31 Thread Alfredo Abambres
I agree that a anything below 1.0 sends the right message AFAIK. Novice question (similar to Dave's - but didn't saw an answer): does Apache Wave versioning uses the http://semver.org/ "standard"? Or will use? Thanks. http://alfredo.abambres.com *"Moving, always moving, and living inside mov

Re: Release planning

2013-05-30 Thread Yuri Z
0.4 is fine with me On Thu, May 30, 2013 at 11:03 PM, Upayavira wrote: > I agree that 1.0 would give the wrong message. Some <1.0 version is > right. > > Upayavira > > On Thu, May 30, 2013, at 08:49 PM, Ali Lown wrote: > > >> Blockers: > > >> What version number should this be? The code is maki

Re: Release planning

2013-05-30 Thread Upayavira
I agree that 1.0 would give the wrong message. Some <1.0 version is right. Upayavira On Thu, May 30, 2013, at 08:49 PM, Ali Lown wrote: > >> Blockers: > >> What version number should this be? The code is making reference to > >> waveinabox 0.3. (Was 0.1, 0.2 ever released?). If we use 0.4 as our

Re: Release planning

2013-05-25 Thread Christian Grobmeier
Great to see you are heading towards a release. I would like to mention if you would build with Maven, there is a lot of these release steps prepared with the so called "apache parent". It's a parent pom which helps to create release candidates etc. I saw you are going with ant, so I would like t

Re: Release planning

2013-05-24 Thread Michael MacFadden
I have no problem signing, I would like to do SOMETHING to help out. I can make the time. ~Michael On 5/24/13 6:28 AM, "Angus Turner" wrote: >Don't see a reason not to tag the release. I think we should go from 0.1, >but I think it's more a personal thing. > >Thanks >Angus Turner >angusisf...@

Re: Release planning

2013-05-24 Thread Angus Turner
Don't see a reason not to tag the release. I think we should go from 0.1, but I think it's more a personal thing. Thanks Angus Turner angusisf...@gmail.com On Fri, May 24, 2013 at 8:51 PM, Ali Lown wrote: > Ok. Do we feel happy to tag the tree now? > > What do we want to call this release? (I

Re: Release planning

2013-05-24 Thread Ali Lown
Ok. Do we feel happy to tag the tree now? What do we want to call this release? (I assume <1, since we don't feel it is completely stable yet. See: https://incubator.apache.org/guides/releasemanagement.html#best-practice-versioning ) @Michael: Are you still happy to do signing? Ali On 23 May 20

Re: Release planning

2013-05-23 Thread Angus Turner
I believe Michael had volunteered to do the signing and push the release over the line, but he seems pretty busy. There's guides on the foundation website on how to sign a release etc. Thanks Angus Turner angusisf...@gmail.com On Thu, May 23, 2013 at 10:55 PM, Ali Lown wrote: > So The list

Re: Next Steps re: Release

2012-12-16 Thread Yuri Z
I ll make a bash script to download the jars On Sun, Dec 16, 2012 at 10:01 PM, Upayavira wrote: > Great! Thx, > > Upayavira > > On Sun, Dec 16, 2012, at 07:19 PM, Michael MacFadden wrote: > > Yes. That should be our first step. I will add a patch to add the txt > > file and remove the jars. > >

Re: Next Steps re: Release

2012-12-16 Thread Upayavira
Great! Thx, Upayavira On Sun, Dec 16, 2012, at 07:19 PM, Michael MacFadden wrote: > Yes. That should be our first step. I will add a patch to add the txt > file and remove the jars. > > ~Michael > > On Dec 16, 2012, at 11:12 AM, Upayavira wrote: > > > Emma and junit are build time requiremen

Re: Next Steps re: Release

2012-12-16 Thread Michael MacFadden
Yes. That should be our first step. I will add a patch to add the txt file and remove the jars. ~Michael On Dec 16, 2012, at 11:12 AM, Upayavira wrote: > Emma and junit are build time requirements, anyone building code can > follow instructions. > > We should get a release out with a text fi

Re: Next Steps re: Release

2012-12-16 Thread Upayavira
Emma and junit are build time requirements, anyone building code can follow instructions. We should get a release out with a text file saying, "download Emma and junit from here:xyz". You never know, someone might download it, then offer a patch to automate the download. But if you don't release,

Re: Release

2012-11-25 Thread Yuri Z
Great, thanks Ali! On Sun, Nov 25, 2012 at 3:28 PM, Ali Lown wrote: > I took another look over the resultant diff and found a few typos from > when I corrected some merge errors (a ':w' from vim for example). > > The whole project compiles properly now, and the test suite all pases. > > I have

Re: Release

2012-11-25 Thread Ali Lown
I took another look over the resultant diff and found a few typos from when I corrected some merge errors (a ':w' from vim for example). The whole project compiles properly now, and the test suite all pases. I have committed this as r1413353. Hopefully this is now all of the licensing stuff sorte

Re: Release

2012-11-24 Thread Angus Turner
Ok so infra has basically said the practical answer is to just commit the patch, unless we want to wait for the issue to be fixed, which could be a while. So unless anyone has any problems with that I suggest you just go for it Ali. Thanks Angus Turner angusisf...@gmail.com On Sun, Nov 25, 2012

Re: Release

2012-11-24 Thread Upayavira
sign on to #asfinfra on freenode, and ask there, if you can. Upayavira On Fri, Nov 23, 2012, at 09:10 PM, Angus Turner wrote: > Seems it is indeed something on the reviewboard side. Anyone know where > we > should go with this? > Thanks > Angus Turner > angusisf...@gmail.com > > > On Sat, Nov 2

Re: Release

2012-11-23 Thread Angus Turner
Seems it is indeed something on the reviewboard side. Anyone know where we should go with this? Thanks Angus Turner angusisf...@gmail.com On Sat, Nov 24, 2012 at 7:59 AM, Angus Turner wrote: > Ok all, > I tried contacting infra with no luck, i'm not sure if my message didn't > get through or wh

Re: Release

2012-11-23 Thread Angus Turner
Ok all, I tried contacting infra with no luck, i'm not sure if my message didn't get through or what. I think it might be worth just creating a new review request so i'll try that next. Thanks Angus Turner angusisf...@gmail.com On Mon, Nov 19, 2012 at 10:22 AM, Angus Turner wrote: > I'll leave i

Re: Release

2012-11-18 Thread Angus Turner
I'll leave it for 10 minutes or so and see what happens. Thanks Angus Turner angusisf...@gmail.com On Mon, Nov 19, 2012 at 10:19 AM, Ali Lown wrote: > Timeout related? > > Might it be worth mentioning to infrastructure? > > Ali > > On 18 November 2012 23:17, Angus Turner wrote: > > It's gettin

Re: Release

2012-11-18 Thread Ali Lown
Timeout related? Might it be worth mentioning to infrastructure? Ali On 18 November 2012 23:17, Angus Turner wrote: > It's getting there. It seems a 4.4mb patch breaks the review system though > :) > Thanks > Angus Turner > angusisf...@gmail.com > > > > On Mon, Nov 19, 2012 at 10:04 AM, Angus T

Re: Release

2012-11-18 Thread Angus Turner
It's getting there. It seems a 4.4mb patch breaks the review system though :) Thanks Angus Turner angusisf...@gmail.com On Mon, Nov 19, 2012 at 10:04 AM, Angus Turner wrote: > Great I'll upload it now. > Thanks > Angus Turner > angusisf...@gmail.com > > > > On Mon, Nov 19, 2012 at 10:02 AM, Ali

Re: Release

2012-11-18 Thread Angus Turner
Great I'll upload it now. Thanks Angus Turner angusisf...@gmail.com On Mon, Nov 19, 2012 at 10:02 AM, Ali Lown wrote: > > It might be easier > > to download the patch apply that and create a script that just adds the > > extra * needed everywhere. > > @Angus, do you want to submit the new patch

Re: Release

2012-11-18 Thread Ali Lown
FWDing, back onto the list... On 18 November 2012 20:07, Angus Turner wrote: > Yeah sorry guys this is my bad. > I've been having computer troubles recently with things failing left right > and centre and it seems the script was lost, as it wasn't put into my back > up because at the time I didn't

Re: Release

2012-11-18 Thread Ali Lown
> Are we still stalled on the release process? We appear to be. >The last I remember we were talking about obfuscating third party jars. Are >we still at that point? Yes. Regarding this: it is unclear if we should make the obfuscation part of the normal build process, or only include it in a '

Re: Release Update

2012-09-30 Thread Angus Turner
Oops I thought I did :) My internet has been a bit stuffy lately... Thanks Angus Turner angusisf...@gmail.com On Sun, Sep 30, 2012 at 6:52 PM, Ali Lown wrote: > > The last review for licensing stuff is up, i'd appreciate it if you all > > looked at it and pointed out any errors i've made. > >

Re: Release Update

2012-09-30 Thread Ali Lown
> The last review for licensing stuff is up, i'd appreciate it if you all > looked at it and pointed out any errors i've made. I can't see it in my 'incoming reviews' section. I did find it eventually (https://reviews.apache.org/r/7363/), and it appears you didn't add any groups for the review. I