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
On Thu, Feb 12, 2009 at 11:04 AM, Alexander Klimetschek
aklim...@day.com 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,
On Thu, Feb 12, 2009 at 8:26 AM, Carsten Ziegeler cziege...@apache.org 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
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 should be
