Nice Tom On Tuesday, January 5, 2016, Tom Barber <tom.bar...@meteorite.bi> wrote:
> Cool. Alright, I've added tentative version numbers and tentative release > dates for those versions in Jira and reminders in my calendar, both are > subject to change, but at least it gives us a good idea. > > Tom > > On Tue, Jan 5, 2016 at 1:16 PM, Cinquini, Luca (398G) < > luca.cinqu...@jpl.nasa.gov <javascript:;>> wrote: > > > +1 from me too. I like the idea that if I make a commit, I know it will > be > > in release within a certain time frame. > > thanks, Luca > > > > On Jan 5, 2016, at 4:34 AM, Lewis John Mcgibbney < > > lewis.mcgibb...@gmail.com <javascript:;>> wrote: > > > > > Sounds like a great idea Tom. The tentative release projections can be > > set > > > in Jira. > > > > > > On Mon, Jan 4, 2016 at 3:15 PM, Tom Barber <tom.bar...@meteorite.bi > <javascript:;>> > > wrote: > > > > > >> Hello folks, > > >> > > >> I was wondering earlier if it would be worth proposing we move OODT > to a > > >> quarterly or 2 monthly release cycle where we pencil in release dates > in > > >> Jira and cut off on those dates. > > >> > > >> Clearly there isn't a massive amount of commit action on OODT > currently, > > >> but when it does happen it can easily go months before a release see's > > the > > >> light of day at which point people end up using unstable snapshots and > > then > > >> they fall over and it makes everyone sad. At least if we had scheduled > > >> release dates then people would know when the next release with their > > fix > > >> is coming. > > >> > > >> I'll volunteer to be release manager and personally I'd support every > > other > > >> month as a release schedule, but I'm interested to know what others > > think. > > >> > > >> Thanks > > >> > > >> Tom > > >> > > > > > > > > > > > > -- > > > *Lewis* > > > > > -- *Lewis*
