[cle-release-team] New Build Process

[Matthew Jones]

Having a README file in place once a process is mostly static is a good
idea. One that will have frequent changes during a fluid process seems like
a less useful as it will be committed and updated often and can be harder to
tell when it's altered.

If you want to put a README there that says "The current build process is
currently being re-worked. Go to <this link> in confluence for any recent
information on the current build process", that would make more sense to me.
That would require that someone actually document changes made, plans/ideas
for future changes and best practices.

Having it in confluence would better allow the community to contribute
toward these ideas as well.

On Wed, Oct 26, 2011 at 2:01 PM, Beth Kirschner <bkirschn at umich.edu> 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
>
> _______________________________________________
> cle-release-team mailing list
> cle-release-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20111026/a07bd9d6/attachment-0006.html