On 11-07-26 01:22 PM, Marvin Addison wrote:
I like git. But, there is one caveat to be aware of. DO NOT make a branch,
merge that branch to the master, revert the merge, and then attempt another
merge to the master.
Thanks for the warning. We will endeavor to learn git with the same
proficiency and expertise that we currently have with svn. While it
may take some time, we have a number of resources to lean on and
should be able to get up to speed quickly. We'll be doing things "the
git way" in no time.
You should have only one primary pusher.
There are a few development models you can leverage with git, and
while I can't say we'll adopt a practice of a single pusher, it will
in practice be a handful at best. I imagine we'll be very close to
what we do today: the lead developer cuts releases, and there is a
backup to serve that role if needed. It's all policy at the end of
the day anyway.
I would recommend some investigation into git and bazaar, as
bazaar looks like it's as functional as git, without the quirks.
While there may be a reasonable case for bzr, it's not even on the
table. We're considering git based on developer experience, the
community and tools around GitHub, and consistency with other open
source, including Jasig, projects.
Yeah, that definitely makes sense for cas then.
M
--
Trenton D. Adams
Senior Systems Analyst/Web Software Developer
Navy Penguins at your service!
Athabasca University
(780) 675-6195
:wq!
--
This communication is intended for the use of the recipient to whom it
is addressed, and may contain confidential, personal, and or privileged
information. Please contact us immediately if you are not the intended
recipient of this communication, and do not copy, distribute, or take
action relying on it. Any communications received in error, or
subsequent reply, should be deleted or destroyed.
---
--
You are currently subscribed to cas-dev@lists.jasig.org as:
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-dev
