Re: Launchpad 7 Release?
2014-09-30 15:23 GMT+02:00 Robert Munteanu rob...@lmn.ro: So now the scripting.java release is complete. It's sort of funny that I proposed waiting for it but in the end there was no need for that since it's not part of the launchpad :-) :) I've removed oak and all runModes from the launchpad in https://svn.apache.org/r1628432 . So I guess we're good to go. I have no idea what should happen now, but if anyone does the road is clear. The next step is releasing the builder project as 7 - once the vote is through we have to manually update the api javadocs. Carsten
Re: Launchpad 7 Release?
So now the scripting.java release is complete. It's sort of funny that I proposed waiting for it but in the end there was no need for that since it's not part of the launchpad :-) I've removed oak and all runModes from the launchpad in https://svn.apache.org/r1628432 . So I guess we're good to go. I have no idea what should happen now, but if anyone does the road is clear. Robert On Sat, Sep 27, 2014 at 6:39 PM, Carsten Ziegeler cziege...@apache.org wrote: Awesome! No, I don't think that there is anything missing and yes it makes sense to wait for the scripting.java release Regards Carsten 2014-09-26 21:59 GMT+02:00 Robert Munteanu romb...@apache.org: And after three weeks more - the oak.server bundle is the only one left with a SNAPSHOT version - we have a release in process for org.apache.sling.scripting.java 2.0.12 which looks important I think it's a good idea to wait for that release to be done ( earliest on Monday afternoon ) and then remove oak + the two run modes from the launchpad and starting the release process for the 7 version. Thoughts? Are we still missing something for the 7 release? Robert On Wed, Sep 3, 2014 at 4:31 PM, Robert Munteanu romb...@apache.org wrote: Just as a follow-up three weeks later - the build works fine with Java 8 ( as a matter of fact, all sling-trunk builds now pass ) - there are 15 SNAPSHOT bundles referenced in the launchpad - we decided to remove Oak support ( 1 SNAPSHOT bundle less ) , tracked under [1] - the oak support task is the only one blocking the 'release task' [2] So the work to be done is releasing those bundles and removing Oak support. If there's additional work to be done, please file new bugs blocking [2] . And help with releasing bundles is always appreciated :-) Robert [1]: https://issues.apache.org/jira/browse/SLING-3907 [2]: https://issues.apache.org/jira/browse/SLING-3810 On Tue, Aug 5, 2014 at 10:09 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi Oliver, On Tue, Aug 5, 2014 at 8:57 AM, Oliver Lietz apa...@oliverlietz.de wrote: ...https://github.com/oliverlietz/sling-tests Was an easier and faster way for me to create tests with Pax Exam and Karaf instead of learning the Sling test stuff spread in different bundles in the repo. Should be easy for me to recreate them in launchpad/integration-tests when I'm done with SLING-3821 Ok, fair enough - what's important IMO is to run the exact same integration tests suite in all environments, that is launchpad/integration-tests. Note that those require the launchpad/test-services bundle. -Bertrand -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org -- Sent from my (old) computer
Re: Launchpad 7 Release?
On Tue, Sep 30, 2014 at 4:28 PM, Carsten Ziegeler cziege...@apache.org wrote: So I guess we're good to go. I have no idea what should happen now, but if anyone does the road is clear. The next step is releasing the builder project as 7 - once the vote is through we have to manually update the api javadocs. OK, I started the release vote for builder 7. We'll see about updating the javadocs when the release is done. Robert
Re: Launchpad 7 Release?
And after three weeks more - the oak.server bundle is the only one left with a SNAPSHOT version - we have a release in process for org.apache.sling.scripting.java 2.0.12 which looks important I think it's a good idea to wait for that release to be done ( earliest on Monday afternoon ) and then remove oak + the two run modes from the launchpad and starting the release process for the 7 version. Thoughts? Are we still missing something for the 7 release? Robert On Wed, Sep 3, 2014 at 4:31 PM, Robert Munteanu romb...@apache.org wrote: Just as a follow-up three weeks later - the build works fine with Java 8 ( as a matter of fact, all sling-trunk builds now pass ) - there are 15 SNAPSHOT bundles referenced in the launchpad - we decided to remove Oak support ( 1 SNAPSHOT bundle less ) , tracked under [1] - the oak support task is the only one blocking the 'release task' [2] So the work to be done is releasing those bundles and removing Oak support. If there's additional work to be done, please file new bugs blocking [2] . And help with releasing bundles is always appreciated :-) Robert [1]: https://issues.apache.org/jira/browse/SLING-3907 [2]: https://issues.apache.org/jira/browse/SLING-3810 On Tue, Aug 5, 2014 at 10:09 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi Oliver, On Tue, Aug 5, 2014 at 8:57 AM, Oliver Lietz apa...@oliverlietz.de wrote: ...https://github.com/oliverlietz/sling-tests Was an easier and faster way for me to create tests with Pax Exam and Karaf instead of learning the Sling test stuff spread in different bundles in the repo. Should be easy for me to recreate them in launchpad/integration-tests when I'm done with SLING-3821 Ok, fair enough - what's important IMO is to run the exact same integration tests suite in all environments, that is launchpad/integration-tests. Note that those require the launchpad/test-services bundle. -Bertrand
Re: Launchpad 7 Release?
Just as a follow-up three weeks later - the build works fine with Java 8 ( as a matter of fact, all sling-trunk builds now pass ) - there are 15 SNAPSHOT bundles referenced in the launchpad - we decided to remove Oak support ( 1 SNAPSHOT bundle less ) , tracked under [1] - the oak support task is the only one blocking the 'release task' [2] So the work to be done is releasing those bundles and removing Oak support. If there's additional work to be done, please file new bugs blocking [2] . And help with releasing bundles is always appreciated :-) Robert [1]: https://issues.apache.org/jira/browse/SLING-3907 [2]: https://issues.apache.org/jira/browse/SLING-3810 On Tue, Aug 5, 2014 at 10:09 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi Oliver, On Tue, Aug 5, 2014 at 8:57 AM, Oliver Lietz apa...@oliverlietz.de wrote: ...https://github.com/oliverlietz/sling-tests Was an easier and faster way for me to create tests with Pax Exam and Karaf instead of learning the Sling test stuff spread in different bundles in the repo. Should be easy for me to recreate them in launchpad/integration-tests when I'm done with SLING-3821 Ok, fair enough - what's important IMO is to run the exact same integration tests suite in all environments, that is launchpad/integration-tests. Note that those require the launchpad/test-services bundle. -Bertrand
Re: Launchpad 7 Release?
On Wednesday 23 July 2014 08:24:35 Bertrand Delacretaz wrote: On Tue, Jul 22, 2014 at 10:33 PM, Oliver Lietz apa...@oliverlietz.de wrote: On Tuesday 22 July 2014 13:30:59 Bertrand Delacretaz wrote: ...Are you planning to setup integration tests for that Karaf-based launcher? Sure. There are already basic bootstrap tests which check if the required bundles are available and active in org.apache.sling.launchpad.karaf- integration-tests and also some extended tests which check for services and nodes in the repository... Sorry my question was unclear - are you planning to run the launchpad/integration-tests on the Karaf-based launcher? So that the same test suite is used for that and for the launchpad. SLING-3821 - some tests fail simply because required bundles are not present. I will add more bundles/features in the next days to fix them and come to you for some other failing tests as I'm not that familiar with the Sling test stuff. And there is sling-tests on GitHub. Where exactly? Not sure what that is. https://github.com/oliverlietz/sling-tests Was an easier and faster way for me to create tests with Pax Exam and Karaf instead of learning the Sling test stuff spread in different bundles in the repo. Should be easy for me to recreate them in launchpad/integration-tests when I'm done with SLING-3821. O. -Bertrand
Re: Launchpad 7 Release?
Hi Oliver, On Tue, Aug 5, 2014 at 8:57 AM, Oliver Lietz apa...@oliverlietz.de wrote: ...https://github.com/oliverlietz/sling-tests Was an easier and faster way for me to create tests with Pax Exam and Karaf instead of learning the Sling test stuff spread in different bundles in the repo. Should be easy for me to recreate them in launchpad/integration-tests when I'm done with SLING-3821 Ok, fair enough - what's important IMO is to run the exact same integration tests suite in all environments, that is launchpad/integration-tests. Note that those require the launchpad/test-services bundle. -Bertrand
Re: Launchpad 7 Release?
On Mon, Jul 28, 2014 at 6:40 PM, Oliver Lietz apa...@oliverlietz.de wrote: ...users also expect a major release to be stable. Something they can build on... Once we release 7 it should be much easier to release 7.1. If it hurts, do it more ;-) ...Can you create a wiki page with tasks to be done or tag issues which need to be fixed for 7 so every developer can pick from?... I have created SLING-3810 for the Sling 7 release, please create issues that block it for things that must be done before the release. -Bertrand
Re: Launchpad 7 Release?
On Mon, Jul 28, 2014 at 7:40 PM, Oliver Lietz apa...@oliverlietz.de wrote: I looked in Jira for related issues but found nothing [1] . What are we missing for Java 8? trunk doesn't compile with Java 8 (test failures, ASM issue). Can you set up a build job for trunk with 8? I've set up [1] . So far I see classes sets of failures - scr-maven-plugin fails due to not supporting Java 8, should be fixed by releasing/adopting latest parent pom. I'll start a release vote for that. - Pax-Exam failures dues to missing packages ; not sure yet why that happens Robert [1]: https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.8/ -- Sent from my (old) computer
Re: Launchpad 7 Release?
Hi Am 29.07.2014 um 10:00 schrieb Bertrand Delacretaz bdelacre...@apache.org: On Mon, Jul 28, 2014 at 6:40 PM, Oliver Lietz apa...@oliverlietz.de wrote: ...users also expect a major release to be stable. Something they can build on... Once we release 7 it should be much easier to release 7.1. If it hurts, do it more ;-) That would be 8 :-) Also, apart from the contents discussion, one thing which held us back releasing the Sling App for a long time is the way how we intended to do the release: creating a tagged SVN structure of all the module sources contained in the release which is tedious and error prone. I think a Sling App Release artifacts are just a service to the community and the source of the release really just is the contents descriptor. This also makes releasing a lot easier and more straightforward. Regards Felix
Re: Launchpad 7 Release?
Hi Felix, On Tue, Jul 29, 2014 at 10:25 AM, Felix Meschberger fmesc...@adobe.com wrote: ...I think a Sling App Release artifacts are just a service to the community and the source of the release really just is the contents descriptor I don't understand - do you mean that we should just tag and release the launchpad/builder source code? If yes, I agree - as long as its bundle list doesn't reference snapshots (I forgot if Maven is aware of snapshots in there) that's fine. -Bertrand
Re: Launchpad 7 Release?
Hi Am 29.07.2014 um 10:31 schrieb Bertrand Delacretaz bdelacre...@apache.org: Hi Felix, On Tue, Jul 29, 2014 at 10:25 AM, Felix Meschberger fmesc...@adobe.com wrote: ...I think a Sling App Release artifacts are just a service to the community and the source of the release really just is the contents descriptor I don't understand - do you mean that we should just tag and release the launchpad/builder source code? If yes, I agree - as long as its bundle list doesn't reference snapshots (I forgot if Maven is aware of snapshots in there) that's fine. Yes, that's what I mean. Regards Felix
Re: Launchpad 7 Release?
On Mon, Jul 28, 2014 at 7:40 PM, Oliver Lietz apa...@oliverlietz.de wrote: - SLING-3008 looks still problematic Is the issue that we have a code block that can be removed? I don't see that as a launchpad release blocker. The problem is an incompatible JSON response due to this code block which I noticed when querying users. It may happen else where. As this is part of a released bundle, please file a new Jira to get it fixed. Robert -- Sent from my (old) computer
Re: Launchpad 7 Release?
On Sun, Jul 27, 2014 at 1:09 PM, Oliver Lietz apa...@oliverlietz.de wrote: On Wednesday 23 July 2014 08:04:00 Carsten Ziegeler wrote: 2014-07-22 23:12 GMT+02:00 Oliver Lietz apa...@oliverlietz.de: +1, I think it's important to have a Sling 7 release soon. Yes, but not a half-baked one. We would have even more users complainig about 7 as we now have with 6. Well, which part do you think would be half-baked if we simply release everything as is. I think most of the bundles (if not all) are in a pretty good shape right now. Sorry if it sounded to harsh. Some points which come to my mind: - we don't have full support for Java 8 I looked in Jira for related issues but found nothing [1] . What are we missing for Java 8? - SLING-3575 failing test with newer Jackrabbit It would be good if you added more details about the test failure to the issue. This would allow others beside the issue reporter to chime in and maybe propose a fix. - the versions of Commons Threads for the Event bundle used at compile and runtime are not compatible I'm not sure what the problem is here. In launchpad/builder/src/main/bundles/list.xml I see bundle groupIdorg.apache.sling/groupId artifactIdorg.apache.sling.commons.threads/artifactId version3.2.0/version /bundle bundle groupIdorg.apache.sling/groupId artifactIdorg.apache.sling.event/artifactId version3.3.10/version /bundle And in bundles/extensions/event/pom.xml dependency groupIdorg.apache.sling/groupId artifactIdorg.apache.sling.commons.threads/artifactId version3.1.0/version scopeprovided/scope /dependency I don't see any incompatibilities in there. In any case, if you see problems related to that setup please file a Jira with an explanation so that it's not forgotten in this email thread. - SLING-3008 looks still problematic Is the issue that we have a code block that can be removed? I don't see that as a launchpad release blocker. - lack of documentation, major changes between 6 and 7, upgrade paths That sounds like a general issue that I agree with. But then again, not releasing while waiting for documentation is not bringing any value IMO. What's important is that we get a release which supports non-ancient Java versions out for developers to try out. We can talk later when we have people complaining about upgrade paths :-) . In my (limited) experience, people build their own bundle lists anyway, the launchpad is just a way to quickly get one's hands dirty with Sling. - Oak integration not on par with Jackrabbit (failing tests) Right, at the moment we have two failing ITs for Oak ( [2] ). However, we can simply release with Jackrabbit as the default runmode, and look into those later. I don't see any real value in releasing a *major* 7 now as is and then plan any future releases and how to improve the release process. If it takes even more time to get a major release out which can be used as good basis for future releases than so it be even if it takes more weeks or months. If the effort for releasing major versions is to high we should maybe switch to a rolling release model where we maintain a list with released and compatible bundles. We can discuss that for Launchpad 8 or 7.1 or 2014.1 or whatever we decide to call it. But I think it's important to get version 7 out as soon as we can. Thanks, Robert [1]: https://issues.apache.org/jira/issues/?jql=project%20%3D%20SLING%20AND%20text%20~%20%22java%208%22%20and%20resolution%20is%20empty [2]: https://builds.apache.org/view/S-Z/view/Sling/job/sling-oak-it-1.6/ Regards, O. Carsten I haven't checked the SNAPSHOT bundles, but I think there are some bundles where nothing changed after their latest release so we may use some already released bundles and not release *all* now. there are probaly less than 20 bundles. In theory, the list.xml should only reference snapshots which have actually changes. But I'll check this today to see where we are. Carsten
Re: Launchpad 7 Release?
On Monday 28 July 2014 14:56:03 Robert Munteanu wrote: On Sun, Jul 27, 2014 at 1:09 PM, Oliver Lietz apa...@oliverlietz.de wrote: On Wednesday 23 July 2014 08:04:00 Carsten Ziegeler wrote: 2014-07-22 23:12 GMT+02:00 Oliver Lietz apa...@oliverlietz.de: +1, I think it's important to have a Sling 7 release soon. Yes, but not a half-baked one. We would have even more users complainig about 7 as we now have with 6. Well, which part do you think would be half-baked if we simply release everything as is. I think most of the bundles (if not all) are in a pretty good shape right now. Sorry if it sounded to harsh. Some points which come to my mind: - we don't have full support for Java 8 hi Robert, I looked in Jira for related issues but found nothing [1] . What are we missing for Java 8? trunk doesn't compile with Java 8 (test failures, ASM issue). Can you set up a build job for trunk with 8? - SLING-3575 failing test with newer Jackrabbit It would be good if you added more details about the test failure to the issue. This would allow others beside the issue reporter to chime in and maybe propose a fix. please see also the latest comments in SLING-3479 - the versions of Commons Threads for the Event bundle used at compile and runtime are not compatible I'm not sure what the problem is here. In launchpad/builder/src/main/bundles/list.xml I see bundle groupIdorg.apache.sling/groupId artifactIdorg.apache.sling.commons.threads/artifactId version3.2.0/version /bundle bundle groupIdorg.apache.sling/groupId artifactIdorg.apache.sling.event/artifactId version3.3.10/version /bundle And in bundles/extensions/event/pom.xml dependency groupIdorg.apache.sling/groupId artifactIdorg.apache.sling.commons.threads/artifactId version3.1.0/version scopeprovided/scope /dependency I don't see any incompatibilities in there. In any case, if you see problems related to that setup please file a Jira with an explanation so that it's not forgotten in this email thread. I will have a look after my holidays. - SLING-3008 looks still problematic Is the issue that we have a code block that can be removed? I don't see that as a launchpad release blocker. The problem is an incompatible JSON response due to this code block which I noticed when querying users. It may happen else where. - lack of documentation, major changes between 6 and 7, upgrade paths That sounds like a general issue that I agree with. But then again, not releasing while waiting for documentation is not bringing any value IMO. What's important is that we get a release which supports non-ancient Java versions out for developers to try out. We can talk later when we have people complaining about upgrade paths :-) . In my (limited) experience, people build their own bundle lists anyway, the launchpad is just a way to quickly get one's hands dirty with Sling. Yes. But users also expect a major release to be stable. Something they can build on. - Oak integration not on par with Jackrabbit (failing tests) Right, at the moment we have two failing ITs for Oak ( [2] ). However, we can simply release with Jackrabbit as the default runmode, and look into those later. Please search for JackrabbitOnly.class which will bring up several more tests which are disabled for Oak. I don't see any real value in releasing a *major* 7 now as is and then plan any future releases and how to improve the release process. If it takes even more time to get a major release out which can be used as good basis for future releases than so it be even if it takes more weeks or months. If the effort for releasing major versions is to high we should maybe switch to a rolling release model where we maintain a list with released and compatible bundles. We can discuss that for Launchpad 8 or 7.1 or 2014.1 or whatever we decide to call it. But I think it's important to get version 7 out as soon as we can. Can you create a wiki page with tasks to be done or tag issues which need to be fixed for 7 so every developer can pick from? Thanks, O. Thanks, Robert [1]: https://issues.apache.org/jira/issues/?jql=project%20%3D%20SLING%20AND%20t ext%20~%20%22java%208%22%20and%20resolution%20is%20empty [2]: https://builds.apache.org/view/S-Z/view/Sling/job/sling-oak-it-1.6/ Regards, O. Carsten I haven't checked the SNAPSHOT bundles, but I think there are some bundles where nothing changed after their latest release so we may use some already released bundles and not release *all* now. there are probaly less than 20 bundles. In theory, the list.xml should only reference snapshots which have actually changes. But I'll check this today to see where we are.
Re: Launchpad 7 Release?
On Wednesday 23 July 2014 08:04:00 Carsten Ziegeler wrote: 2014-07-22 23:12 GMT+02:00 Oliver Lietz apa...@oliverlietz.de: +1, I think it's important to have a Sling 7 release soon. Yes, but not a half-baked one. We would have even more users complainig about 7 as we now have with 6. Well, which part do you think would be half-baked if we simply release everything as is. I think most of the bundles (if not all) are in a pretty good shape right now. Sorry if it sounded to harsh. Some points which come to my mind: - we don't have full support for Java 8 - SLING-3575 failing test with newer Jackrabbit - the versions of Commons Threads for the Event bundle used at compile and runtime are not compatible - SLING-3008 looks still problematic - lack of documentation, major changes between 6 and 7, upgrade paths - Oak integration not on par with Jackrabbit (failing tests) I don't see any real value in releasing a *major* 7 now as is and then plan any future releases and how to improve the release process. If it takes even more time to get a major release out which can be used as good basis for future releases than so it be even if it takes more weeks or months. If the effort for releasing major versions is to high we should maybe switch to a rolling release model where we maintain a list with released and compatible bundles. Regards, O. Carsten I haven't checked the SNAPSHOT bundles, but I think there are some bundles where nothing changed after their latest release so we may use some already released bundles and not release *all* now. there are probaly less than 20 bundles. In theory, the list.xml should only reference snapshots which have actually changes. But I'll check this today to see where we are. Carsten
RE: Launchpad 7 Release?
-Original Message- From: Carsten Ziegeler [mailto:cziege...@apache.org] Sent: Wednesday, July 23, 2014 9:22 AM To: dev@sling.apache.org Subject: Re: Launchpad 7 Release? I've updated the bundle list - it was pretty current. For three bundles we still have open issues before we can release: Commons JSON https://issues.apache.org/jira/browse/SLING/fixforversion/12315999 Explorer https://issues.apache.org/jira/browse/SLING/fixforversion/12316190 JCR Jackrabbit Server https://issues.apache.org/jira/browse/SLING/fixforversion/12324840 I would like to include a 1.0.0 release of resourceaccesssecurity in Sling 7. I think it's pretty mature, documentation is up to date [1] and I recently Added a bunch of various tests. WDYT? Best regards mike
Re: Launchpad 7 Release?
2014-07-22 23:12 GMT+02:00 Oliver Lietz apa...@oliverlietz.de: +1, I think it's important to have a Sling 7 release soon. Yes, but not a half-baked one. We would have even more users complainig about 7 as we now have with 6. Well, which part do you think would be half-baked if we simply release everything as is. I think most of the bundles (if not all) are in a pretty good shape right now. Carsten I haven't checked the SNAPSHOT bundles, but I think there are some bundles where nothing changed after their latest release so we may use some already released bundles and not release *all* now. there are probaly less than 20 bundles. In theory, the list.xml should only reference snapshots which have actually changes. But I'll check this today to see where we are. Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Re: Launchpad 7 Release?
On Tue, Jul 22, 2014 at 10:33 PM, Oliver Lietz apa...@oliverlietz.de wrote: On Tuesday 22 July 2014 13:30:59 Bertrand Delacretaz wrote: ...Are you planning to setup integration tests for that Karaf-based launcher? Sure. There are already basic bootstrap tests which check if the required bundles are available and active in org.apache.sling.launchpad.karaf- integration-tests and also some extended tests which check for services and nodes in the repository... Sorry my question was unclear - are you planning to run the launchpad/integration-tests on the Karaf-based launcher? So that the same test suite is used for that and for the launchpad. And there is sling-tests on GitHub. Where exactly? Not sure what that is. -Bertrand
Re: Launchpad 7 Release?
I've updated the bundle list - it was pretty current. For three bundles we still have open issues before we can release: Commons JSON https://issues.apache.org/jira/browse/SLING/fixforversion/12315999 Explorer https://issues.apache.org/jira/browse/SLING/fixforversion/12316190 JCR Jackrabbit Server https://issues.apache.org/jira/browse/SLING/fixforversion/12324840 2014-07-23 8:24 GMT+02:00 Bertrand Delacretaz bdelacre...@apache.org: On Tue, Jul 22, 2014 at 10:33 PM, Oliver Lietz apa...@oliverlietz.de wrote: On Tuesday 22 July 2014 13:30:59 Bertrand Delacretaz wrote: ...Are you planning to setup integration tests for that Karaf-based launcher? Sure. There are already basic bootstrap tests which check if the required bundles are available and active in org.apache.sling.launchpad.karaf- integration-tests and also some extended tests which check for services and nodes in the repository... Sorry my question was unclear - are you planning to run the launchpad/integration-tests on the Karaf-based launcher? So that the same test suite is used for that and for the launchpad. And there is sling-tests on GitHub. Where exactly? Not sure what that is. -Bertrand -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Re: Launchpad 7 Release?
On Wed, Jul 23, 2014 at 10:21 AM, Carsten Ziegeler cziege...@apache.org wrote: I've updated the bundle list - it was pretty current. For three bundles we still have open issues before we can release: Explorer https://issues.apache.org/jira/browse/SLING/fixforversion/12316190 One open issue, very generic, called 'jQuery JCR Explorer - step 2'. Also no code changes since 2012. I think we can release this one as-is. Robert
Re: Launchpad 7 Release?
On Wed, Jul 23, 2014 at 9:21 AM, Carsten Ziegeler cziege...@apache.org wrote: ...For three bundles we still have open issues before we can release: Commons JSON https://issues.apache.org/jira/browse/SLING/fixforversion/12315999 SLING-3786 does not fix anything, it's just refactoring/testing so it's fine to defer it if convenient. -Bertrand
Re: Launchpad 7 Release?
just my 2c, but before releasing 7 it would be a good idea to make sure all tutorials and samples are correctly working as well. I took a quick look at espblog and was not able to get it to run with launchpad 7 Ruben On 7/22/2014 11:04 PM, Carsten Ziegeler wrote: 2014-07-22 23:12 GMT+02:00 Oliver Lietz apa...@oliverlietz.de: +1, I think it's important to have a Sling 7 release soon. Yes, but not a half-baked one. We would have even more users complainig about 7 as we now have with 6. Well, which part do you think would be half-baked if we simply release everything as is. I think most of the bundles (if not all) are in a pretty good shape right now. Carsten I haven't checked the SNAPSHOT bundles, but I think there are some bundles where nothing changed after their latest release so we may use some already released bundles and not release *all* now. there are probaly less than 20 bundles. In theory, the list.xml should only reference snapshots which have actually changes. But I'll check this today to see where we are. Carsten
Re: Launchpad 7 Release?
Hi, On Tue, Jul 22, 2014 at 7:59 AM, Carsten Ziegeler cziege...@apache.org wrote: ...Basically I see two options: a) we simply release all snapshot bundles now as is and get the launchpad out of the door b) we reduce the list... The launchpad has conflicting requirements IMO 1) Run integration tests for all relevant bundles (the test launchpad) 2) Provide a good starting point to experiment with Sling (the user launchpad) For 2) we can reduce the set of bundles and cannot use any snapshots, but IMO for 1) we need to use snapshots, and test as many bundles as possible. So maybe we need two launchpad variants? Testing both would be difficult though, as newer tests often require the latest snapshots. -Bertrand
Re: Launchpad 7 Release?
On Tuesday 22 July 2014 07:59:22 Carsten Ziegeler wrote: Hi, hello, a new launchpad release is long time overdue. I think one of the problems is that we include so many different bundles that there is always a couple of them which need just a little bit of work to be released. And once those are done, the next bundles are on that list. the problem I see is that the list from launchpad is used for development and we don't maintain a stable list with non-SNAPSHOT bundles. Basically I see two options: a) we simply release all snapshot bundles now as is and get the launchpad out of the door I haven't checked the SNAPSHOT bundles, but I think there are some bundles where nothing changed after their latest release so we may use some already released bundles and not release *all* now. b) we reduce the list Can we split the list (into features) like I've done for Karaf? I think we should try to do something in between :) Reducing the list and then simply releasing everything. As a first step I think we shouldn't support two repository implementations. Oak is now mature and can be used in production, so why not just include Oak? This would already remove several bundles. I'm fine with just supporting Oak in 7 but I think there is some work left to be on par with Jackrabbit 2. If we stick to Jackrabbit 2 for 7 we should downgrade to 2.6 or upgrade to 2.8 as 2.7 is an unstable branch, no? Then there are things like OCM which we don't really support - so why ship it? Because people ask for it. Same for other bundles like Freemarker and Groovy templating. If we don't support bundles we should clearly state it and move them to contrib. And I guess there is more A roadmap (wiki page?) with milestones for (a) next release(s) would really be helpful as one can spend spare cycles to work on more important tasks - e.g. using Service User Mapping in JCR Server et al. Also we should use a common set of bundles in our (integration) tests to verify that everything is working with the bundle list from launchpad. My goals for a first *Karaf* Launchpad release are a current released JCR Server (whether Jackrabbit or Oak) and getting the Event bundle fixed (not sure what's the cause for a failing IT yet). Regards, O. WDYT Regards Carsten
Re: Launchpad 7 Release?
My initial thought before writing this mail was to suggest two launchpads, one very minimal which we can release more frequently. This would contain the bare minimum and gets people playing around with it. And the other one would be the full blown thing used for testing. We could even add all modules to the full one. Looking at the snapshot list of the builder project, I guess we could just release all of them and we're got with Sling 7 and then maybe have a look at how to change things after Sling 7? So if there are people interested in driving the release of the individual bundles, we should be done with that prett fast :) And I totally agree that the documentation needs to be updated, revised Carsten 2014-07-22 14:31 GMT+02:00 Daniel Klco dk...@apache.org: I agree with a release of 7 in general. I think we need to also as Oliver indicated, create a release roadmap so we have some schedule in mind for the future. On that note, what about increasing the frequency of Launchpad releases? Right now releases are infrequent enough that it's a 'big deal' if a dependency isn't ready, which may not be the case if the launchpad releases we biannual or even quarterly. Also, the documentation for Sling 6 is quite stale and does not include many important features which are used in downstream applications. -Dan On Tue, Jul 22, 2014 at 7:30 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Tue, Jul 22, 2014 at 12:20 PM, Oliver Lietz apa...@oliverlietz.de wrote: ...My goals for a first *Karaf* Launchpad release are a current released JCR Server (whether Jackrabbit or Oak) and getting the Event bundle fixed (not sure what's the cause for a failing IT yet) Are you planning to setup integration tests for that Karaf-based launcher? If we can provide that (at http://ci.apache.org/ as well) it lets users decide which launcher they want to use, knowing that all our tests pass when that launcher is used. -Bertrand -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
Re: Launchpad 7 Release?
On Tue, 2014-07-22 at 15:30 +0200, Carsten Ziegeler wrote: Looking at the snapshot list of the builder project, I guess we could just release all of them and we're got with Sling 7 and then maybe have a look at how to change things after Sling 7? +1, I think it's important to have a Sling 7 release soon. It's going to be fun though, we have a large number of releases to perform :-) $ grep -c -e SNAPSHOT src/main/bundles/list.xml 20 Robert
Re: Launchpad 7 Release?
On Tuesday 22 July 2014 13:30:59 Bertrand Delacretaz wrote: On Tue, Jul 22, 2014 at 12:20 PM, Oliver Lietz apa...@oliverlietz.de wrote: ...My goals for a first *Karaf* Launchpad release are a current released JCR Server (whether Jackrabbit or Oak) and getting the Event bundle fixed (not sure what's the cause for a failing IT yet) Are you planning to setup integration tests for that Karaf-based launcher? Sure. There are already basic bootstrap tests which check if the required bundles are available and active in org.apache.sling.launchpad.karaf- integration-tests and also some extended tests which check for services and nodes in the repository. And there is sling-tests on GitHub. If we can provide that (at http://ci.apache.org/ as well) it lets users decide which launcher they want to use, knowing that all our tests pass when that launcher is used. I will have a look when back from holidays. Regards, O. -Bertrand
RE: Launchpad 7 Release?
On Tue, 2014-07-22 at 15:30 +0200, Carsten Ziegeler wrote: Looking at the snapshot list of the builder project, I guess we could just release all of them and we're got with Sling 7 and then maybe have a look at how to change things after Sling 7? +1, I think it's important to have a Sling 7 release soon. It's going to be fun though, we have a large number of releases to perform :-) $ grep -c -e SNAPSHOT src/main/bundles/list.xml 20 Robert +1 for a speedy Sling 7 release and discuss how to increase the frequency of future Launchpad releases after the Sling 7 release. Best regards mike
Re: Launchpad 7 Release?
On Tuesday 22 July 2014 20:49:45 Robert Munteanu wrote: On Tue, 2014-07-22 at 15:30 +0200, Carsten Ziegeler wrote: Looking at the snapshot list of the builder project, I guess we could just release all of them and we're got with Sling 7 and then maybe have a look at how to change things after Sling 7? +1, I think it's important to have a Sling 7 release soon. Yes, but not a half-baked one. We would have even more users complainig about 7 as we now have with 6. It's going to be fun though, we have a large number of releases to perform :-) $ grep -c -e SNAPSHOT src/main/bundles/list.xml 20 As said before... I haven't checked the SNAPSHOT bundles, but I think there are some bundles where nothing changed after their latest release so we may use some already released bundles and not release *all* now. there are probaly less than 20 bundles. Regards, O. Robert
Launchpad 7 Release?
Hi, a new launchpad release is long time overdue. I think one of the problems is that we include so many different bundles that there is always a couple of them which need just a little bit of work to be released. And once those are done, the next bundles are on that list. Basically I see two options: a) we simply release all snapshot bundles now as is and get the launchpad out of the door b) we reduce the list I think we should try to do something in between :) Reducing the list and then simply releasing everything. As a first step I think we shouldn't support two repository implementations. Oak is now mature and can be used in production, so why not just include Oak? This would already remove several bundles. Then there are things like OCM which we don't really support - so why ship it? And I guess there is more WDYT Regards Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
