[Deploying Sakai] [Building Sakai] Trunk: ui package proposal
john at caret.cam.ac.uk
Wed Nov 11 23:25:12 PST 2009
I would not characterise this as an either/or choice.
I believe we could (a) have independent tools and (b) distribute an
assembly of selected tools as a single download 'package'. Thus at
release time, you could take the default 'package' or build your own
The key question revolves around quality control expectations. If we
say that combination in the default package has gone through a
concerted QA effort, but other combinations rely on the independent
tools individual QA and combinations different from the default will
need testing by the adopter, then I think we are probably describing
the plan for 2.7, but without calling it "monolithic". I believe all
we are saying is "tested package/assembly/distribution of tools and
On 10 Nov 2009, at 16:58, Michael Korcuska wrote:
> FWIW, we are planning on a normal 2.7.0 that will be "monolithic". It
> will be built on top of some of these separate pieces but we're not
> planning on solely a "construct it yourself" approach. What happens
> after that point is certainly up for discussion. I personally like the
> idea of letting tools evolve independently and occasionally grabbing
> the latest stable versions into a monolithic release when it makes
> sense. But I don't have to deploy Sakai on my campus.
> On Nov 10, 2009, at 08:41, Mark Norton wrote:
>> Seth Theriault wrote:
>>> Another observation is that the semi-rapid movement from a
>>> monolithic release (2.5) to a separated release (2.6 + K1) to a
>>> more modular bundle (2.7 + K1 + "independents") may be leaving
>>> some people in the dust. That's my main thrust here.
>> There was talk at one point about creating identified monolithic
>> after most of the major tools in Sakai were made independent.
>> Having a
>> simple way to build Sakai with Samigo automatically include (or
>> builds) is a desirable thing. That said, I don't think we are at the
>> point of creating these custom aggregate builds. We need to get the
>> independent pieces settled before they can be used (easily) to make
>> larger structures.
>> - Mark Norton
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org
>> with a subject of "unsubscribe"
> Michael Korcuska
> Executive Director, Sakai Foundation
> mkorcuska at sakaifoundation.org
> phone: +1 510-859-4247 (google voice)
> skype: mkorcuska
> production mailing list
> production at collab.sakaiproject.org
> TO UNSUBSCRIBE: send email to production-unsubscribe at collab.sakaiproject.org
> with a subject of "unsubscribe"
More information about the production