They are actively working on the stable release (the one that is in Beta now). My guess would be a month or two. Maybe less. I was referring to the stable release of Chrome, not the gallery (I assume the gallery will go out of beta once the beta goes to stable).
☆PhistucK On Sat, Jan 2, 2010 at 05:02, Jon Stritar <[email protected]> wrote: > On Thu, Dec 31, 2009 at 2:23 PM, PhistucK <[email protected]> wrote: > >> 1. Yes, but it should be optional (or a check box that says "Expose the >> e-mail to the developer" or something similar). >> > > Users don't have to reveal their email address-- the gallery could email > responses for me. > > >> 2. You can upload a new extension without publishing it. IDs can be >> sniffed (location.hostname in the background page) instead of being hard >> coded. >> > > The issue I have is that I'm not able to install the actual built extension > that is about to be published. The only way I can get a copy of it, built > with the production ID / private key, is by publishing and downloading it > like everyone else. If I use my own private key, the extension will be > installed side-by-side and not upgrade the released extension when I test > locally. It's scary not being able to get the crx before publishing it-- > what if I uploaded the wrong zip without realizing it? My extension does not > use the IDs itself, so hard-coding is not an issue. > > >> 3. The parts that are updated are of the other fields except for the >> actual extension. If the version is also updated without actually publishing >> that version - this is a bug and you should file it on new.crbug.com(after >> you searched for it on >> crbug.com) >> > 4. Yes. I imagine they also thought of that, but it is too much work for >> the initial introduction of the gallery, maybe for Chrome 5 (or in an >> unrelated workflow, in a few months or after the upcoming stable hype is >> over). >> 5. They stated that they will be adding more statistics, but it will >> probably be after the upcoming stable hype. >> > > Nice.. do you know the time frame on the stable release? > > >> ☆PhistucK >> >> >> On Thu, Dec 31, 2009 at 18:19, Jon Stritar <[email protected]> wrote: >> >>> Nice job with the extension gallery! It looks nice and I think it'll >>> shape up into a great place to find and publish extensions. I released a few >>> upgrades to my extension a couple weeks ago and have some comments based on >>> my experience... I hope they can be taken into consideration to make the >>> gallery even more effective. >>> >>> >>> 1. There needs to be a way to contact people who comment on your >>> listing. Most people report bugs by leaving a comment and not going to >>> the >>> support link. Developers need a way to contact them, other than by >>> posting >>> more comments- users don't go back to them very often. >>> 2. Updates are very hard to test if you didn't upload your own >>> private key when first releasing the extension. I didn't upload one, so I >>> have no way to build the extension with the live extension ID except by >>> publishing the extension to everyone. I also can't download old versions >>> of >>> the extension from the dashboard. Together, this makes it difficult to >>> test >>> upgrade and migration code. I need to maintain my own list of old >>> extension >>> versions that are built with a separate testing key, hoping that they >>> reflect what's released. I think this is an important issue... we should >>> either be able to download the private key, or better yet, we should be >>> able >>> to install the new extension from the dashboard before publishing it, >>> along >>> with historical versions. >>> 3. The release work flow is not very clear. This builds off the last >>> item a bit. My understanding of it is that after I upload a new version >>> of >>> the extension, people can't actually download it until I click publish, >>> but >>> part of the main page updates before hitting publish (like the version >>> being >>> displayed... but not the version being downloaded). Right now the work >>> flow >>> seems centered around designing the listing page, but we should think of >>> it >>> as an overall release work flow. >>> 4. There should be a way to roll-back or revert a particular version. >>> This item combined with (3), (4) and the auto-updating makes for a very >>> stressful upgrade process. If there's a bug that we didn't catch, which >>> is >>> more likely because of the difficulty in testing, people immediately >>> start >>> upgrading to it. Testing and fixing this could take a while one again >>> because of (3), so sometimes its nice to be able to pull a version. I'm >>> scared to hit unpublish- I don't know what it does (probably because the >>> workflow is unclear)( other than pull the entire listing. >>> 5. It would be nice to see more statistics for both the ratings and >>> users in the developer console. For example, how many people rated it >>> 0,1,2,3..., or how ratings and users change over time. >>> >>> I hope these comments are useful. >>> >>> Happy new year, >>> >>> --Jon >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Chromium-extensions" group. >>> To post to this group, send email to >>> [email protected]. >>> To unsubscribe from this group, send email to >>> [email protected]<chromium-extensions%[email protected]> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/chromium-extensions?hl=en. >>> >> >> > -- You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en.
