[sakai2-tcc] LTI Release Consulting

[Steve Swinsburg]

Hi Chuck,

Sorry for the late joining in to this discussion. The answer is yes to all of these.

One thing to note is that pom mods are generally not required in the source tags either, since the project should be binding to a stable version, i.e. 2.7.3 or 2.8.2 or 2.9.1 (NOT 2.9.1-SNAPSHOT). 

What this means is that the parent pom will be released to the Maven repository so people who checkout the source code can just build the project without modification of the pom, Maven will find it and everyone will be happy. The parent poms are generally only used for getting generic stuff like plugins/repositories and other settings, but also the versions of various API's and services. And if the versions of API's don't have incompatible changes in them (and most of the time they don't), then the tool will build against the older versions just fine, and then be deployed with the newer versions (since Tomcat has them deployed) and it will be sweet.

Three cases to demonstrate this:

I use the 1.1 tag of the adobe connect tool in my 2.9 builds, it binds to a parent of master 2.8.2. No issues.
I use the 1.0.2 tag of roster2 in my 2.9 builds, it binds to a parent of purepoms 2.8.0. No issues.
I use the 1.2.6 tag of hierarchy in my 2.9 builds, it binds to a parent of 2.5.4. No issues.

cheers,
Steve

On 27/02/2013, at 2:27 AM, Charles Severance <csev at umich.edu> wrote:

> Thanks everyone for all the help / feedback - things are quickly clearing up.  Here is what I think are the recommendations:
> 
> (a) Make a branch/tag for blti-2.1.x - this should reference 2.9.0 as its parent in the pom.xml
> 
> (b) I should test blti-2.1.x with 2.9.0, 2.9.1, and 2.9-x and note the results in my release notes (it would be weird if one artifact did not work with all three)
> 
> (c) There will be one binary artifact blti-2.1.0 that should work in all the 2.9.x releases
> 
> (d) Folks who use source from various 2.9's should be able to check out 2.1.0 and tweak only the parent in the pom.xml and nothing else - but there is no need to me to make separate tags just for this.
> 
> (e) Check to see the source and artifacts work with 2.8.3 - if they do, document it - if not either document the non-working or possibly make some other tag at that point
> 
> Generally follow the Profile2 model for releases and release notes.
> 
> Did I get it?
> 
> /Chuck
> 
> _______________________________________________
> 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/sakai2-tcc/attachments/20130227/d963a107/attachment-0001.html