[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Pan-users] khaley/lostcoder's rep: last commit: "gtk3 compatibility
Re: [Pan-users] khaley/lostcoder's rep: last commit: "gtk3 compatibility finished" =:^)
Tue, 31 May 2011 16:25:39 +0000 (UTC)
Pan/0.134 (Wait for Me; GIT 717b0ac branch-testing)
Steve Davies posted on Tue, 31 May 2011 15:16:03 +0100 as excerpted:
> On 18 May 2011 11:22, Duncan <address@hidden>
>> Since someone was asking... (see subject)
>> Of course, that doesn't mean it doesn't have bugs to squish,
>> but in /theory/ it's all there now.
> Can I confirm that this:
> Is still the "pre-release/testing" repo ?
A bit more on the repo and git in general. If you know git fairly well,
as you likely do if you use it for regular development, feel free to skip
the rest, unless you wish to teach me a bit more about it. =:^)
Note however that the above is the general git repository, which has
multiple branches. Unlike say SVN, git branches are about as cheap as
tags to branch, maintain as long as needed, and remerge or throw away when
the time comes, and one mark of a dev that knows and uses git to its
fullest is a repository with all sorts of branches, both general and for
each specific topic/feature-project if it's more than a trivial patch or
KHaley seems to be such a developer, as if I recall from last I checked,
there were at least the three general branches (master, which is the usual
git default, testing, and a for-upstream-commit branch), plus a number of
topic branches of various types. The topic branches won't be very
interesting to most users unless they're following that specific topic
exclusively, while one would choose the general branch based on desired
stability. I believe testing to be the freshest but least stable, the
branch the various sub-branches will be merged with first. Master, as the
default branch, should be more stable as it should have at least been
tested by khaley and anyone like me foolish enough to try testing. As
such, master's probably what most here would be interested in. The for
upstream branch would be the most stable, with commits already tested
stable for some period by various master branch users and judged ready for
PKovar to pull directly into the upstream gnome repo.
The upstream gnome repo in turn should at least in theory be pretty much
release-tag ready at any time, stable as an upstream release could be
expected to be, but of course some weeks behind khaley/lostcoder master,
which is I'd guess hours to days behind testing. And of course distro
releases are generally months behind upstream but may include their own
patches designed to integrate them better with the distro.
And of course ATM we now have HMueller's newest development, bin-posting,
as well. AFAIK it isn't even in khaley testing yet, but then from the
still some bugs to squish comment, he's probably not ready for it to be,
either. Given the size of the changes in such a project, it'd be ideal
for a topic/project branch when khaley first pulls it, keeping its
development on a separate branch as well as merged into testing, until
khaley at least tests it too.
So pick your poison, stale^h^hbleness vs. up-to-the-moment features.
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman