buildbot success in CPS Generic on CPS-3.6-full

The Buildbot has detected a restored build on builder CPS-3.6-full while building CPS Generic.
Full details are available at:
 http://buildbot.cps-cms.org/builders/CPS-3.6-full/builds/11

Buildbot URL: http://buildbot.cps-cms.org/

Buildslave for this Build: purity.racinet.fr

Build Reason: scheduler
Build Source Stamp: [branch default] 6f81f928cbd64144096cfc4151a7c64471abed30
Blamelist: Georges Racinet on ishtar.racinet.fr <georges@...>

Build succeeded!

sincerely,
 -The Buildbot

_______________________________________________
cps-devel mailing list
http://lists.cps-cms.org/listinfo/cps-devel

buildbot failure in CPS Generic on CPS-3.6-full

The Buildbot has detected a new failure on builder CPS-3.6-full while building CPS Generic.
Full details are available at:
 http://buildbot.cps-cms.org/builders/CPS-3.6-full/builds/10

Buildbot URL: http://buildbot.cps-cms.org/

Buildslave for this Build: purity.racinet.fr

Build Reason: scheduler
Build Source Stamp: [branch default] 2ad7f470309ae22370579ebe4b37cb265b6643c0
Blamelist: Georges Racinet on ishtar.racinet.fr <georges@...>

BUILD FAILED: failed shell_2

sincerely,
 -The Buildbot

_______________________________________________
cps-devel mailing list
http://lists.cps-cms.org/listinfo/cps-devel

Buildbot notifications

Dear CPS developers,

as of now, the buildbot will notify this list of builders status changes
(typically from success to failure and back).
This way, developers will be informed of current problems that may
impact their work or bleeding-edge based deployments, and get a notice
when situation is back to normal.
I'll do a voluntary failure and fix in a few minutes to test the
notification itself.

Of course, this also serves the purpose of fixing the problems as soon
as they occur. That's usually easier than a month later.

We considered also sending these notifications to the code mailing list,
but decided that they would be unnoticed among the changesets and trac
notifications. Build failures are supposed not to happen that often, but
of course the purpose of using a tool such as buildbot is to perform the
extensive testing that would not be realistic in the typical developer
workflow, so they will happen.

All of this is still in progress and a bit experimental, we'll see what
to do if people here find that this generates too much traffic.

Regards,

--

-- 
Georges Racinet, http://www.racinet.fr
Zope/CPS expertise, assistance & development
GPG: 0x4862FFF7 identi.ca & twitter: gracinet

Real-time update of CPS documentation

Hello again,

thanks to our recent continuous integration efforts, the RST
documentation of the CPS products is now converted to HTML and put
online in real time on http://doc.cps-cms.org. There still are quite a
few obsolete parts, though, but at least this gives developers more
incentive to update the documentation.

We currently maintain two lines : CPS-3.5-head is the latest in the 3.5
series ; CPS-head is the latest of the latest (currently 3.6).

In case of doubt, here's the link to watch the building process :
http://buildbot.cps-cms.org/waterfall?builder=CPS-3.5-doc&builder=CPS-3.6-doc

Cheers,

--

-- 
Georges Racinet, http://www.racinet.fr
Zope/CPS expertise, assistance & development
GPG: 0x4862FFF7 identi.ca & twitter: gracinet

_______________________________________________
cps-devel mailing list
http://lists.cps-cms.org/listinfo/cps-devel

Changes in CPS mailing-lists hosting

Dear all,

the four mailing lists related to CPS have just moved to the
lists.cps-cms.org
domain, including all membership options and archives. Everything should
therefore
be about the same for you, apart from the addresses.

From now on, the addresses at lists.nuxeo.com are obsolete. We can't
guarantee that
you'll be read if you post on them.

Many thanks to our friends at Nuxeo for their help on this operation,
that will
allow us to manage them directly according to our needs.

To make a bit more sense of this cross-posting, let me take the
opportunity to
try and clarify the purposes of the different lists a bit (advices welcome).

 - cps-devel is focused on the development of CPS itself. Discussions
should be about
   design decisions and changes in the standard distributions
(CPS-3-base to CPS-3-full). We
   also often make announcements of releases that are not considered as
ready for a wider
   public there.

 - cps-users and cps-users-fr are for... users ! In practice, that
should mean mostly questions

Buildbot continuous integration for CPS

Hi there,

a big plus on he quality side : we started buildboting CPS (again) a few
days ago, see http://buildbot.cps-cms.org/waterfall.
The tests are triggered by pushes on the reference repositories hosted
at http://hg.cps-cms.org.

Email notifications of failures aren't configured yet, but we'll send
them either to this list or to code@... (opinions welcome).

If any of you are interested in setting up slaves, please check the
setup instructions at
http://hg.cps-cms.org/buildbot/cps-config/file/tip/README.txt .
In that repository you'll also find a template configuration and
instructions to buildbot hgbundler-tracked custom projects.

Regards,

--

-- 
Georges Racinet, http://www.racinet.fr
Zope/CPS expertise, assistance & development
GPG: 0x4862FFF7 identi.ca & twitter: gracinet

_______________________________________________
cps-devel mailing list
http://lists.nuxeo.com/mailman/listinfo/cps-devel

About CPSPortlets in 3.6

Hi everybody,

as you may already know, the rendering system of portlets is the major
visible change of CPS 3.6 for now.
Today, I started documenting the new system (and the old one actually,
as a legacy paragraph) in CPSPortlets/doc
This is written in narrative/reference style.

Comments and contributions are very welcome, especially if someone has
the courage to initiate one or two howtos:
 - override an existing portlet rendering ;
 - define a new rendering for an existing portlet.

Many files in CPSPortlets/doc are sadly early days drafts or are quite
outdated (the piece on styling for instance).
I also entirely rewrote the README.txt

Remark: this new system is used only for a few portlet types in 3.6.0
(check CPSPortlets/browser/portlets.zcml to see all view definitions).
We still have quite a bit of porting/cleaning to do.

Cheers,

--

-- 
Georges Racinet, http://www.racinet.fr
Zope/CPS expertise, assistance & development
GPG: 0x4862FFF7 identi.ca & twitter: gracinet

Code freeze in the 3.5 branch

Hello again,

CPS 3.5.5 should be released in a week or two. That confirms our pace of
about two months.

In the meanwhile, we will address showstoppers only, with a few
exceptions at the edges (a missing export/import adapter in
CPSSharedCalendar, a better CSV export in CPSUserforms). New
enhancements and non critical bugfixes should be done in branches, now.

Let me remind you our convention : while working on milestone 3.5.n, the
bulk of old tickets sit in 3.5.(n+1), so that they don't hide the
relatively smaller number of current tickets, but can be cherry picked
for immediate treatment.

Tickets scheduled for CPS 3.5.6 have already been postponed to 3.5.7
New tickets should be scheduled for 3.5.6, except CPS 3.5.5
showstoppers, of course.

Cheers,

--

-- 
Georges Racinet, http://www.racinet.fr
Zope/CPS expertise, assistance & development
GPG: 0x4862FFF7 identi.ca & twitter: gracinet

_______________________________________________
cps-devel mailing list

CPS 3.6.0 released

Hello everyone,

CPS 3.6.0 has been tagged yesterday.

It is to be considered as an alpha release, to be used in production by
experts only. That's why I don't announce it on the users mailing-lsits.
Also, the target audience is expected to be familiar with the versioning
system (see http://trac.cps-cms.org). Therefore I don't feel the urge to
dump tarballs or .deb packages. I will if someone asks for them, though.

The main purpose of this landmark release is to use the trac for the
default branch issues and enhancements, now that a first big round of
ground work has been done.

The main changes in the 3.6 series so far are :

 - migration to Zope 2.10 and CMF 2.1.1 (CMF not embedded any more)
 - major refactor of CPSPortlets with ZTK-style views based renderings
(w/ backwards compatibility)

I will document the new CPSPortlets way ASAP, but let me says that it's
much cleaner, natural and easy to understand than before.

People wanting to test migrations from CPS 3.5 should read the dedicated
file in CPSDefault/doc

Let me also remind everyone that CPS 3.6 series is transitional, not
expected to be stable, although thay may happen at some point.

Have a nice week

CPS 3.5.4 released

Hi there,

CPS-3.5.4 has been tagged yesterday and uploaded to
http://downloads.cps-cms.org

This is the end of the push freeze to the official repositories.

We are currently testing the Debian package (still an issue with the
cleaning of files related to the Five version that used to ship with CPS
3.5.3).
We'll make announcements to the user mailing lists once the Debian
package is ready.

The full changelog from CPS 3.5.3 of the CPS-3-full bundle is attached
to this email (see also http://trac.cps-cms.org/milestone/CPS%203.5.4)
You can have more of these with the ``hgbundler bundle-changelog`` command.

The issues that were still tagged for 3.5.4 have been pushed to 3.5.5
Overall, we're quite pleased with the new tracking policy of keeping the
big bunch of tickets in the n+2 (currently 3.5.6) milestone. It allowed
us a much shorter cycle for 3.5.4 (with 2 weeks of freeze time due to
work overaload of the project leaders).

Now the bulk of old tickets are scheduled for 3.5.6, but nothing
prevents anyone to treat some earlier (please reassign to 3.5.5 in the
process).

Cheers,

--

-- 

Freeze of CPS-3.5 branch

We are on the verge of releasing CPS 3.5.4.

This version will get Debian packages and more general exposure than CPS
3.5.3, which had some cosmetic issues in its default incarnation (front
page etc.)

We'll stay in frozen state for about one week, the time to give it more
testing and to upgrade the permanent demo to it.

The branch for #2479 (issues with language changes) will be merged
before that, but that's the only changes that will be accepted to the
CPS-3.5 branch, except release showstoppers, if any, of course.

If you really need something, you'll have to do it in a branch, and
we'll merge it again right after the release.
I've already complied to this policy by implementing #2495 and #2496 in
branches.

Regards,
--

-- 
Georges Racinet, http://www.racinet.fr, http://anybox.fr
Zope/CPS & OpenERP expertise, assistance & development
GPG: 0x4862FFF7 identi.ca & twitter: gracinet

_______________________________________________
cps-devel mailing list
http://lists.nuxeo.com/mailman/listinfo/cps-devel