Paul McNett wrote:
> Carl Karsten wrote:
>
>> release version (.tar)
>> web update version
>> svn trunk version.
>>
>> I know they are different, I know what the difference is between release and
>> svn. I can't get a clear picture on what the web update version is.
>
>
> I'll explain it in terms of subversion, which may make in clearer. We
> could have implemented web update using subversion if we could have made
> having subversion a requirement, which we can't.
>
> But, pretend for this example that web update relies on Subversion on
> both client and server sides. We've released Dabo 0.8.3 on 12/1, and it
> had revision 3793. A week later, at revision 3812, we decided to make a
> Web Update release:
>
> svn copy http://svn.dabodev.com/dabo/trunk
> http://svn.dabodev.com/dabo/web_update
>
> We basically made a branch that contains dabo's trunk as of revision 3812.
>
> Now on the client side, Dabo's checkForWebUpdates() checks out the
> version file to determine if there's a later version:
>
> svn co http://svn.dabodev.com/dabo/web_update/dabo/__version__.py[1]
>
> If a new version was detected, Dabo checks out the new version over top
> of the running version, and quits the app. The app starts up again,
> python notices that the .pyc files are out of date, and recompiles them.
> The app begins, web update checks for the current version, determines we
> are current, and runs the app normally.
>
> Now, all the real web update is doing is saving a revision number on
> Ed's server that corresponds to the last 'blessed' subversion revision
> number (3812 in the above example). Dabo uses that revision number to
> check against the local copy, and if different it downloads the correct
> dabo tree from the server.
>
> Is this clearer or muddier?
well... it contradicts some of the conclusions I had come up with, but they
were
based on air, so it shouldn't take much to blow them away :)
>
> [1] Subversion doesn't let you check out single files, but I'm
> pretending here to make it clearer.
>
>
>> What sort of stability is expected in each?
>
>
> trunk: not stable.
> tagged release: expected to be stable.
> web update release: somewhere between trunk and tagged release.
>
so to be clear:
web update is not any sort of branch. it is just a revision of truck. maybe
even a tag.
the point of making a tagged release tarball is to reduce the amount of files
that web update has to pull over, and to update things the web update process
can't update (like itself.)
I thought the web update was to make a tagged release more stable, like just
bug
fixes, or what you get when you do "apt-get upgrade" in Ubuntu.
Without changing anything on the server side (code, servers, configs,
procedures
that Ed follows) could svn be used on the client and get the same set of
files?
(assuming you can figure out what revision, which looks like:
curl http://trac.dabodev.com/browser/trunk/dabo/__version__.py?format=txt | awk
-F= '/^_approximateRevision/ { gsub(/[~" ]/, "", $2); print $2 }'
Carl K
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
Searchable Archives: http://leafe.com/archives/search/dabo-dev
This message: http://leafe.com/archives/byMID/dabo-dev/[EMAIL PROTECTED]
