Thank you all for the feedback. This is super helpful! One question that I still have is this: do we have a bias for suggesting package rename or any package name can remain in place?
Thanks, Roman. On Sat, Aug 8, 2015 at 2:25 AM, Andy Seaborne <a...@apache.org> wrote: > Hi, > > Jena graduated 2012 with old namespaces under com.hp.hpl.jena, and some > under org.openjena, with an intention to change at the first major release > update. As new packages came along, they went into org.apache.jena but the > user facing packages remained where they were. > > We released Jena 3.0.0 last month, so 3 years. That major release was > coupled to another incompatible change (RDF 1.1 semantics) so 3.x > wasn't just to do the packages, package renaming waited until a convenient > point. > > Our users have data with (RDF) namespaces under old names - we are not > planning on changing that at all. (A general issue for all linked data.) > > I don't see it as an issue for graduation if the project has considered the > matter. > > Andy > > > On 07/08/15 23:16, Matthew Hayes wrote: >> >> Hi all, >> >> Roman Shaposhnik suggested I open a discussion on the following topic: >> >> For Apache DataFu, all of the Java classes are declared in a datafu.* >> namespace. This has been the naming convention since the DataFu project >> started in 2010. Since DataFu became part of the Apache incubation >> process, the topic has come up of moving all of the classes into a >> org.apache.datafu.* namespace. This was first discussed in January 2014 >> (see DATAFU-7) and most recently again in the past couple weeks. The >> consensus at the time last year was that it would be a huge pain for users >> and not worth the cost. It would break any script out there currently >> using DataFu. Also Jakob Homan and Russell Journey pointed out that this >> is just a convention and not all Apache projects follow it. Since we >> would >> like DataFu to graduate sometime soon it would be good to clarify what the >> requirements are on package naming conventions before we do a release. >> >> Thoughts? >> >> Thanks, >> Matt >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
