[sakai2-tcc] Status of Websphere/DB2 support for 2.8.0

John Bush john.bush at rsmart.com
Wed Mar 16 09:28:19 PDT 2011 

I definitely prefer 1 and then 2.  This stuff is cross cutting, and taking
it out and moving it into contrib, will make it harder for someone to take
it up again.  So I think its better to wait for IBM.  I think either option
will stir it up enough to make a more hardlined decision in a future
release.

On Wed, Mar 16, 2011 at 8:00 AM, May, Megan Marie <mmmay at indiana.edu> wrote:

> I have contacted Howard Baker about this discussion and will keep the TCC
> updated on any news on that front.
>
> I prefer option #2 since it is #1 but also includes communicating the state
> to the community broadly.
>
> ~Megan
>
> -----Original Message-----
> From: sakai2-tcc-bounces at collab.sakaiproject.org [mailto:
> sakai2-tcc-bounces at collab.sakaiproject.org] On Behalf Of Aaron Zeckoski
> Sent: Wednesday, March 16, 2011 10:27 AM
> To: Beth Kirschner
> Cc: sakai2-tcc Committee
> Subject: Re: [sakai2-tcc] Status of Websphere/DB2 support for 2.8.0
>
> Option 1 makes the most sense to me
> -AZ
>
> On Wed, Mar 16, 2011 at 10:16 AM, Beth Kirschner <bkirschn at umich.edu>
> wrote:
> > Either 1 or 2 is fine with me. The cynic in me says that option #1 will
> not do anything to solicit community support (which I think is unlikely
> anyway).
> >
> > - Beth
> >
> > On Mar 16, 2011, at 1:47 AM, Anthony Whyte wrote:
> >
> >> There are actually 5 options on the table (the Swinsburg proposal does
> not trump the original set of options by virtue of being the latest option
> proposed).
> >>
> >> PROPOSED OPTIONS
> >>
> >> 1.  Do nothing other than state in the release notes that the WAS module
> and Db2 conversion scripts are unsupported and not tested.  The hope here is
> that support will be forthcoming in time for 2.8.1.
> >>
> >> 2.  Consider the WAS module and Db2 support deprecated and state in the
> release notes and publicly via a TCC announcement that each will be removed
> as of 2.9.0 if community members are unwilling to support WAS/Db2.  If
> support materializes after 2.8.0 is released the status of WAS can be
> reviewed and changed.
> >>
> >> 3. Remove the WAS project and Db2 conversion scripts from trunk and
> 2.8.x and relocate both to contrib.
> >>
> >> 4. Remove the WAS module and Db2 scripts from 2.8.x but delay moving the
> WAS project from trunk to contrib until IBM provides a statement of how the
> plan (or not plan) to support WAS.
> >>
> >> 5. Treat the DB2 conversion script issue as separate from the WAS
> support issue.  Remove scripts from trunk and 2.8.x immediately, assuming we
> have confirmation that support for it is not going to continue.
> >>
> >>
> >> WORK REQUIRED
> >>
> >> Since we don't have an answer from IBM yet regarding their support
> plans, option no. 5 (as originally stated) should be eliminated as an
> option.  That said, I estimate the effort involved regarding options 1-5 as
> follows:
> >>
> >> 1. 15 minutes.  Append a statement in the release notes (Confluence) and
> perhaps also the release page (source.sakaiproject.org) regarding WAS/Db2
> status.  I can do this.
> >>
> >> 2. 30 minutes.  Do no. 1 plus issue a statement to the Community
> regarding WAS/Db2 deprecation.  The TCC should issue the statement via
> email.
> >>
> >> 3. Unknown.  An audit of WAS/Db2-related code/scripts has been performed
> by Jean-Francois and can be found at
> https://jira.sakaiproject.org/browse/SAK-20243.  Unfortunately the
> sub-tasks do not include the names of the tools they are meant to represent
> (it might be helpful to edit the task summary and add the tool name).  There
> are 19 projects to be touched including the kernel.  In most, but not all
> cases, the task involves deletion of a Db2 conversion script.  The kernel
> includes Db2-spiced Java code in the impl, utils and private that we would
> want to deprecate.  Db2-spiced Java code can also be found in content and
> webdav.  The SAK does not cover pom work (quite easy) required to remove the
> WAS profile.  The kernel and maintenance teams are likely candidates for the
> majority of this work.  Then there is the task of moving WAS and any scripts
> to contrib.  Chris Maurer traditionally handles this activity.
> >>
> >> 4. Unknown.  Tasks same as no. 3 above minus troubling Chris Maurer.
> >>
> >> 5. 3 hours.  Remove all Db2 conversion scripts from trunk and merge
> changes to 2.8.x.  Maintenance team and branch management would handle this
> work.
> >>
> >>
> >> Again, I recommend against pursuing options 3-5 (or some subset of them)
> at this stage in the 2.8.0 release cycle.  I prefer option 2.
> >>
> >> I also encourage the TCC leadership to contact Howard Baker <
> hcbaker at us.ibm.com> and discuss with him further the issues at stake here.
> >>
> >> Cheers,
> >>
> >> Anth
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> On Mar 15, 2011, at 11:48 PM, May, Megan Marie wrote:
> >>
> >>> It's not clear to me that we've reached consensus here.
> >>>
> >>> The last proposal was to
> >>> -  remove the WAS module from 2.8 but leave it in trunk.
> >>> - remove support for DB2  if it is confirmed support
> >>>
> >>> You'll notice a consistent message from me is that we need to strive
> >>> to do everything in our power to  release at the end of this month.
> >>> Typically, the closer to a release we are, the more scrutiny the
> >>> release seems to get and thus, we realize there are things that
> >>> should have been done but aren't.    It's at these times that I
> >>> would encourage us to understand
> >>> 1)  The scope/effort in the proposed change
> >>> 2) Who is tasked with making the change (specific name)
> >>> 3) Timeline needed to make the change
> >>> 3) Discussion on why it should be done asap.   While it might be the
> "right" thing to do, what was the risks with completing the task for a
> subsequent release (ie 2.8.1)?
> >>>
> >>> Megan
> >>>
> >>> -----Original Message-----
> >>> From: sakai2-tcc-bounces at collab.sakaiproject.org
> >>> [mailto:sakai2-tcc-bounces at collab.sakaiproject.org] On Behalf Of
> >>> Jean-Francois Leveque
> >>> Sent: Monday, March 14, 2011 10:28 AM
> >>> To: Steve Swinsburg
> >>> Cc: sakai2-tcc Committee
> >>> Subject: Re: [sakai2-tcc] Status of Websphere/DB2 support for 2.8.0
> >>>
> >>> There is still code related to MSSQL, Derby or PostgreSQL in several
> places. Found it when looking for DB2.
> >>>
> >>> Should we audit this too?
> >>>
> >>> cheers,
> >>> J-F
> >>>
> >>> Steve Swinsburg a écrit :
> >>>> May I propose a modified 3 for the WAS module? Remove from 2.8
> >>>> since we don't have time to address it before the release, but
> >>>> leave it in trunk until such time as IBM respond either way. If
> >>>> their response is negative, drop it from trunk back to contrib.
> >>>>
> >>>> The DB2 issue is separate and if we already have confirmation that
> >>>> support for it is not going to continue, then it should be removed
> >>>> immediately, much like the MSSQL have been.
> >>>>
> >>>> cheers,
> >>>> Steve
> >>>>
> >>>>
> >>>> On 10/03/2011, at 11:05 PM, Anthony Whyte wrote:
> >>>>
> >>>>> Currently the DB2 conversion scripts are incomplete.  In addition,
> >>>>> Earle Nietzel of Marist, mentioned in an email on the dev list a
> >>>>> couple of weeks ago that "IBM WebSphere support is not going past
> >>>>> 2.6.x and should probably not be used since bugs will not be fixed."
> >>>>>
> >>>>> I wrote Howard Baker at IBM and requested clarification regarding
> >>>>> IBM's current commitment regarding Sakai CLE Websphere/DB2 support.
> >>>>> He replied that he is "working with the higher ed strategy team
> >>>>> within IBM to determine what our focus should be for Sakai in 2011.
> >>>>> I should have a better idea in about a month. At that point I will
> >>>>> be able to give you a more definitive answer. Right now our focus
> >>>>> is on resolving some issues with Sakai 2.7.1 and the IBM JDK/JRE."
> >>>>>
> >>>>> Unfortunately, resolution of the question will occur only after
> >>>>> the expected release of sakai-2.8.0 on 31 March 2010.  This means
> >>>>> that at present the sakai-2.8.0 WAS module and it's companion DB2
> >>>>> conversion script are unsupported.  Presently, given the state of
> >>>>> the DB2 conversion script, no one can perform a successful DB2
> >>>>> upgrade from
> >>>>> 2.7.1 to 2.8.0
> >>>>>
> >>>>> The situation is mitigated somewhat by the absence of any known
> >>>>> Sakai CLE production instances running Websphere/DB2.  Neither
> >>>>> John Bush nor myself are aware of any production instances.  Two
> >>>>> weeks ago I polled both the production and dev lists regarding
> >>>>> Websphere/DB2 production instances.  Thus far I have received no
> replies.
> >>>>>
> >>>>> At the same time the absence of any known production installations
> >>>>> raises questions regarding the suitability of the WAS module as a
> >>>>> core CLE project.  It may well make sense to move the project out
> >>>>> of the release and re-designate it a Contrib project where it can
> >>>>> be maintained by interested community members independent of CLE
> >>>>> release timelines--but that is not for me to decide.
> >>>>>
> >>>>> Options
> >>>>>
> >>>>> 1.  Do nothing other than state in the release notes that the WAS
> >>>>> module and Db2 conversion scripts are unsupported and not tested.
> >>>>> The hope here is that support will be forthcoming in time for 2.8.1.
> >>>>>
> >>>>> 2.  Consider the WAS module deprecated and state in the release
> >>>>> notes that it will be removed as of 2.9.0 if community members are
> >>>>> unwilling to support it.  If support materializes after 2.8.0 is
> >>>>> released the status of WAS can be reviewed and changed.
> >>>>>
> >>>>> 3.  Remove the WAS module from trunk and 2.8.x and relocate it to
> >>>>> contrib along with Db2 conversion scripts.
> >>>>>
> >>>>> Option no. 2 most closely resembles past practice but others may
> >>>>> hold a different opinion on how the current situation should be
> handled.
> >>>>>
> >>>>> Cheers,
> >>>>>
> >>>>> Anthony
> >>> _______________________________________________
> >>> sakai2-tcc mailing list
> >>> sakai2-tcc at collab.sakaiproject.org
> >>> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
> >>> _______________________________________________
> >>> sakai2-tcc mailing list
> >>> sakai2-tcc at collab.sakaiproject.org
> >>> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
> >>>
> >>>
> >>
> >> _______________________________________________
> >> sakai2-tcc mailing list
> >> sakai2-tcc at collab.sakaiproject.org
> >> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
> >
> > _______________________________________________
> > sakai2-tcc mailing list
> > sakai2-tcc at collab.sakaiproject.org
> > http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
> >
>
>
>
> --
> Aaron Zeckoski - Software Engineer - http://tinyurl.com/azprofile_______________________________________________
> sakai2-tcc mailing list
> sakai2-tcc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
> _______________________________________________
> sakai2-tcc mailing list
> sakai2-tcc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>



-- 
John Bush
602-490-0470
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20110316/5a21905a/attachment-0001.html

More information about the sakai2-tcc mailing list