Updated Status of MINA 2 Space
Finally was able to spend some time with the User Guide. Have managed to migrate most of the pages. The User Guide is mostly complete, just need some glue code work to be done. Shall tryt o finish it ASAP. Haven't migrate some of the pages like IoBuffer and IoHandler that I created with a view to provide an indepth of design. As of now they don't have much useful information. I don't intend to transfer them unless someone feels strongly about it. Do we need to migrate Artwork and Class Diagram pages? Finally getting ready for 2.0 :-) thanks ashish
Re: Updated Status of MINA 2 Space
Le Tue, 23 Feb 2010 16:57:43 +0530, Ashish paliwalash...@gmail.com a écrit : Finally was able to spend some time with the User Guide. Have managed to migrate most of the pages. The User Guide is mostly complete, just need some glue code work to be done. Shall tryt o finish it ASAP. Haven't migrate some of the pages like IoBuffer and IoHandler that I created with a view to provide an indepth of design. As of now they don't have much useful information. I don't intend to transfer them unless someone feels strongly about it. Do we need to migrate Artwork and Class Diagram pages? Finally getting ready for 2.0 :-) thanks ashish On my side I updated main page for adding news, the contact and ML pages Some links in the nav bar need to updated (like issue tracking, testimonials,..) I think artwork can be trashed. If the user guide cover class diagram you can trash it too no ? -- Julien Vermillard Archean Technologies http://www.archean.fr signature.asc Description: PGP signature
Re: Updated Status of MINA 2 Space
On Tue, Feb 23, 2010 at 5:06 PM, Julien Vermillard jvermill...@archean.fr wrote: Le Tue, 23 Feb 2010 16:57:43 +0530, Ashish paliwalash...@gmail.com a écrit : Finally was able to spend some time with the User Guide. Have managed to migrate most of the pages. The User Guide is mostly complete, just need some glue code work to be done. Shall tryt o finish it ASAP. Haven't migrate some of the pages like IoBuffer and IoHandler that I created with a view to provide an indepth of design. As of now they don't have much useful information. I don't intend to transfer them unless someone feels strongly about it. Do we need to migrate Artwork and Class Diagram pages? Finally getting ready for 2.0 :-) thanks ashish On my side I updated main page for adding news, the contact and ML pages Well we started working together :-) I saw ur updates Some links in the nav bar need to updated (like issue tracking, testimonials,..) Yeah that's the next step.. need to work on that I think artwork can be trashed. If the user guide cover class diagram you can trash it too no ? No User Guide doesn't cover this as of now, but it can be placed under MINA Internals section. Just have a cursory look if I have missed something.. thanks ashish
Vote canceled : Re: [Vote] MINA 2.0-GA
Hi guys, I cancel this vote and will relaunch a new one immediately. -- Regards, Cordialement, Emmanuel Lécharny www.nextury.com
[VOTE] Release MINA 2.0 (take 2)
Hi guys, I canceled the previous vote which was not mentionning a svn version. Julien was kin enough to generate jars : http://people.apache.org/~jvermillard/2.0.0-RC2/ (source tarballs are also available). The build is based on svn revision r912511. [ ] +1 Yes, release 2.0 now [ ] +/-0 I have no opinion [ ] -1 No, wait. My vote : +1 Vote is on for 72 hours, up to friday, 3pm Paris time -- Regards, Cordialement, Emmanuel Lécharny www.nextury.com
Re: [VOTE] Release MINA 2.0 (take 2)
+1 Jeff On Feb 23, 2010, at 6:21 AM, Emmanuel Lecharny wrote: Hi guys, I canceled the previous vote which was not mentionning a svn version. Julien was kin enough to generate jars : http://people.apache.org/~jvermillard/2.0.0-RC2/ (source tarballs are also available). The build is based on svn revision r912511. [ ] +1 Yes, release 2.0 now [ ] +/-0 I have no opinion [ ] -1 No, wait. My vote : +1 Vote is on for 72 hours, up to friday, 3pm Paris time -- Regards, Cordialement, Emmanuel Lécharny www.nextury.com
Sshd, FtpServer and Vysper : missing g+w on /www/mina.apache.org
Hi guys, we are unable to update some pages on /www/mina.apache.org because the pages belongs to induvidual (which is normal) but mina group does not have +w rights on them. Can you set your umask to 002 in your .profile, and chmod -R g+w on the directory ? Many thanks ! -- Regards, Cordialement, Emmanuel Lécharny www.nextury.com
Re: [VOTE] Release MINA 2.0 (take 2)
Le Tue, 23 Feb 2010 14:21:29 +0100, Emmanuel Lecharny elecha...@gmail.com a écrit : Hi guys, I canceled the previous vote which was not mentionning a svn version. Julien was kin enough to generate jars : http://people.apache.org/~jvermillard/2.0.0-RC2/ (source tarballs are also available). The build is based on svn revision r912511. [ ] +1 Yes, release 2.0 now [ ] +/-0 I have no opinion [ ] -1 No, wait. My vote : +1 Vote is on for 72 hours, up to friday, 3pm Paris time +1 again -- Julien Vermillard Archean Technologies http://www.archean.fr signature.asc Description: PGP signature
Re: [VOTE] Release MINA 2.0 (take 2)
+1
Re: [VOTE] Release MINA 2.0 (take 2)
On Tue, Feb 23, 2010 at 2:21 PM, Emmanuel Lecharny elecha...@gmail.com wrote: Julien was kin enough to generate jars : http://people.apache.org/~jvermillard/2.0.0-RC2/ The source in these packages are not buildable with Maven, due to the module paths in the root POM and the directories for the modules not matching. For example, there is no legal module and the parent module is in a mina-parent directory. Is this the same source packages as we plan to release? /niklas
Re: Sshd, FtpServer and Vysper : missing g+w on /www/mina.apache.org
On Tue, Feb 23, 2010 at 3:02 PM, Emmanuel Lecharny elecha...@gmail.com wrote: we are unable to update some pages on /www/mina.apache.org because the pages belongs to induvidual (which is normal) but mina group does not have +w rights on them. Can you set your umask to 002 in your .profile, and chmod -R g+w on the directory ? Done for ftpserver and vysper. But, I already got umask 002 set in my .profile (and my .bashrc just to make sure) and have for a long time, still I get this problem over and over again. Anyone got any clue? /niklas
Re: [VOTE] Release MINA 2.0 (take 2)
On 2/23/10 5:25 PM, Niklas Gustavsson wrote: On Tue, Feb 23, 2010 at 2:21 PM, Emmanuel Lecharnyelecha...@gmail.com wrote: Julien was kin enough to generate jars : http://people.apache.org/~jvermillard/2.0.0-RC2/ The source in these packages are not buildable with Maven, due to the module paths in the root POM and the directories for the modules not matching. For example, there is no legal module and the parent module is in a mina-parent directory. Is this the same source packages as we plan to release? Pakages are just provided for convenience. Please check out the sources from trunk, revision r912511, if you want to build the project and test the binaries. -- Regards, Cordialement, Emmanuel Lécharny www.nextury.com
Re: Sshd, FtpServer and Vysper : missing g+w on /www/mina.apache.org
On 2/23/10 5:31 PM, Niklas Gustavsson wrote: On Tue, Feb 23, 2010 at 3:02 PM, Emmanuel Lecharnyelecha...@gmail.com wrote: we are unable to update some pages on /www/mina.apache.org because the pages belongs to induvidual (which is normal) but mina group does not have +w rights on them. Can you set your umask to 002 in your .profile, and chmod -R g+w on the directory ? Done for ftpserver and vysper. But, I already got umask 002 set in my .profile (and my .bashrc just to make sure) and have for a long time, still I get this problem over and over again. Anyone got any clue? I *think* there might be a problem with the script that does a rsync from the server where the wiki is exported. To be checked... -- Regards, Cordialement, Emmanuel Lécharny www.nextury.com
Re: Sshd, FtpServer and Vysper : missing g+w on /www/mina.apache.org
On Tue, Feb 23, 2010 at 5:52 PM, Emmanuel Lécharny elecha...@apache.org wrote: I *think* there might be a problem with the script that does a rsync from the server where the wiki is exported. To be checked... The scripts run in my crontab and looks like: 0 * * * * (/usr/local/bin/rsync -r /www/confluence-exports/FTPSERVER/ /www/mina.apache.org/ftpserver/) 0 * * * * (/usr/local/bin/rsync -r /www/confluence-exports/VYSPER/ /www/mina.apache.org/vysper/) /niklas
Re: [VOTE] Release MINA 2.0 (take 2)
On Tue, Feb 23, 2010 at 5:34 PM, Emmanuel Lécharny elecha...@apache.org wrote: Pakages are just provided for convenience. Please check out the sources from trunk, revision r912511, if you want to build the project and test the binaries. My problem is not really building MINA, I just want to make sure that this is not a problem that our users that download source packages from the 2.0 release will have :-) /niklas
Re: [VOTE] Release MINA 2.0 (take 2)
On Feb 23, 2010, at 8:34 AM, Emmanuel Lécharny wrote: On 2/23/10 5:25 PM, Niklas Gustavsson wrote: On Tue, Feb 23, 2010 at 2:21 PM, Emmanuel Lecharnyelecha...@gmail.com wrote: Julien was kin enough to generate jars : http://people.apache.org/~jvermillard/2.0.0-RC2/ The source in these packages are not buildable with Maven, due to the module paths in the root POM and the directories for the modules not matching. For example, there is no legal module and the parent module is in a mina-parent directory. Is this the same source packages as we plan to release? Pakages are just provided for convenience. Please check out the sources from trunk, revision r912511, if you want to build the project and test the binaries. I'm new here so I'm going to ask what might be an obvious question. Is this the way you usually do releases here in Mina? Seems quite odd to me. Regards, Alan
Re: [VOTE] Release MINA 2.0 (take 2)
Le Tue, 23 Feb 2010 09:37:37 -0800, Alan D. Cabrera l...@toolazydogs.com a écrit : On Feb 23, 2010, at 8:34 AM, Emmanuel Lécharny wrote: On 2/23/10 5:25 PM, Niklas Gustavsson wrote: On Tue, Feb 23, 2010 at 2:21 PM, Emmanuel Lecharnyelecha...@gmail.com wrote: Julien was kin enough to generate jars : http://people.apache.org/~jvermillard/2.0.0-RC2/ The source in these packages are not buildable with Maven, due to the module paths in the root POM and the directories for the modules not matching. For example, there is no legal module and the parent module is in a mina-parent directory. Is this the same source packages as we plan to release? Pakages are just provided for convenience. Please check out the sources from trunk, revision r912511, if you want to build the project and test the binaries. I'm new here so I'm going to ask what might be an obvious question. Is this the way you usually do releases here in Mina? Seems quite odd to me. Regards, Alan Before we used to start a vote on trunk :) -- Julien Vermillard Archean Technologies http://www.archean.fr signature.asc Description: PGP signature
Re: Sshd, FtpServer and Vysper : missing g+w on /www/mina.apache.org
On 2/23/10 6:06 PM, Niklas Gustavsson wrote: On Tue, Feb 23, 2010 at 5:52 PM, Emmanuel Lécharnyelecha...@apache.org wrote: I *think* there might be a problem with the script that does a rsync from the server where the wiki is exported. To be checked... The scripts run in my crontab and looks like: 0 * * * * (/usr/local/bin/rsync -r /www/confluence-exports/FTPSERVER/ /www/mina.apache.org/ftpserver/) 0 * * * * (/usr/local/bin/rsync -r /www/confluence-exports/VYSPER/ /www/mina.apache.org/vysper/) /niklas We should create real scrips in /www/mina.apache.org, and use them in crontab. We also have to add this line in the script : /bin/chmod -R g+w /www/mina.apache.org/ Maybe someone from infra can find a better solution. -- Regards, Cordialement, Emmanuel Lécharny www.nextury.com
Re: [VOTE] Release MINA 2.0 (take 2)
On 2/23/10 6:24 PM, Niklas Gustavsson wrote: On Tue, Feb 23, 2010 at 5:34 PM, Emmanuel Lécharnyelecha...@apache.org wrote: Pakages are just provided for convenience. Please check out the sources from trunk, revision r912511, if you want to build the project and test the binaries. My problem is not really building MINA, I just want to make sure that this is not a problem that our users that download source packages from the 2.0 release will have :-) HMMM. Not sure I don't grok the sentence... Can you rephrase in smaller chunks so that I can see where you see a potential problem ? Thanks ! -- Regards, Cordialement, Emmanuel Lécharny www.nextury.com
Re: [VOTE] Release MINA 2.0 (take 2)
On Tue, Feb 23, 2010 at 6:46 PM, Emmanuel Lécharny elecha...@apache.org wrote: My problem is not really building MINA, I just want to make sure that this is not a problem that our users that download source packages from the 2.0 release will have :-) HMMM. Not sure I don't grok the sentence... Can you rephrase in smaller chunks so that I can see where you see a potential problem ? I'll try to rephrase. How will the source packages that will be MINA 2.0 look like? Will they be like the one on this vote (which is not buildable) or in some other structure? If they different, could we please vote on the real release artifacts? Otherwise, it's hard to review them. I could of course only vote on the code, but I think it's a good thing for us to also review the actual release artifacts, not knowing exactly how the guy building the release will do them (for example, these tar balls does not look like something that came out of mvn assembly:assembly). /niklas
Re: [VOTE] Release MINA 2.0 (take 2)
On Tue, Feb 23, 2010 at 6:48 PM, Emmanuel Lecharny elecha...@gmail.com wrote: base line : we vote code, not binaries (this is ASF). We could branch a release, and vote the branch, assuming that once generated, we would move the branch in tags, or delete it if we rollback the vote. Or we can vote a revision, and provide builded packages, for those who don't want to build them. Personally, I prefer to branch before the release (that way we can change the POM versions and get a real release build to vote on). And, as mentioned in my other email, I find it very useful to have real release binaries to vote on, in addition to the code (which is obviously our ultimate release). I also think we should look into using Nexus and staging (for the next release, this one is already overdue) to slim down the procedure even more. /niklas
Re: [VOTE] Release MINA 2.0 (take 2)
On 2/23/10 6:53 PM, Niklas Gustavsson wrote: On Tue, Feb 23, 2010 at 6:46 PM, Emmanuel Lécharnyelecha...@apache.org wrote: My problem is not really building MINA, I just want to make sure that this is not a problem that our users that download source packages from the 2.0 release will have :-) HMMM. Not sure I don't grok the sentence... Can you rephrase in smaller chunks so that I can see where you see a potential problem ? I'll try to rephrase. How will the source packages that will be MINA 2.0 look like? Will they be like the one on this vote (which is not buildable) or in some other structure? If they different, could we please vote on the real release artifacts? Otherwise, it's hard to review them. I could of course only vote on the code, but I think it's a good thing for us to also review the actual release artifacts, not knowing exactly how the guy building the release will do them (for example, these tar balls does not look like something that came out of mvn assembly:assembly). Got it. Let's then branch a 2.0.0 version, and build the packages from it. There is also one thing we should do, follow the ASF rule : Every ASF release *must* contain a source package, which must be sufficient for a user to build and test the release provided they have access to the appropriate platform and tools If the source tar ball is not buildable, then we have a problem. We may have to assign a RM at some point (and it won't be me ;) -- Regards, Cordialement, Emmanuel Lécharny www.nextury.com
Re: [VOTE] Release MINA 2.0 (take 2)
Le Tue, 23 Feb 2010 18:53:37 +0100, Niklas Gustavsson nik...@protocol7.com a écrit : (for example, these tar balls does not look like something that came out of mvn assembly:assembly). Well it is. I did : mvn -Dwith-LGPL-dependencies package assembly:assembly The release process is documented in the wiki you can try it. Apparently the legal module is explicitly excluded of the packaging. And svn blame says it's all Alex fault :) If we reintroduce this module, the tarball will be maven buildable. -- Julien Vermillard Archean Technologies http://www.archean.fr signature.asc Description: PGP signature
Hudson build is still unstable: MINA-tru nk-jdk1.6-windows » Apache MINA Core #16
See http://hudson.zones.apache.org/hudson/job/MINA-trunk-jdk1.6-windows/org.apache.mina$mina-core/changes
Hudson build is still unstable: MINA-trunk-jdk1.6-windows #16
See http://hudson.zones.apache.org/hudson/job/MINA-trunk-jdk1.6-windows/changes
Re: [VOTE] Release MINA 2.0 (take 2)
On Tue, Feb 23, 2010 at 7:24 PM, Julien Vermillard jvermill...@archean.fr wrote: (for example, these tar balls does not look like something that came out of mvn assembly:assembly). Well it is. If so, I think our build is broken, maybe due to not having module artifactIds and module directory names matching. If we reintroduce this module, the tarball will be maven buildable. Great! But, are you sure, for example, the core module is known to Maven as located in a core directory, but the assembly seems to have put it in a mina-core directory. /niklas
Re: Sshd, FtpServer and Vysper : missing g+w on /www/mina.apache.org
On Tue, Feb 23, 2010 at 6:44 PM, Emmanuel Lécharny elecha...@apache.org wrote: We should create real scrips in /www/mina.apache.org, and use them in crontab. We're using the documented solution for doing this: http://cwiki.apache.org/CWIKI/#Index-Canweusetheautoexportsiteaspartofourmainwebsite%253F In the Can we use the autoexport site as part of our main web site? section. We also have to add this line in the script : /bin/chmod -R g+w /www/mina.apache.org/ I can surely add this to the script, but I'm wondering if the problem might not be with some setting on the parent directory making the access rights not correctly set. But, then again, all this umask stuff is magic to me :-) /niklas
Re: Sshd, FtpServer and Vysper : missing g+w on /www/mina.apache.org
Le Tue, 23 Feb 2010 21:05:50 +0100, Niklas Gustavsson nik...@protocol7.com a écrit : On Tue, Feb 23, 2010 at 6:44 PM, Emmanuel Lécharny elecha...@apache.org wrote: We should create real scrips in /www/mina.apache.org, and use them in crontab. We're using the documented solution for doing this: http://cwiki.apache.org/CWIKI/#Index-Canweusetheautoexportsiteaspartofourmainwebsite%253F In the Can we use the autoexport site as part of our main web site? section. We also have to add this line in the script : /bin/chmod -R g+w /www/mina.apache.org/ I can surely add this to the script, but I'm wondering if the problem might not be with some setting on the parent directory making the access rights not correctly set. But, then again, all this umask stuff is magic to me :-) /niklas I think the problem is due to cron not running the .profile before running the rsync -- Julien Vermillard Archean Technologies http://www.archean.fr signature.asc Description: PGP signature
