On 05/17/2011 05:07 PM, Eric Dalquist wrote:
Not in the next two months or so, just don't have time. I still have some re-org
changes I'd like to work on but if we want to scrap the 2.1 versioning for now
and stick trunk back to 2.0 so we have less to maintain I'm fine with that.
I'd just as well be fine with releasing 2.0.3 instead.
It'll need just the few differences from trunk backported, which will have only
minor impact on Jetspeed to realign (only the added RequestContext.getAttribute
method, which is fine).
But it depends on your goals and objectives. Doing the above would mean for
uPortal to switch (back) to 2.0.3, but technically it wouldn't make a difference.
Scraping the 2.1 trunk however doesn't make sense if you plan to work on this in
a few months anyway. So in your case I'd just take the 2.0.x branch and release
that after the minor backport changes.
Note: there are also still 2 open issues on 2.0.3 and 2.1.0 both, both of which
IMO can be bumped to a later 2.0.x and/or delegated to (only) the 2.1.0 version.
Thanks,
Ate
-Eric
On 05/17/2011 09:49 AM, Ate Douma wrote:
On 05/17/2011 04:28 PM, Eric Dalquist wrote:
In preparation for an RC of uPortal I'd like to get a M2 release of Pluto 2.1.0
cut. If there are no objections I'll start the process of staging the M2
artifacts this evening and then post a vote.
No objections from me.
We'll soon will need a release for Jetspeed 2.2.2 as well (currently
configured using Pluto 2.0.3-SNAPSHOT).
BTW: I just did a src tree compare between 2.0.3-SNAPSHOT and 2.1.0-SNAPSHOT
and the difference so far really are still only trivial, even including the
one minor API change on RequestContext (adding getAttribute call) ...
Are you still planning to do major (re)work or changes after 2.1.0?
Ate
-Eric
