I have a client that won't let me use 1.2 because 1.1.19 is tagged as
stable whereas 1.2 is RC2...
I tried and tried to explain to him the many reasons why it would be
better and more efficient and more secure etc... to use 1.2 but to no
avail since all he can see is the 'stable' tag ...
So I was wondering if any one had any insight on when the 1.2 version
would be tagged as stable.
I really don't want to go back working with 1.1 :( ...
I know the work put into this framework and all I'm asking if there is
a chance for a stable tagged version within the forthcoming month
since this would allow me to advocate 1.2 and save myself some
trouble ...
thanks
ps. I know I'll probably get answers like : 'it'll be out when it'll
be out', or 'just change client' :) but if the release is close I'd
hate developing for 1.1.
ps2. And I surely would like to help for the release but I
unfortunately miss time and skills.
> I have a client that won't let me use 1.2 because 1.1.19 is tagged as > stable whereas 1.2 is RC2...
> I tried and tried to explain to him the many reasons why it would be > better and more efficient and more secure etc... to use 1.2 but to no > avail since all he can see is the 'stable' tag ...
> So I was wondering if any one had any insight on when the 1.2 version > would be tagged as stable.
> I really don't want to go back working with 1.1 :( ...
> I know the work put into this framework and all I'm asking if there is > a chance for a stable tagged version within the forthcoming month > since this would allow me to advocate 1.2 and save myself some > trouble ...
> thanks
> ps. I know I'll probably get answers like : 'it'll be out when it'll > be out', or 'just change client' :) but if the release is close I'd > hate developing for 1.1.
> ps2. And I surely would like to help for the release but I > unfortunately miss time and skills.
> I have a client that won't let me use 1.2 because 1.1.19 is tagged as
> stable whereas 1.2 is RC2...
> I tried and tried to explain to him the many reasons why it would be
> better and more efficient and more secure etc... to use 1.2 but to no
> avail since all he can see is the 'stable' tag ...
> So I was wondering if any one had any insight on when the 1.2 version
> would be tagged as stable.
> I really don't want to go back working with 1.1 :( ...
> I know the work put into this framework and all I'm asking if there is
> a chance for a stable tagged version within the forthcoming month
> since this would allow me to advocate 1.2 and save myself some
> trouble ...
> thanks
> ps. I know I'll probably get answers like : 'it'll be out when it'll
> be out', or 'just change client' :) but if the release is close I'd
> hate developing for 1.1.
> ps2. And I surely would like to help for the release but I
> unfortunately miss time and skills.
Why is your client deciding how you work? What if your client told
you to build it in C++ because he likes C++ would you do it? Or that
he only approves of dreamweaver/homesite as an editor? Also ask if
your client uses gmail or google calendar? both of these are beta and
therefore should not be used by his logic. And honestly what makes
software stable? no bugs? then all os'es can be considered
unstable. Windows gets patches weekly. mac os and linux also get
frequent patches. Yet these are considered stable.
My client decides because they are corporate and have people who said
they could not have 'not stable' software used for their sites, which
is I agree is the position of people who don"t really know what
software is about, they don"t even have the skills to judge whether it
is or not. It's a bank and they are just a pain.
I guess I'll just not work with them anymore which will prevent me
from going insane.
Sorry to have bothered the community with this.
thomas
On Sep 5, 5:34 pm, fr3nch13 <fr3nc...@gmail.com> wrote:
On Sep 5, 3:27 pm, "thomas.m...@gmail.com" <thomas.m...@gmail.com>
wrote:
> I know all this, believe me
> My client decides because they are corporate and have people who said
> they could not have 'not stable' software used for their sites, which
> is I agree is the position of people who don"t really know what
> software is about, they don"t even have the skills to judge whether it
> is or not. It's a bank and they are just a pain.
> I guess I'll just not work with them anymore which will prevent me
> from going insane.
> Sorry to have bothered the community with this.
> thomas
Its no bother really, Unless you really don't want to work with 1.1
anymore there is really nothing wrong with it. You could always
charge more to have to work with 1.1 so you have time to backport some
of the features that you need, and any additional headaches.
> My client decides because they are corporate and have people who said
> they could not have 'not stable' software used for their sites, which
> is I agree is the position of people who don"t really know what
> software is about, they don"t even have the skills to judge whether it
> is or not. It's a bank and they are just a pain.
> I guess I'll just not work with them anymore which will prevent me
> from going insane.
> Sorry to have bothered the community with this.
> thomas
> On Sep 5, 5:34 pm, fr3nch13 <fr3nc...@gmail.com> wrote:
> > IMO the RC2 is kind of a misnomer as this is the most stable release
> > candidate of any software i've ever worked with.
> No worries, build stuff in 1.1...
> When 1.2 becomes stable charge them lost of $$$ to convert to 1.2
> Put this in a contract, since once 1.2 is stable 1.1 is obsolete and
> will require immediate upgrade ;)
> On Sep 5, 3:27 pm, "thomas.m...@gmail.com" <thomas.m...@gmail.com>
> wrote:
> > I know all this, believe me
> > My client decides because they are corporate and have people who said
> > they could not have 'not stable' software used for their sites, which
> > is I agree is the position of people who don"t really know what
> > software is about, they don"t even have the skills to judge whether it
> > is or not. It's a bank and they are just a pain.
> > I guess I'll just not work with them anymore which will prevent me
> > from going insane.
> > Sorry to have bothered the community with this.
> > thomas
> > On Sep 5, 5:34 pm, fr3nch13 <fr3nc...@gmail.com> wrote:
> > > IMO the RC2 is kind of a misnomer as this is the most stable release
> > > candidate of any software i've ever worked with.
In my opinion, you probably just need to tell him what "stable" means
for something like a framework. People hear "unstable", think of
Windows, and think of unexpected crashes. Tell him that using RC2
does not in anyway affect whether or not the site will crash, I bet
that is what he is thinking.
On Sep 6, 3:20 am, "thomas.m...@gmail.com" <thomas.m...@gmail.com>
wrote:
> > > My client decides because they are corporate and have people who said
> > > they could not have 'not stable' software used for their sites, which
> > > is I agree is the position of people who don"t really know what
> > > software is about, they don"t even have the skills to judge whether it
> > > is or not. It's a bank and they are just a pain.
> > > I guess I'll just not work with them anymore which will prevent me
> > > from going insane.
> > > Sorry to have bothered the community with this.
Well... 1.2 is yet a Release Candidate, although a very stable and
robust release candidate, but yet release candidate.
The main reason that it is kept on this name is because there might
be, yet, some hidden flaws in it. Flaws that neither you nor I know in
it... That could actually jeopardise your customer's system.
He is not willing to take the risks... I would not be willing to take
the risks on his shoes as well...
> I have a client that won't let me use 1.2 because 1.1.19 is tagged as
> stable whereas 1.2 is RC2...
> I tried and tried to explain to him the many reasons why it would be
> better and more efficient and more secure etc... to use 1.2 but to no
> avail since all he can see is the 'stable' tag ...
> So I was wondering if any one had any insight on when the 1.2 version
> would be tagged as stable.
> I really don't want to go back working with 1.1 :( ...
> I know the work put into this framework and all I'm asking if there is
> a chance for a stable tagged version within the forthcoming month
> since this would allow me to advocate 1.2 and save myself some
> trouble ...
> thanks
> ps. I know I'll probably get answers like : 'it'll be out when it'll
> be out', or 'just change client' :) but if the release is close I'd
> hate developing for 1.1.
> ps2. And I surely would like to help for the release but I
> unfortunately miss time and skills.
I agree, the customer is always right, but you can always refuse to do
the job and explain exactly why. if you are that a good programmer
you will always have work to do, so why bother. I bet you the new
cake will be released very soon. Not so long ago it was only about
40% complete now it is almost 100% and wont be long until it gets
released as stable.
Cheers
Marcus
On Sep 6, 5:43 pm, Dérico Filho <uldericofi...@gmail.com> wrote:
> Well... 1.2 is yet a Release Candidate, although a very stable and
> robust release candidate, but yet release candidate.
> The main reason that it is kept on this name is because there might
> be, yet, some hidden flaws in it. Flaws that neither you nor I know in
> it... That could actually jeopardise your customer's system.
> He is not willing to take the risks... I would not be willing to take
> the risks on his shoes as well...
> > I have a client that won't let me use 1.2 because 1.1.19 is tagged as
> > stable whereas 1.2 is RC2...
> > I tried and tried to explain to him the many reasons why it would be
> > better and more efficient and more secure etc... to use 1.2 but to no
> > avail since all he can see is the 'stable' tag ...
> > So I was wondering if any one had any insight on when the 1.2 version
> > would be tagged as stable.
> > I really don't want to go back working with 1.1 :( ...
> > I know the work put into this framework and all I'm asking if there is
> > a chance for a stable tagged version within the forthcoming month
> > since this would allow me to advocate 1.2 and save myself some
> > trouble ...
> > thanks
> > ps. I know I'll probably get answers like : 'it'll be out when it'll
> > be out', or 'just change client' :) but if the release is close I'd
> > hate developing for 1.1.
> > ps2. And I surely would like to help for the release but I
> > unfortunately miss time and skills.
and I tried to explain that stable means 'considered stable' and that
RC2 was working perfectly for we had to do. I think they would have
preferred me to craft custom code which would have been far less
secure and stable than using cakephp but that would not have been
tagged anything as it was custom ...that's how stupid they are imo,
I'm not that a good programmer but good enough to get work, so I won't
bother myself with them anymore in the future :)
As for 'hidden flaws' I doubt that when 1.2 is tagged stable this
will mean that all possible bugs have been eradicated (this is
software in its nature I feel), so not using a software product
