[cle-release-team] [sakai2-tcc] New Build Process

[Matthew Jones]

I started up this page in confluence:

https://confluence.sakaiproject.org/display/REL/New+2.9+Build+Process

I would add a README.txt file to the root of /svn/ pointing to this
directory. The README could contain some other information about directory
layout,  svn conventions, ways to get access, and anything else that's
unlikely to change that much.

I'd think that this confluence page could possibly be merged to the readme,
but I think the process is still going to change a little, however if anyone
DOES change it, please update the wiki! ;)

-Matthew

On Wed, Oct 26, 2011 at 6:31 PM, Steve Swinsburg
<steve.swinsburg at gmail.com>wrote:

> The most minimal checkout I've been able to make is what we are using for a
> web service delivery framework, and is here:
> https://source.sakaiproject.org/svn//msub/anu.edu.au/services/2.8.x/
>
> The only optional tool (apart from the admin ones) is SiteStats (maybe one
> other).
>
> Off topic, but a minimal install can be done!
>
> cheers,
> Steve
>
>
>
>
> On 27/10/2011, at 5:49 AM, Mark Norton wrote:
>
> > I recently tried to make a kernel-only Sakai build and failed.  Way too
> > many dependencies for me to figure out.  I wanted to build a small app
> > (not the Sakai portal) that makes calls into the kernel so that I could
> > play with some of it's features.  In the end, I had to drag in all of
> > Sakai to enable me to do this.  As such, some of Chuck's suggestions
> > would be very useful - to me if no one else.
> >
> > - Mark Norton
> >
> >
> > On 10/26/2011 2:39 PM, csev wrote:
> >> Beth,
> >>
> >> I will preface my remarks with the fact that I am proposing ideas that I
> have no idea if they negatively impact our release process and that I am
> technically incapable of implementing because they are so complex.   But...
>   That said, here is a scenario that I think works well.
> >>
> >> In a sense, we need several (I will say say three for argument sake)
> checkout distros.
> >>
> >> sakai-small - Suitable for working on a single indie or new tool
> (replaces cafe) - but does include kernel, portal, resources, site info,
> admin tools, grade book and a few other tools.  Should be as small as
> possible and yet allow me to work on Basic LTI or start a brand new tool
> with nothing else checked out.
> >>
> >> sakai-medium - Lots of the common stuff like announcements, calendar,
> emailarchive, messagecenter, samigo - in particular things that more complex
> indies (like lessonbuilder or the under-development dashboard) tend to
> depend on.
> >>
> >> sakai-large - The whole enchilada - suitable for grepping.   What is
> sakai-trunk-all right now.   We would use thing for nightles and as the seed
> for the release process and QA testing.   This can also be used for quick
> setup of demo / pilot servers that want to follow "trunk" of all the
> projects.
> >>
> >> In a sense, the idea is to take sakai-trunk-all and prune from the
> dependency branches inwards.  Medium prunes the outermost ring of the
> dependency tree from large.  Small prunes even further with the
> understanding that it is OK if a complex indie cannot build on small.   The
> goal of small is to be as small as possible and no smaller but to contain
> all the source that is within whatever ring we define.
> >>
> >> A fourth distro smaller might be kernel itself - but this might be
> something that sets a tomcat with kernel plus some httpunit or other tests
> too.
> >>
> >> A fifth larger distro might include some contrib projects - we could
> call that sakai-tasty-contrib.  Sakai-tasty-contrib could also be used for
> demo servers.
> >>
> >> Thinking out loud.  Back to working on curriculum materials for my day
> job....
> >>
> >> /Chuck
> >>
> >>
> >> On Oct 26, 2011, at 2:01 PM, Beth Kirschner wrote:
> >>
> >>> Hi everyone,
> >>>
> >>>   There's been some confusion in the developer community (at least here
> at UM) about the recent changes/improvements to the build process to create
> an "all-indie" release process. I'd like to propose we add a README.txt file
> in the root of the sakai source tree that explains the current build&
>  release process, as well as a link to the sakai-trunk-all build  (
> https://source.sakaiproject.org/svn/sakai/branches/sakai-trunk-all/). I'd
> also like to propose that we call re-brand the "all-indie release process"
> as a "all-indie build process", since this more accurately describes the
> changes (imo).
> >>>
> >>>   I'd like to bring this up for discussion at tomorrow's MT/RT call,
> but would welcome feedback online as well.
> >>>
> >>> Thoughts?
> >>> - Beth
> >>>
> >>> _______________________________________________
> >>> sakai2-tcc mailing list
> >>> sakai2-tcc at collab.sakaiproject.org
> >>> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
> >>>
> >>>
> >> _______________________________________________
> >> sakai2-tcc mailing list
> >> sakai2-tcc at collab.sakaiproject.org
> >> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
> >>
> >>
> >
> >
> > _______________________________________________
> > sakai2-tcc mailing list
> > sakai2-tcc at collab.sakaiproject.org
> > http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>
> _______________________________________________
> sakai2-tcc mailing list
> sakai2-tcc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20111027/47ad89bd/attachment-0006.html