Hi,
I support this plan as well… A stable release with XML/RPC and switch
to AVRO later…
thanks, Luca> On Jun 14, 2016, at 2:28 PM, Lewis John Mcgibbney <lewis.mcgibb...@gmail.com> > wrote: > > ACK > > On Tue, Jun 14, 2016 at 1:25 PM, Chris Mattmann <mattm...@apache.org> wrote: > >> +1 to release as 1.0 and also to do a press release >> with Sally >> >> >> >> >> >> On 6/14/16, 4:19 PM, "Tom Barber" <tom.bar...@meteorite.bi> wrote: >> >>> Hi folks, >>> >>> Something we've mulled over for a while now is when to call OODT 0.x -> >> 1.0. >>> >>> Some of us feel we've reached that point, the code base is largely stable >>> and feels like feature complete enough to call it 1.0, so I would like to >>> release it. >>> >>> Part of the reasoning for this is we have a number of large changes in the >>> pipeline, including: >>> >>> Revamped OPSUI >>> Internal messaging implementation >>> Replace XMLRPC with Avro >>> New curation app >>> A bunch of new file manager backends >>> >>> and more. >>> >>> Releasing 1.0 would allow us to then start work in revamping the trunk to >>> implement these features, that would include a number of sizeable >>> architecture changes under the hood. >>> >>> Does anyone have any great argument against releasing 1.0? I figure I >>> should ask before getting into the release cycle. >>> >>> Cheers >>> >>> Tom >> >> > > > -- > *Lewis*
signature.asc
Description: Message signed with OpenPGP using GPGMail
