Hooray, thanks Mark. - a
On Tue, Aug 11, 2009 at 1:22 PM, Mark Larson (Google)<m...@chromium.org> wrote: > Yes, I think we can add something so each channel has a persistent URL. I'll > discuss with Aaron offline. > > On Sat, Aug 8, 2009 at 00:17, Darin Fisher <da...@chromium.org> wrote: >> >> On Fri, Aug 7, 2009 at 11:59 PM, Aaron Boodman <a...@chromium.org> wrote: >>> >>> Ok, sorry I got defensive. Short answer is we don't know if it can >>> handle the load. I will add a bug to myself to investigate. >> >> Oh, I didn't think you were overly defensive... >> >>> >>> Do you have any opinion on adding the tags? I guess the cost would be >>> that when we do new releases the release manager would have to update >>> the tag. >> >> It sounds like a reasonable request to me. >> -Darin >> >>> >>> - a >>> >>> On Fri, Aug 7, 2009 at 11:45 PM, Darin Fisher<da...@chromium.org> wrote: >>> > I totally agree. Reducing the cost of maintaining docs is very nice >>> > indeed >>> > ;-) >>> > -Darin >>> > >>> > On Fri, Aug 7, 2009 at 11:36 PM, Aaron Boodman <a...@chromium.org> wrote: >>> >> >>> >> We can put a cache in front of it if needed. Actually I'd like to put >>> >> something dumb and simple in front of it anyway, so we could have >>> >> shorter URLs that aren't tied to viewvc. >>> >> >>> >> But I think having the docs be checked in and not having a separate >>> >> deploy step is worth some extra complexity on the frontend. In Gears >>> >> the docs being out of date, or out of sync with the various versions >>> >> was an annoying problem. >>> >> >>> >> - a >>> >> >>> >> On Fri, Aug 7, 2009 at 9:55 PM, Darin Fisher<da...@chromium.org> >>> >> wrote: >>> >> > This is pretty cool, but my experience with ViewVC is that it is >>> >> > kind of >>> >> > slow. Do we know if it can handle the additional load this will >>> >> > generate? >>> >> > -Darin >>> >> > >>> >> > On Fri, Aug 7, 2009 at 3:23 PM, Aaron Boodman <a...@chromium.org> >>> >> > wrote: >>> >> >> >>> >> >> Hi all, >>> >> >> >>> >> >> I was wondering if the release managers could add a tag in >>> >> >> Subversion >>> >> >> for each of the stable, beta, and dev release channels. I want a >>> >> >> ViewVC URL that I can give people that will always refer to the >>> >> >> version of the code that is on stable (or whatever) at that moment. >>> >> >> >>> >> >> The reason I want to do this is because the extensions possee is >>> >> >> checking our docs into source control, so that they can be viewed >>> >> >> live >>> >> >> from viewvc. They're still in progress, but you can see them >>> >> >> starting >>> >> >> to come together here: >>> >> >> >>> >> >> >>> >> >> >>> >> >> http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/docs/index.html >>> >> >> >>> >> >> The cool thing about this approach is that when we branch releases, >>> >> >> the docs from trunk will be branched too. So the docs for a certain >>> >> >> release area always with the code for that release. >>> >> >> >>> >> >> If we had the aforementioned tags, the canonical URL for, eg, the >>> >> >> stable extension docs could just be: >>> >> >> >>> >> >> >>> >> >> >>> >> >> >>> >> >> http://src.chromium.org/viewvc/chrome/branches/stable/src/chrome/common/extensions/docs/index.html >>> >> >> >>> >> >> - a >>> >> >> >>> >> >> >> >> >>> >> > >>> >> > >>> > >>> > >> >> >> >> > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
