Yes, I have a copy of 2.6 mostly Mavenized right now. Once we're happy with the 2.6 release I'll actually be creating a temporary branch to do the work in and then merge it back in to trunk.
We don't have any commit message notification, the RSS feed from Fisheye is the best solution (better than a mailing list imo) For Jira there is a list for each project: http://www.ja-sig.org/wiki/display/JSG/Jira+Notifications -Eric Elliot Metsger wrote: > Seems like a reasonable plan to me. I understand you've already got > some Maven 2 things ready to rock once the GA is released? > > Also, is there a email list that commit messages are sent to, or are > we relying on Fisheye's feeds? I didn't see an SVN or SCM commit list > on the wiki page of email lists. > > Thanks for everyone's effort with 2.6.0! > > Elliot > > Eric Dalquist wrote: >> With the 2.6 release imminent it is time to start planning how the >> changes outlined here >> http://www.ja-sig.org/wiki/display/UP3/uPortal3+Community+Goals+and+Objectives >> >> will be carried out. >> >> I'll be detailing this plan in Jira this week but wanted to get some >> feedback here as well. >> >> The list in the wiki has been re-ordered a bit after looking at code >> and talking with other developers. The plan right now is to approach >> tasks in the following order: >> >> 1. Convert to Maven for build management >> 2. Unify the Spring configuration and usage >> 3. Code cleanup, this goes along closely with 2. Includes removal of >> deprecated code, using the externalized GAP and PersonDirectory jars >> and similar changes. >> 4. Upgrade to Pluto 1.1 >> >> I'd like to get feedback on this roadmap (either on the list or in >> the wiki). I'm also looking for ideas on naming versions in Jira. We >> have already had M1 through M4 and an RC from the sandbox code. >> Should we start with a 3.0.0-M5 and then go to a RC2 once we're at >> the RC stage? >> >> -Eric >
smime.p7s
Description: S/MIME Cryptographic Signature
