[cle-release-team] [WG: Sakai QA] Sakai CLE 2.9.1-RC01 testing
Matthew Jones
matthew at longsight.com
Tue Jan 22 10:13:30 PST 2013
Clarifying to the release team and tcc,
I talked about this with Neal this morning, and this is a different process
than what was done in the lead-up to the 2.9.0 release. This was actually
what Chris Maurer did back at the beginning of the 2.9 release cycle.
Prior maintenance releases (2.8.2) didn't have any release candidates at
all though it was easier to clean up (fix) anything incorrect as the
artifacts were in our repository. This is harder (not possible) when things
are in maven central, and master points to everything. What we're doing is
essentially building a pack-bin from the 2.9.x-all and testing against
that. If there are no additional merges done between that time then it
should be the same as 2.9.1. If there are blockers found merges needed they
will be made.
Nobody should run really the rc01 anyway outside of QA for this maintenance
release since 2.9.1 will come quickly after and I can provide the binary if
other QA servers *want* to run it. This shortens the release candidate
cycle from 2 days waiting for Jenkins and uploads and around 4-6 hours of
my time to 1 hour of my time and 1 hour of waiting. (If that, mostly just
to checkout, build, cleanup and redeploy)
Back when the rc03->2.9.0 was cut, it wasn't even guaranteed to be a
unchanged version as 2.9.0 was re-cut from 2.9.x (without fixed versions)
and re-released. The only issues that could cause a problem would be
introduced during the actual release process (binding to incorrect
versions) but I'm confident that those were fixed a few release candidates
ago and I'm pay a good amount of attention to the details of what gets
pushed.
I think this will be a good step going forward to help speed up the release
process and eliminate artifacts that clutter up the repositories.
On Tue, Jan 22, 2013 at 12:56 PM, Neal Caidin <
nealcaidin at sakaifoundation.org> wrote:
> Hi All,
>
> We are going to take a snapshot of 2.9.x and move to the Longsight QA
> server on Wednesday evening/Thursday morning. This will essentially be our
> RC01 testing. If all goes well, we will test this Thursday and Friday, and
> if the testing passes, then 2.9.1 can be cut next week.
>
> The QA team is working on "light regression" testing scripts. Essentially
> just a few key functions from the most used tools. That, plus some
> additional testing of Jiras that were merged into 2.9.x and not yet tested
> will comprise our QA approach.
>
> More details will be forthcoming, but if you can, please help with QA
> testing this Thursday and Friday.
>
> Cheers,
>
> Neal Caidin
>
> Sakai CLE Community Coordinator
> nealcaidin at sakaifoundation.org
> Skype: nealkdin
> AIM: ncaidin at aol.com
>
>
>
>
>
>
> _______________________________________________
> sakai-qa mailing list
> sakai-qa at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-qa
>
> TO UNSUBSCRIBE: send email to sakai-qa-unsubscribe at collab.sakaiproject.orgwith a subject of "unsubscribe"
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20130122/b4a17829/attachment-0006.html
More information about the cle-release-team
mailing list