has been released to the stable channel,
while you're on it, how about updating the developer's channel as well ? it's been a long time and the dev version is fairly outdated.
you said the dev channel may be delayed a few days, it's been a few weeks !! I actually test chrome and report bugs and I'm stuck with an outdated version, please.
I guess you're working on the next platform beta6, how about "hiring" someone else to take care of Chrome (dev) since it has rapid updates ?
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
I said it would usually be at least a few days late and it would be updated time-permitting. Chrome Dev is released weekly on Tuesdays, absurdly often for a 'stable' app, but normal for a development test (which this is). It is not intended for use as a primary browser. You are welcome to use it as such, but you will have to accept the limitations (there will be annoying bugs in it, sometimes you will have to suffer with them longer than usual because updates are time-permitting to non-stable apps). If you don't like that, use the stable branch which is intended for everyday use. I don't think this needs to be explained a 4th time nor another new thread created about it.
Sometimes, the impossible can become possible, if you're awesome!
there is no annoying bugs in it,
are you suggesting I test the Stable release ?!
I created this to suggest the following:
since you are busy with PA beta6 and other Stable apps, how about assigning the Chrome dev to someone you trust? only the dev release.
I'm not asking this because I have problems, but because I want to test it.
Sometimes making love is just not enough, you have to step it up!
I think you're in danger of being flamed.
If you want to test it that badly the very nanosecond it's released then download the regular installed version. Either that or find some new hobbies. I mean come on, seriously? Use the developer version as your stable version if you must, just don't expect people, who's time you don't pay for to devote the majority of it to you, and you alone.
If Google released a new developer version every hour on the hour would you expect PA.c to update their version too?
you're the one who's risking it, but I will avoid that for now.
"the very nanosecond it's released " ?? it's two weeks outdated, I agree for a 3 to 5 days of delay.
"then download the regular installed version" oh! I didn't know this is possible, that's some news you got there!! unfortunately I'm at college and this isn't possible.
"Use the developer version as your stable version if you must" nothing is a most, I do things because I choose to.
"to devote the majority of it to you, and you alone." it's not just me.
"If Google released a new developer version every hour" do talk silly, there is the Canary build for daily updates.
Sometimes making love is just not enough, you have to step it up!
So use the local version. Testing results of the portable version are *invalid* in terms of submitting them as bugs for testing anyway as the portable version is an unofficial setup.
The choice is either
you get to use the dev build and accept that it will nearly always be outdated and updated only as time permits or (b) we ditch the dev build and just do beta and stable like we do with other apps. Those are your choices. The more people complain about it being outdated, the more likely we will switch to choice B. It's not worth the noise in the forums to support a dev build.
Online installer builds are being held for PA.c Installer 2.0.3.
Sometimes, the impossible can become possible, if you're awesome!
bug reports are valid,
and the crash handler creates the same reports in the event viewer. it's not my first time.
Sometimes making love is just not enough, you have to step it up!
That may be so, but as soon as the Google Chrome development team sees you're using a non-standard version, they going to ditch your bug report faster than you can say "PortableApps development release". It's too much hassle on their part, how can they be sure that it's not simply a problem with the portable version, and if so then they couldn't care less. Sure, they could confirm the bug in the installed version and probably most likely will but the second they can't reproduce it then it will be labeled as a PortableApps problem. That's just the way it is. John and the team don't need the extra hassle of trying to figure out what are bugs, from a development version of an application, caused by the base app itself versus the portable version.
I would be more than grateful even if portableapps.com provides just the stable version meant for use by the general public, in view of any possible constraints of resources.
I agree that a tester should use the app in its original form (nightly/weekly/whatever builds) rather than expect portableapps to package something which typically has a fleeting half-life.
If I understood Chrome's new policy, they intend to roll out stable versions every six weeks (or earlier only if there's a major security upgrade).