Re: Time to release Sling 6 update 1 ? ( Was : Re: Time to release Sling 7? )

2013-08-07 Thread Felix Meschberger
I assume you are talking of Sling 7 ? 

If so, I agree ;-)

Regards
Felix

Am 07.08.2013 um 07:52 schrieb Carsten Ziegeler:

 I definitely agree that we should try to get Sling 6 out asap - and I think
 we're pretty close to that. Apart maybe from a release of one or two
 additional bundles, we need to release the discovery stuff (I plan to do
 this end of this week/early next week) and the new admin login stuff Felix
 is working on (hopefully this needs just a few weeks from now). Once these
 releases are through we can release Sling 6.
 So I think let's look at the snapshot dependencies in launchpad, see if
 these artifacts have some urgent open issues, fix them (if there are any)
 and then release the stuff.
 
 For the build server problems, I'm totally unhappy with the Jenkins
 installation (and this since years) - apart from spamming the mailing list,
 the value right now seems really very low. Though I have no idea how to
 change this...
 
 Regards
 Carsten
 
 
 2013/8/7 Robert Munteanu romb...@apache.org
 
 Sorry to resurrect such an old thread, but I started this conversation 3
 months ago and we aren't close to releasing Sling 7.
 
 IMO the build server flakiness contributes to this uncertainty, but so
 do a few or our tests, being unstable as well.
 
 What I'd like to propose now is to make a very minor, specific release
 of the Sling Launchpad: build it with org.apache.sling.launchpad.base
 2.5.0 .
 
 This is a low-risk move - I've tested it myself and has the advantage of
 allowing first-time users to get on board with Java 7. Right now I fear
 that some of them walk away after an unsuccessful attempt of running
 Sling.
 
 Thoughts?
 
 Robert
 
 
 
 
 -- 
 Carsten Ziegeler
 cziege...@apache.org



Re: Time to release Sling 6 update 1 ? ( Was : Re: Time to release Sling 7? )

2013-08-07 Thread Bertrand Delacretaz
On Wed, Aug 7, 2013 at 9:47 AM, Felix Meschberger fmesc...@adobe.com wrote:
 I assume you are talking of Sling 7 ?
 If so, I agree ;-)

Me too.

-Bertrand


Re: Time to release Sling 6 update 1 ? ( Was : Re: Time to release Sling 7? )

2013-08-07 Thread Robert Munteanu
On Wed, Aug 7, 2013 at 8:52 AM, Carsten Ziegeler cziege...@apache.org wrote:
 I definitely agree that we should try to get Sling 6 out asap - and I think
 we're pretty close to that. Apart maybe from a release of one or two
 additional bundles, we need to release the discovery stuff (I plan to do
 this end of this week/early next week) and the new admin login stuff Felix
 is working on (hopefully this needs just a few weeks from now). Once these
 releases are through we can release Sling 6.
 So I think let's look at the snapshot dependencies in launchpad, see if
 these artifacts have some urgent open issues, fix them (if there are any)
 and then release the stuff.

Sounds good to me. I though we were still far from releasing, so Sling
7 makes me happier than Sling 6.1 .


 For the build server problems, I'm totally unhappy with the Jenkins
 installation (and this since years) - apart from spamming the mailing list,
 the value right now seems really very low. Though I have no idea how to
 change this...

Perhaps we can use Travis for that. I know that Oak does that [1] and
I've set up a proof-of-concept some time ago at [2] but didn't update
it in quite some time. The advantage of Travis is that it always
starts with a fresh VM for each build, so there's no problematic
master-slave communication, which is the #1 problem with our current
Jenkins setup. On the other hand, it doesn't do all the graphs that
Jenkins does and does not publish binary artifacts.

To set up a Travis build we need a .travis.yml file in the root of the
repository, see [3] for what I used.

I can take care of setting up the .travis.yml file to make sure that
Sling builds on Travis. Then we need to find out how to authorize
Travis to build apache/sling ; OAK did it so it's possible.

Robert


[1]: https://travis-ci.org/apache/jackrabbit-oak
[2]: https://travis-ci.org/rombert/sling/
[3]: 
https://github.com/rombert/sling/blob/0fdfca2b3e1e5c473d5fa028aee71c6f1944a09e/.travis.yml


 Regards
 Carsten


 2013/8/7 Robert Munteanu romb...@apache.org

 Sorry to resurrect such an old thread, but I started this conversation 3
 months ago and we aren't close to releasing Sling 7.

 IMO the build server flakiness contributes to this uncertainty, but so
 do a few or our tests, being unstable as well.

 What I'd like to propose now is to make a very minor, specific release
 of the Sling Launchpad: build it with org.apache.sling.launchpad.base
 2.5.0 .

 This is a low-risk move - I've tested it myself and has the advantage of
 allowing first-time users to get on board with Java 7. Right now I fear
 that some of them walk away after an unsuccessful attempt of running
 Sling.

 Thoughts?

 Robert




 --
 Carsten Ziegeler
 cziege...@apache.org



-- 
Sent from my (old) computer


Re: Time to release Sling 6 update 1 ? ( Was : Re: Time to release Sling 7? )

2013-08-07 Thread Bertrand Delacretaz
On Wed, Aug 7, 2013 at 10:35 AM, Robert Munteanu rob...@lmn.ro wrote:
 ...I can take care of setting up the .travis.yml file to make sure that
 Sling builds on Travis. Then we need to find out how to authorize
 Travis to build apache/sling ; OAK did it so it's possible

Sounds good to me!
-Bertrand


Re: Time to release Sling 6 update 1 ? ( Was : Re: Time to release Sling 7? )

2013-08-07 Thread Carsten Ziegeler
Yepp, let's give it a try - we don't need to publish the artifacts, just
getting a success/fail mail is enough

Carsten


2013/8/7 Bertrand Delacretaz bdelacre...@apache.org

 On Wed, Aug 7, 2013 at 10:35 AM, Robert Munteanu rob...@lmn.ro wrote:
  ...I can take care of setting up the .travis.yml file to make sure that
  Sling builds on Travis. Then we need to find out how to authorize
  Travis to build apache/sling ; OAK did it so it's possible

 Sounds good to me!
 -Bertrand




-- 
Carsten Ziegeler
cziege...@apache.org


Re: Time to release Sling 6 update 1 ? ( Was : Re: Time to release Sling 7? )

2013-08-07 Thread Robert Munteanu
On Wed, Aug 7, 2013 at 12:49 PM, Carsten Ziegeler cziege...@apache.org wrote:
 Yepp, let's give it a try - we don't need to publish the artifacts, just
 getting a success/fail mail is enough

Added .travis.yml file in
http://svn.apache.org/viewvc?view=revisionrevision=1511240 and also
filed INFRA-6643 to activate the Travis hook on Github.

After the INFRA issue is resolved I'll look into tweaking the build.

Robert


 Carsten


 2013/8/7 Bertrand Delacretaz bdelacre...@apache.org

 On Wed, Aug 7, 2013 at 10:35 AM, Robert Munteanu rob...@lmn.ro wrote:
  ...I can take care of setting up the .travis.yml file to make sure that
  Sling builds on Travis. Then we need to find out how to authorize
  Travis to build apache/sling ; OAK did it so it's possible

 Sounds good to me!
 -Bertrand




 --
 Carsten Ziegeler
 cziege...@apache.org



-- 
Sent from my (old) computer


Re: Time to release Sling 6 update 1 ? ( Was : Re: Time to release Sling 7? )

2013-08-06 Thread Carsten Ziegeler
I definitely agree that we should try to get Sling 6 out asap - and I think
we're pretty close to that. Apart maybe from a release of one or two
additional bundles, we need to release the discovery stuff (I plan to do
this end of this week/early next week) and the new admin login stuff Felix
is working on (hopefully this needs just a few weeks from now). Once these
releases are through we can release Sling 6.
So I think let's look at the snapshot dependencies in launchpad, see if
these artifacts have some urgent open issues, fix them (if there are any)
and then release the stuff.

For the build server problems, I'm totally unhappy with the Jenkins
installation (and this since years) - apart from spamming the mailing list,
the value right now seems really very low. Though I have no idea how to
change this...

Regards
Carsten


2013/8/7 Robert Munteanu romb...@apache.org

 Sorry to resurrect such an old thread, but I started this conversation 3
 months ago and we aren't close to releasing Sling 7.

 IMO the build server flakiness contributes to this uncertainty, but so
 do a few or our tests, being unstable as well.

 What I'd like to propose now is to make a very minor, specific release
 of the Sling Launchpad: build it with org.apache.sling.launchpad.base
 2.5.0 .

 This is a low-risk move - I've tested it myself and has the advantage of
 allowing first-time users to get on board with Java 7. Right now I fear
 that some of them walk away after an unsuccessful attempt of running
 Sling.

 Thoughts?

 Robert




-- 
Carsten Ziegeler
cziege...@apache.org