We do need to address this soon. I personally am for the 'just rename it' approach as while it will be a bit more pain up front I think it will be less confusing down the road trying to explain to people what the 'old /up2 path is'. I'll be sending another email in just a bit calling for a vote on each approach so we can get the changes made before we do the GA release.

-Eric

Dustin S. wrote:
I just wanted to bring this back up as we get closer and closer to 3.0.0 GA...any status on this?

I think the way that Jason proposed is an excellent idea. svn copy up2 to uPortal and update all references in documentation to point to the new uPortal and encourage everyone to make the switch. Then at some point in the future svn delete up2. This would allow for a 'phased out' approach and give people time to update.

On Wed, Feb 6, 2008 at 7:54 AM, Eric Dalquist <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:

    That is an interesting idea. Do you think having two places in SVN
    with
    the code would cause confusion for those looking for the code for the
    first time?

    Also how many locations online have links directly into svn? Doing a
    quick search excluding mailing list archives there look to be about 10
    pages that need updating:
    http://google.decenturl.com/ja-sig.org-svn-up2-inurl

    It would of course break links in mailing list archives if we just
    moved
    versus copied and disallowed changes to the old url.

    Do others have thoughts on this approach?

    -Eric

    Jason Shao wrote:
    > On Feb 4, 2008, at 2:52 PM, Eric Dalquist wrote:
    >
    >> So way back when uPortal 2 and uPortal 3 were separate code
    bases we
    >> moved from CVS to SVN. As part of this move I had the brilliant
    idea
    >> to include a version number in the name of the SVN path for uPortal
    >> 2.X (up2) and uPortal 3.X (up3). With the very smart change in
    >> direction we made in the last year /up3 has been moved to
    >> /sandbox/portal but /up2 remains. As we get closer to a 3.0.0-GA
    >> release this may be an issue we want to address.
    >
    >
    > How about we svn copy up2 to uPortal, and doing some commit script
    > magic to make up2 read only? I'd hate to break all the existing tag
    > links (I know you can still use them if you specify the
    revision, but
    > it still breaks all the existing tag links that don't)
    >
    > Jason
    >
    > --
    >
    > Jason Shao
    > Application Developer
    > Rutgers University, Office of Instructional & Research Technology
    > v. 732-445-8726 | f. 732-445-5539 | [EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]> |
    > http://jay.shao.org
    >
    >
    >


--
You are currently subscribed to [email protected] as: [EMAIL 
PROTECTED]
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to