1. uPortal 2 Status Andrew Petro, Yale Bill Thompson, Rutgers

2. 9/19/052 Software Maintenance and Evolution  “The majority of development … takes place after the software has seen its first release … is known as software maintenance (or software evolution)” Special Issue on Software Maintenance and Evolution, IEEE Transactions on Software Engineering, October 2005

3. 9/19/053 uPortal release process  Patch releases (frequent, no APIs change, uPortal 2.4.4)  Minor evolutionary releases (periodic, some APIs change where needed, uPortal 2.6)  Major revolutionary releases (rare, huge, uPortal 3)

4. 9/19/054 Kinds of releases  Milestone: just a build. Provide a way to talk about and see progress, a goal.  Release candidate: A build for QA and review working towards a GA release.  GA release: “General audience” or “General availability” releases – a “final” release intended for deployers.

5. uPortal 2.4.x Patches

6. 9/19/056 uPortal 2.4.x strategy  The 2.4.x release strategy has been to: fix reported issues increase portal performance and stability share fixes/optimizations with later release branches incorporate important fixes/optimizations from later releases

7. 9/19/057 2.4.x releases  August 2005: uPortal 2.4.3 Memory and performance  October 2005: uPortal 2.4.3.1 Security release to fix “CWebProxy proxies too much” issue.  Expected December: 2.4.4 Bug fixes, JDK 1.5 support

8. 9/19/058 What’s in a release?

9. uPortal 2.5.x Patches

10. 9/19/0510 uP 2.5.x releases  uPortal 2.5.1 October 2005 CWebProxy security fix Dynamic channel titles  Expected in December: uPortal 2.5.2 Bugfixes and release process engineering

11. 9/19/0511 Dynamic channel titles  Modest feature  An example of evolving the codebase

12. 9/19/0512 Pluggable stats recorder  Enable use case of multiple stats recorders in use concurrently

13. 9/19/0513 Bugs – and their resolution  WSRP consumption doesn’t work in 2.5 But until Sakai 2.1.0, what WSRP did you really want to consume?  Some JSR-168 support problems Making this more concrete Patching

14. CWebProxy security fix In uPortal 2.4.3.1 and 2.5.1

15. 9/19/0515 Proxying too much  Exploit allowed the Adversary to proxy arbitrary files on the portal filesystem as the Tomcat user, e.g. your uPortal configuration files including database passwords.

16. 9/19/0516 The fix  Restrict what paths can be set at runtime.

17. 9/19/0517 On Reporting Security Exploits  uPortal is an opensource project.  Our strength is, we thrive on, open communication, sharing  But security exploits are special: Let’s not share them until they’re fixed.  In progress: new reporting process

18. uPortal 2.6 Evolution

19. 9/19/0519 DLM enhancements  uPortal 2.5 welcomed DLM into baseline uPortal  uPortal 2.6 will include enhancements to DLM in the way managed fragments are managed

20. 9/19/0520 Fine grained permission grants  Delegating permission to publish channels to a subset of portal users.

21. 9/19/0521

22. 9/19/0522 When will uPortal 2.6 be released?  When it’s ready  When the uPortal developers (sufficiently) agree that it’s time to release a new minor release  Prediction: Spring ‘06.

23. The on-going community process “Community” means us.

24. 9/19/0524 Many ways to contribute  Many thanks to Vincent Mathieu for stepping up to produce quickstarts.

25. 9/19/0525 Lather, Rinse, Repeat: The patch/release march  Continue to incrementally improve uPortal 2.x so long as there’s interest and resources.

26. 9/19/0526 Many deployers of uP 2.x

27. 9/19/0527

28. 9/19/0528 Use cases

29. 9/19/0529 JIRA issue tracker  Bugfixes, new features, enhancements Patches Screenshots Scheduling

30. 9/19/0530 Evolving supporting infrastructure

31. 9/19/0531 Patches are a wonderful thing  Concrete, specific, technical, unambiguous

32. 9/19/0532 Evolution  Our Release Process accommodates evolutionary change for minor releases.  Some of these requirements therefore can be realized for uP 2.6, in 2-5 and 2-4 patches.  There are important opportunities here.

33. 9/19/0533 Revolution  What are the killer features that make a major, revolutionary upgrade worth it? A “no brainer” upgrade?

34. 9/19/0534 Sustainability  Direct Stakeholder Involvement  Funded Contributions  Commercial Partners