juneau-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Bognar <james.bog...@salesforce.com>
Subject Re: [PROPOSE] Release Apache Juneau 6.0.1-incubating RC1
Date Mon, 14 Nov 2016 15:27:45 GMT
Thanks Craig,

I've added a tl;dr section to the versioning guidelines for the most common
case:
https://cwiki.apache.org/confluence/display/JUNEAU/Versioning+guidelines#Versioningguidelines-1-Quickguidelines

On Mon, Nov 14, 2016 at 10:08 AM, Craig Russell <craig.russell@oracle.com>
wrote:

> I don’t think there is a problem with adding new features in a 6.0.1
> release.
>
> I also don’t think there is a problem with 6.124.0 release although it
> might be a bit awkward.
>
> And we might consider release cadence in making decisions on numbering.
>
> Other projects use the major (6) release for incompatible changes. Users
> may have to make code changes to their own code to use the new release.
>
> They might use minor (0) release for significant features that are still
> compatible. Things like new adapters, new versions of dependencies (java 9,
> java 10). The industry is used to projects maintaining minor releases with
> patch releases “indefinitely”. You can see other projects that issue
> multiple patch releases at the same time. They might release 6.0.44,
> 6.1.22, 6.2.13, and 6.3.2. So this would argue for minimizing the number of
> minor releases.
>
> Patch (1) releases would be used for bug fixes and small feature changes.
> Users would be expected to upgrade to the latest patch release to get bug
> fixes.
>
> I think it would be good to have some documented themes (like the above)
> so everyone knows what to expect.
>
> Craig
>
> > On Nov 14, 2016, at 6:24 AM, James Bognar <james.bognar@salesforce.com>
> wrote:
> >
> >> I thought there's 4 parts to Juneau.  Do you have examples for all the
> >> components individually and together?
> >
> > The overview document is broken down into individual sections for
> > core/server/client/microservice with lots of examples...
> > http://juneau.incubator.apache.org/site/apidocs/overview-summary.html#
> overview.description
> >
> >> I'm +1 to do it as well.  Do we want to call it 6.0.1 or 6.1?  I usually
> >> treat the third digit as a bug fix, second digit as a feature.
> >
> > That's tricky.  I did add 3 new configuration properties to ParserContext
> > (PARSER_strict, PARSER_inputStreamCharset, PARSER_fileCharset) and now
> the
> > reader-based parsers have the ability to read from byte arrays.  So it
> does
> > have new 'features'.
> >
> > I'm continuously adding new features along the way.  We may end up not
> > using the bug-fix number very often and instead end up with a large minor
> > version (e.g. 6.102.0).  I'm okay with that if everyone else is.
> >
> >
> >
> >
> > On Sun, Nov 13, 2016 at 5:51 PM, John D. Ament <johndament@apache.org>
> > wrote:
> >
> >> On Sun, Nov 13, 2016 at 5:35 PM James Bognar <
> james.bognar@salesforce.com>
> >> wrote:
> >>
> >>> Thanks Stian!
> >>>
> >>> If we did do a webinar, I would think that maybe a demo of the samples
> >> app
> >>> is a good starting point that covers all the basics.
> >>>
> >>> The samples microservice is described in detail here:
> >>>
> >>> http://juneau.incubator.apache.org/site/apidocs/
> >> overview-summary.html#Samples
> >>>
> >>>
> >> I thought there's 4 parts to Juneau.  Do you have examples for all the
> >> components individually and together?
> >>
> >>
> >>>
> >>> On a side note....I think I only got one +1 vote from Jochen on
> releasing
> >>> Juneau 6.0.1 RC1.  Can I get a quick role call?
> >>>
> >>
> >>
> >> I'm +1 to do it as well.  Do we want to call it 6.0.1 or 6.1?  I usually
> >> treat the third digit as a bug fix, second digit as a feature.
> >>
> >>
> >>>
> >>>
> >>>
> >>> On Fri, Nov 11, 2016 at 6:15 PM, Stian Soiland-Reyes <stain@apache.org
> >
> >>> wrote:
> >>>
> >>>> If we can work together on what we should present, then I am OK to do
> >> the
> >>>> actual webinar. Gives me an excuse to catch up properly with how to
> use
> >>>> Juneau!
> >>>>
> >>>> I think it could be interesting to connect to the Big Data Europe EU
> >>>> project https://www.big-data-europe.eu
> >>>>
> >>>> They are doing microservices, Docker, Linked Data and Apache Spark.
> >>>>
> >>>> Also they do lots of webinars! You might find one with me as well:
> >>>>
> >>>> https://www.big-data-europe.eu/the-open-phacts-pilot-
> >>>> second-hangout-for-the-health-societal-challenge/
> >>>>
> >>>> On 9 Nov 2016 6:09 pm, "James Bognar" <james.bognar@salesforce.com>
> >>> wrote:
> >>>>
> >>>>>> Perhaps a webinar or something to describe what you can do with
> >>>>>> Juneau? I think the tutorial on http://juneau.apache.org/#
> >> about.html
> >>>>>> is already good - but we need to hook people first.
> >>>>>
> >>>>> I'm bad at webinars.  And I'm not sure how it would work for a
> >> project
> >>>> like
> >>>>> ours.
> >>>>>
> >>>>>> What kind of audience should we target? Linked Data people (small
> >>>>>> community) or more like general web API developer folks?
> >>>>>
> >>>>> I'm trying to target anything microservice or Docker related.
> >>>>>
> >>>>>> ApacheCon is also a good venue to present Juneau - would you
have
> >>>>>> possibility to attend that?
> >>>>>
> >>>>> I'll keep the Miami location in mind.
> >>>>>
> >>>>>> According to [1], there are six committers, which should be
> >>> completely
> >>>>>> suffcient, assuming not all of you guys are from a single company.
> >> I
> >>>>>> am more concerned, that (according to [2]), you are the only
active
> >>>>>> one:
> >>>>>
> >>>>> My concern as well.  I fully expect Peter Haumer from IBM to continue
> >>>>> contributing code around the RDF support.  The other contributors
> >> have
> >>>>> contributed in the past, but they haven't been active for a while
> >>> now.  2
> >>>>> people isn't sufficient.
> >>>>>
> >>>>>
> >>>>> On Wed, Nov 9, 2016 at 10:09 AM, Jochen Wiedmann <
> >>>>> jochen.wiedmann@gmail.com>
> >>>>> wrote:
> >>>>>
> >>>>>>> On 9 November 2016 at 14:23, James Bognar <
> >>>> james.bognar@salesforce.com
> >>>>>>
> >>>>>> wrote:
> >>>>>>>> Unfortunately, we're not having very good luck attracting
new
> >>>>>> contributors
> >>>>>>>> yet.
> >>>>>>
> >>>>>> According to [1], there are six committers, which should be
> >>> completely
> >>>>>> suffcient, assuming not all of you guys are from a single company.
> >> I
> >>>>>> am more concerned, that (according to [2]), you are the only
active
> >>>>>> one:
> >>>>>>
> >>>>>> Jochen
> >>>>>>
> >>>>>> 1: http://juneau.apache.org/#community.html
> >>>>>> 2: https://git-wip-us.apache.org/repos/asf?p=incubator-juneau-
> >>>>>> website.git;a=log
> >>>>>>
> >>>>>> --
> >>>>>> The next time you hear: "Don't reinvent the wheel!"
> >>>>>>
> >>>>>> http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/
> >>>>>> evolution-of-the-wheel-300x85.jpg
> >>>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> James Bognar
> >>>>>
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> James Bognar
> >>>
> >>
> >
> >
> >
> > --
> > James Bognar
>
> Craig L Russell
> Architect
> craig.russell@oracle.com
> P.S. A good JDO? O, Gasp!
>
>
>
>
>
>


-- 
James Bognar

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message