Folks,

Currently, issues marked for "4.0" in JIRA represent work that was
done for what was known as the "4.0 branch" in SVN (now known as the
"feature-cas4api" branch in Github).  This was a pretty large scale
re-architecture of the CAS product.  Lots of great work went into this
branch, however given the current consensus on a more modest major
release it seems unlikely that the "feature-cas4api" branch and the
associated "4.0" JIRA issues will culminate into a GA release in the
near term.

Given community consensus on the near term major release as
represented in the CAS Roadmap, and the complications of cleaning up
the old "4.0" JIRA issues, perhaps for sanity's sake we should leave
the JIRA issues as is, and simply skip to 5.0 for what is to be the
next current major release target.

Otherwise, as was pointed out previously on cas-dev, we'll need a
fairly large (arguably non-productive) effort to clean up JIRA for
"4.0" while somehow preserving the history.  Shortness path to that
may be to skip over "4.0" and label our next major release 5.0 both on
the Roadmap and in JIRA.

I'm happy to "fix" JIRA and the Roadmap if there is consensus that
this is the best way to proceed.

Committer vote?  Other paths?

Best,
Bill

https://wiki.jasig.org/display/CAS/CAS+Roadmap

-- 
You are currently subscribed to cas-dev@lists.jasig.org as: 
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/cas-dev

Reply via email to