I posted a note recently about an epic or story to ensure that we get the major documentation updated. With the size of the 2->3 change I think we need to provide documentation. I have some started for the security section and Bruno pointed me to a skeleton page for the rest but I think the documentation needs to be completed before release.
Perhaps it makes sense to create an epic for the release where we can hang all the tasks that need to be completed as an easy way to track them. I was wondering how to do the update of the documentation in a way that does not step on the current documentation. Claude On Sun, Jul 19, 2015 at 7:07 PM, Andy Seaborne <[email protected]> wrote: > How is it going? We seem to have converged for JENA-990 now and the > jena-core/jena-permissions split feels reasonable. > > The PR backlog is reduced, though #47 is still outstanding. > > Doing RC1 of a release this week would fit well for me. And hopefully, > enough bandwidth to create a clean maven repository. > > Comments? > > Andy > > > On 14/07/15 15:01, Andy Seaborne wrote: > >> Works for me. >> >> If any changes to jena-core can be done first, we can make sure things >> are stable and also not overlap. >> >> It'll take me a few days to clear what backlog I can, or assess that >> just before a release is not a good time for a change. >> >> + Documentation bulk changes done (by the power of "perl -i"). >> >> + AnonId done. >> >> (It seems that PRs are not always getting closed/mark merged on github - >> I haven't found the common factor - #80 and #86 aren't behaving, maybe >> it just taking a very long time to propagate) >> >> Andy >> >> On 14/07/15 10:45, Claude Warren wrote: >> >>> I would like to get JENA-990 (Rename UpdateDeniedException) into Jena3 >>> I would also like to clean up the permissiosn system so that it uses the >>> exceptions described in JENA-990 and I would like to clean up the >>> node/triple handling. the Permissions code was originally designed to be >>> graph implementaiton agnostic. So there is a layer of complexity that >>> can >>> be removed and should make it faster. >>> >>> I started work on 990 yesterday. I think I can have all of the above >>> completed by end of week. (Unit tests included) >>> >>> Claude >>> >>> On Mon, Jul 13, 2015 at 4:36 PM, Andy Seaborne <[email protected]> wrote: >>> >>> After some build-wrestling today, I am hopeful we can do a Jena3 release >>>> soon. >>>> >>>> There are a few things I know need doing: >>>> >>>> 1. Documentation : com.hp.hpl.jena => org.apache.jena >>>> >>>> This is a bulk change - except for [1] !! >>>> Add a big statement to the front page linking to the migration page. >>>> >>>> 2. AnonId (JENA-986, JENA-987) >>>> >>>> This removes a linkage between the core of the core (graph) and the RDF >>>> API. There is PR#86 for this. >>>> >>>> >>>> As time and understanding permits I will try to process other PRs as >>>> well. >>>> >>>> I'd very much like to get #82 (JENA-979) in. >>>> >>>> (#47 / JENA-901 / LPDRuleEngine) could do with another review - there >>>> is a >>>> bit labelled FIXME) >>>> >>>> I have a bit of time this month so I'm able to RM the release. >>>> >>>> What else must be done before we can go for Jena 3.0.0? >>>> >>>> Closing any JIRA that are done (thanks Claude for the recent batch) is >>>> helpful. >>>> >>>> Andy >>>> >>>> [1] >>>> http://jena.staging.apache.org/documentation/migrate_jena2_jena3.html >>>> >>>> >>>> >>> >>> >> > -- I like: Like Like - The likeliest place on the web <http://like-like.xenei.com> LinkedIn: http://www.linkedin.com/in/claudewarren
