Re: Plone 4.2.6, 4.3.2 soft-released
Guido Stevens <[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.devel |
|---|---|
| Organization | Cosent -:- s h a r i n g m a k e s s e n s e |
| Message-ID | <[email protected]> |
On 09/11/2013 05:20 PM, Eric Steele wrote:
> On Wednesday, September 11, 2013 at 11:06 AM, Guido Stevens wrote:
>
>> My Travis builds are erroring because the unified installer is not
>> present on Launchpad yet.
> Yes. We're currently waiting on the Installers Team to finish up the
> installers. Expect those to be available sometime this week.
I expected something like that, and appreciate the work involved.
> Going forward, is this going to cause a lot of issues? If so, I can hold
> off linking up the -latest aliases on dist.plone.org
While that sounds like an easy solution, and avoids continuous
integration going down for a week after each point release, it has some
downsides.
I'd expect the majority of those using test-4.x.cfg to be experienced
Plone devs running continuous integration setups. You want a new release
to hit their builds asap to detect any issues with either the new core
release, or with add-on compatibility, as soon as possible.
Delaying the -latest symlink delays this QA for a week and also might
create some confusion because of the inconsistency where -latest would
not point to the actual latest release for a while.
> <http://dist.plone.org> until the installers are available. The other
> option would be to begin providing a zip of the buildout cache so that
> relying on the installer isn't necessary.
I don't know how much work is involved in that, but it sounds like a
better option to me, for the reasons given above.
:*CU#
--
Guido Stevens | +31.43.3618933 | http://cosent.nl
s o c i a l k n o w l e d g e t e c h n o l o g y
------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. Consolidate legacy IT systems to a single system of record for IT
2. Standardize and globalize service processes across IT
3. Implement zero-touch automation to replace manual, redundant tasks
http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk