Hi,
Jukka Zitting schrieb:
> Hi,
>
> On Thu, Feb 12, 2009 at 8:26 AM, Carsten Ziegeler
> wrote:
>> Please keep in mind that Sling is a very modular system consisting
>> mainly of a variety of bundles. Sling has the intent to separately
>> release single modules (bundles). This is one of the num
Hi,
On Thu, Feb 12, 2009 at 8:26 AM, Carsten Ziegeler wrote:
> Please keep in mind that Sling is a very modular system consisting
> mainly of a variety of bundles. Sling has the intent to separately
> release single modules (bundles). This is one of the number one
> priorities for Sling - the big
On Thu, Feb 12, 2009 at 11:04 AM, Alexander Klimetschek
wrote:
> I might look a bit ugly, but [...]
Well, this might be true (you decide), but what I really wanted to say
was: "It might look a bit ugly..."
;-)
Regards,
Alex
--
Alexander Klimetschek
alexander.klimetsc...@day.com
Hi all,
first of all +1 for a restructuring. Separating the contrib stuff from
the main code, but still having the possibility to check out
everything in one place, makes a lot of sense. If more and more new
bundles come in (ala CookingEggServiceBundle), which won't be actively
maintained most of
Jukka Zitting wrote:
>
> IMHO, the trunk should contain *exactly* what goes into a release.
> I.e. a release should pretty much be just a packaged export of a
> tagged version of the trunk.
>
> If we want to track things that aren't (yet) going to be included in
> the next release, then they shou
Hi,
Paul Noden schrieb:
> Makes things a little clearer! Where would the groovy scripting engine
> come, under java?
Best of all: The Groovy Scripting Engine is not maintained by us:
Starting with 1.6 RC1 (RC3 has been published on monday), the
groovy-all.jar is a real bundle containing the Scrip
Makes things a little clearer! Where would the groovy scripting engine
come, under java?
2009/2/11 Jukka Zitting :
> Hi,
>
> On Wed, Feb 11, 2009 at 10:47 AM, Felix Meschberger
> wrote:
>> With this proposed structure, it is easily visible, what gets included
>> in the main (big) release -- as p
Hi,
On Wed, Feb 11, 2009 at 10:47 AM, Felix Meschberger wrote:
> With this proposed structure, it is easily visible, what gets included
> in the main (big) release -- as part of launchpad/bundles -- and what
> not.
IMHO, the trunk should contain *exactly* what goes into a release.
I.e. a release
Hi all,
Our source tree is currently structured mainly according to
functionality. This is fine for quickly locating some bundle or project
to inspect or work on. It is problematic in the sense, that it is not
readily visible, what is being maintained in terms of releases and what
is included in b
