Hi Walter,
On 11/18/2010 09:51 AM, Walter Rafelsberger wrote:
On 11/17/2010 03:58 PM, Jerome Renard wrote:
However, for a custom app, it does not make sense to bundle all Zeta
Components if you only want to use e.g. Graph or Mail (which are 2 of
the most used components).
For inspiration
2010/11/29 Manuel Pichler m...@manuel-pichler.de:
Hi Toby,
Am Montag, den 29.11.2010, 11:21 +0100 schrieb Tobias Schlitt:
[...]
On 11/17/2010 03:58 PM, Jerome Renard wrote:
However, for a custom app, it does not make sense to bundle all Zeta
Components if you only want to use e.g. Graph
On Mon, 29 Nov 2010, Manuel Pichler wrote:
Am Montag, den 29.11.2010, 11:21 +0100 schrieb Tobias Schlitt:
[...]
On 11/17/2010 03:58 PM, Jerome Renard wrote:
However, for a custom app, it does not make sense to bundle all Zeta
Components if you only want to use e.g. Graph or Mail
On Thu, 4 Nov 2010, Tobias Schlitt wrote:
I have studied the guidelines for releases in the ASF and tried to make
up a release process document for us. Please find it attached for
discussion. You can also find it in our SVN under
docs/release_process.txt
My comments:
Component
On Thu, 11 Nov 2010, Tobias Schlitt wrote:
On 11/07/2010 11:55 AM, Thomas Ernest wrote:
Here comes questions :
A/ What is your opinion about the proposal automate full package release ?
B/ What are advantages of separating full package release process from
component release process ?
On Thu, 18 Nov 2010, Tobias Schlitt wrote:
Don't get me wrong, I insist of keeping our PEAR channel as the primary
distribution way.
Absolutely.
Derick
--
http://derickrethans.nl | http://xdebug.org
Like Xdebug? Consider a donation: http://xdebug.org/donate.php
twitter: @derickr and @xdebug
On Tue, 16 Nov 2010, Tobias Schlitt wrote:
as far as I can see there are two major points in this discussion:
1. Providing updates for single components in short time frames could
bring people to an update hell, when they need to download and upgrade
some components every week.
They don't
Hi all
On Thu, Nov 18, 2010 at 10:45 AM, Gaetano Giunta
giunta.gaet...@gmail.comwrote:
otoh: would we have such info available for existing components or would it
be so hard to extract it in a precise and useful way that it would not be
done anyway (I mean apart from the obvious
On 18. nov. 2010, at 07.44, Tobias Schlitt wrote:
Hi guys,
On 11/17/2010 03:58 PM, Jerome Renard wrote:
On Tue, Nov 16, 2010 at 5:43 PM, Gaetano Giunta giunta.gaet...@gmail.com
wrote:
[...]
But think about this: why is eZ Publish bundling the whole of the ZetaC when
it only uses
Hi all,
I'm not qualified to participate actively to the current discussions,
although i'm reading it all.
However, i'd like to share how it works with python/pinax projects because
it might inspire you.
On Thu, Nov 18, 2010 at 9:46 AM, Tobias Schlitt tob...@schlitt.info wrote:
Hi Max,
On
Another point that has maybe already been discussed but how do we manage
components in the SVN, do we have separate tags and branches for the set of
components and each component ?
My point is to chose the easiest way to deliver things : if each package
must be done manually, it increases the
Hi James,
On 11/18/2010 10:04 AM, James Pic wrote:
I'm not qualified to participate actively to the current discussions,
although i'm reading it all.
hoo? Why not?
However, i'd like to share how it works with python/pinax projects because
it might inspire you.
Any kind of input is highly
Hi Tobias;
On Thu, Nov 4, 2010 at 5:28 PM, Tobias Schlitt tob...@schlitt.info wrote:
Hi,
I have studied the guidelines for releases in the ASF and tried to make
up a release process document for us. Please find it attached for
discussion. You can also find it in our SVN under
Hi Gaetano,
On Tue, Nov 16, 2010 at 5:43 PM, Gaetano Giunta
giunta.gaet...@gmail.com wrote:
[...]
But think about this: why is eZ Publish bundling the whole of the ZetaC when
it only uses a couple of components?
Simply because that was the easiest (and quickest) solution when I
wrote the build
Hi Maxime,
On Tue, Nov 16, 2010 at 5:47 PM, Maxime Thomas maxime.t...@gmail.com wrote:
[...]
And honestly, I cannot see the problem of downloading all even if you don't
use some parts. Who can do the more can do the less.
Yes, but less is more :D
Ok --- []
--
Jérôme Renard
Hi guys,
On 11/17/2010 03:58 PM, Jerome Renard wrote:
On Tue, Nov 16, 2010 at 5:43 PM, Gaetano Giunta giunta.gaet...@gmail.com
wrote:
[...]
But think about this: why is eZ Publish bundling the whole of the ZetaC when
it only uses a couple of components?
Simply because that was the
Maxime Thomas wrote:
Sound strange, if we look at what is done elsewhere :
- JQuery UI : shared version number
- Zend : shared version number
- Former eZComponents : both version number
also YUI
The shared version number implies a kind of packaged application. Else it
can be difficult to
2010/11/16 Gaetano Giunta giunta.gaet...@gmail.com:
Maxime Thomas wrote:
Sound strange, if we look at what is done elsewhere :
- JQuery UI : shared version number
- Zend : shared version number
- Former eZComponents : both version number
also YUI
The shared version number implies a kind
Patrick ALLAERT wrote:
2010/11/16 Gaetano Giuntagiunta.gaet...@gmail.com:
Maxime Thomas wrote:
Sound strange, if we look at what is done elsewhere :
- JQuery UI : shared version number
- Zend : shared version number
- Former eZComponents : both version number
also YUI
The shared version
Why not, but if I want a set of components that includes tiein, how can I do
? Do I have to download each components separately ?
My opinion is maybe to get both version numbers as it was done fore ezc, a
version number for the set and a version number for each components.
By this way, everyone
Hi guys,
as far as I can see there are two major points in this discussion:
1. Providing updates for single components in short time frames could
bring people to an update hell, when they need to download and upgrade
some components every week.
2. The clear target of Zeta to provide components
Hi Thomas,
On 11/07/2010 11:55 AM, Thomas Ernest wrote:
Le 04/11/2010 17:28, Tobias Schlitt a écrit :
docs/release_process.txt
It is a very interesting and useful synthesis. Thank you.
The document summarizes the requirements for releases roughly and then
tries to relealize these in
Hi Tobias,
Le 04/11/2010 17:28, Tobias Schlitt a écrit :
docs/release_process.txt
It is a very interesting and useful synthesis. Thank you.
The document summarizes the requirements for releases roughly and then
tries to relealize these in a release process specific to Zeta.
There are
23 matches
Mail list logo
