The trunk code freeze is over. The 4.0.0 tag is set, the 4.0.0 maven
artifacts should be in the central maven repo in a few hours and the
downloads are posted: http://downloads.jasig.org/uportal/uPortal-4.0.0/
If you can do any sanity checks on any of these it is more than welcome.
We'll be
I'd like to see uPortal's source code moved to git and hosted on GitHub.
There have been quite a few folks that have been working on uPortal 4,
uMobile or are otherwise interested that have asked about using git.
After looking into it a bit more I think it would be a very valuable
change for
+1
On 08/31/2011 02:26 PM, Eric Dalquist wrote:
I'd like to see uPortal's source code moved to git and hosted on
GitHub. There have been quite a few folks that have been working on
uPortal 4, uMobile or are otherwise interested that have asked about
using git. After looking into it a bit more
+/- 0
I think making this change so soon after the uPortal 4.0.0 release, is a
mistake. I think it would be better to let that release simmer for a
while to shake out if there were any major problems.
If this vote was to take place in a month, or at least 2 weeks after
some university was
+1
- Original Message -
From: Jen Bourey jennifer.bou...@gmail.com
To: uportal-dev@lists.ja-sig.org
Sent: Wednesday, August 31, 2011 12:50:43 PM
Subject: Re: [uportal-dev] [VOTE] Move uPortal source to GitHub
+1
On Aug 31, 2011, at 12:26 PM, Eric Dalquist wrote:
I'd like to see
There's a command line interface, cool.
Does git have anything like svn:externals? A quick search brought up a
few pages that lead me to believe it might be an issue, though if a
read-only SVN repository is still part of the plan, maybe that covers
it. I'd have to do more research.
On Wed, Aug
I'm curious as yo why the concern about the closeness to the 4.0
release? I was actually thinking that doing the switch as soon as
possible after 4.0 would be better as it would give more time for
developers to get used to the change before a 4.0.1 is needed.
-Eric
On 8/31/11 3:05 PM, Cris J
Call me pessimistic, but... there seem to be two givens in the world of
software that concern me with this change at this time.
1) a .0 release is notoriously not perfect and is usually followed on
very quickly by a .1 release shortly after to fix some glaring bug that
will prevent most
Not officially voting just yet as I'd like to see this really thrashed out.
Switching to a different SCM system can isolate users who don't know how to use
it. Git is complex. Much more so than Subversion. It may be more powerful but
that doesn't mean a lot to the average user who wants to fix
