[cle-release-team] [Building Sakai] Sakai indie 2.9.1 tag, indie projects parent version.

[Matthew Jones]

You're right it's wrong. Since API's shouldn't have changed between 2.9.0
and 2.9.1 it shouldn't cause a problem (and if it does someone merged an
API change), but it would require a new (2.9.2) release if we wanted to
make it correct.

I do know how it happened. The release process has to run *mvn
versions:update-parent* to set the parent version before releasing the
indie and commit, then revert the parent back after the release. This
variable is provided to Jenkins and wasn't correctly updated to 2.9.1. This
is because of the long standing MNG-624 [1] and no other way to set the
parent other than hard coding. There was also problem that Sam noticed half
way through releasing the indies where the parent wasn't being committed
because Jenkins didn't have the SSH key for some reason and the builds were
all failing (but still being released to Sonatype). I thought I'd fixed
that, but looks like this still existed and wasn't updated. I saw that
2.9.0 was still in there, and it seemed strange but I didn't think anything
of it at the time.

I think this entire release process needs to change because there really
are too many manual steps and things that can go wrong. I'll respond to Dr.
Chuck's email about that relating to the 2.9.1-all tag, as I don't think
people should be using that tag for anything and I don't think the indie
assemblies/core-deploy are useful either.

[1] http://jira.codehaus.org/browse/MNG-624


On Fri, Feb 15, 2013 at 6:01 AM, Steve Swinsburg
<steve.swinsburg at gmail.com>wrote:

> Taking this to the cle-release-team list. The indies for 2.9.1 are binding
> to a 2.9.0 master. This doesn't sound right at all.
>
>
> cheers,
> Steve
>
> On 15/02/2013, at 8:02 PM, JUAN JOSé MEROñO SáNCHEZ <jjmerono at um.es>
> wrote:
>
> > Hi all,
> >
> > Does anyone knows why all indie projects (e.g. announcement 2.9.1,
> > basic-lti 2.0.1, etc...) included in the 2.9.1 version, have as their
> > parent master version 2.9.0 instead of 2.9.1?
> > I thought that indie versions included in 2.9.1 should have 2.9.1 as
> > their master parent version, like versions included in 2.9.0 have 2.9.0
> > as parent version, is that right?
> >
> >
> https://source.sakaiproject.org/svn/announcement/tags/announcement-2.9.0/pom.xml
> > (for sakai2.9.0)
> >
> https://source.sakaiproject.org/svn/announcement/tags/announcement-2.9.1/pom.xml
> > (for sakai2.9.1, but the same parent version)
> >
> > https://source.sakaiproject.org/svn/basiclti/tags/basiclti-2.0.0/pom.xml
> > (for sakai2.9.0)
> > https://source.sakaiproject.org/svn/basiclti/tags/basiclti-2.0.1/pom.xml
> > (for sakai2.9.1, but the same parent version)
> >
> > As this situation appears in every indie project I suspect that there is
> > a good reason (maybe in order to get out the indies releases before
> > releasing master 2.9.1),
> > I would love to know the reason, can anyone explain it?
> >
> > Thanks in advance!!
> >
> > _______________________________________________
> > sakai-dev mailing list
> > sakai-dev at collab.sakaiproject.org
> > http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> >
> > TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
>
> _______________________________________________
> 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/20130215/f9adf67a/attachment-0006.html