👍
On Tue, Aug 15, 2017 at 8:39 AM, Sijie Guo wrote:
> Added a page on website about the release schedule :
> http://bookkeeper.apache.org/community/releases
>
> Marked the BP-13 as accepted, since there is no objections to this. Let's
> try out this release plan in 4.6.0.
>
> - Sijie
>
> On Mon,
Added a page on website about the release schedule :
http://bookkeeper.apache.org/community/releases
Marked the BP-13 as accepted, since there is no objections to this. Let's
try out this release plan in 4.6.0.
- Sijie
On Mon, Aug 14, 2017 at 1:59 AM, Enrico Olivelli
wrote:
> Let's do it.
> Ji
Let's do it.
Jia if you want to manage ir for me it us ok. I would try for 4.7 or 4.5.1
Enrico
Il lun 14 ago 2017, 08:50 Sijie Guo ha scritto:
> I updated the wiki page to reflect what Matteo suggested - 3 months per
> release and 4 releases per year.
>
> so the release schedule will be:
>
> -
I updated the wiki page to reflect what Matteo suggested - 3 months per
release and 4 releases per year.
so the release schedule will be:
- 4.6.0 : August 2017 - November 2017
- 4.7.0 : November 2017 - February 2018
- 4.8.0 : February 2018 - May 2018
- 4.9.0 : May 2018 - August 2018
If there is
Matteo,
Thank you for your comments. Make sense to me. Will update the BP if there
is no other suggestions.
Sijie
On Aug 11, 2017 9:33 AM, "Matteo Merli" wrote:
I would suggest to do quarterly releases (eg: every 3 months), since that
seems to me a good tradeoff ratio between planning and agil
I would suggest to do quarterly releases (eg: every 3 months), since that
seems to me a good tradeoff ratio between planning and agility of shipping
new features/improvements.
Matteo
On Fri, Aug 11, 2017 at 4:36 AM Enrico Olivelli wrote:
> Il ven 11 ago 2017, 13:10 Sijie Guo ha scritto:
>
> >
Il ven 11 ago 2017, 13:10 Sijie Guo ha scritto:
> Folks, please take a look at this. We need to decide the schedule for
> 4.6.0.
>
Maybe we can take 4.3 clients as compatible baseline for 4.6.
What is the next step?
Shiuld you call a vote ?
Enrico
> - Sijie
>
> On Mon, Aug 7, 2017 at 6:59 PM
Folks, please take a look at this. We need to decide the schedule for 4.6.0.
- Sijie
On Mon, Aug 7, 2017 at 6:59 PM, Sijie Guo wrote:
> Hi all,
>
> First thanks everyone who contributed to 4.5.0 in the past year, and
> especially thanks JV for spending time doing the release. The first release
On Thu, Aug 10, 2017 at 2:12 AM, Enrico Olivelli
wrote:
> Il gio 10 ago 2017, 10:09 Sijie Guo ha scritto:
>
> > yes, it is end-of-life. For example, currently we kept all the release
> > versions since 2011? but I believe there is no one still running releases
> > like 4.0.* and 4.1.*, even 4.2*
Il gio 10 ago 2017, 10:09 Sijie Guo ha scritto:
> yes, it is end-of-life. For example, currently we kept all the release
> versions since 2011? but I believe there is no one still running releases
> like 4.0.* and 4.1.*, even 4.2*.
Idea: shall we do some kind of survey anout the versions in use
yes, it is end-of-life. For example, currently we kept all the release
versions since 2011? but I believe there is no one still running releases
like 4.0.* and 4.1.*, even 4.2*. We definitely need to clean up those old
releases and mark them as EOL (no more support from the community). If we
decide
Thanks for this. It looks clear in the link. We could discuss the blue
items in the meeting.
BTW, what is EOL stand for? End of Life?
On Wed, Aug 9, 2017 at 2:45 PM, Sijie Guo wrote:
> I drafted a BP to adopt the Kafka one. I also highlights the content that
> might require discussions in blue i
I drafted a BP to adopt the Kafka one. I also highlights the content that
might require discussions in blue in the wiki page:
https://cwiki.apache.org/confluence/display/BOOKKEEPER/BP-13+-+Time+Based+Release+Plan
Also I listed following points that require discussion for people to check
them easie
It would be great.
Thank you
Enrico
Il mar 8 ago 2017, 09:24 Jia Zhai ha scritto:
> +1 to adopt it. All the benefits seems reasonable.
>
> On Tue, Aug 8, 2017 at 9:59 AM, Sijie Guo wrote:
>
> > Hi all,
> >
> > First thanks everyone who contributed to 4.5.0 in the past year, and
> > especially
+1 to adopt it. All the benefits seems reasonable.
On Tue, Aug 8, 2017 at 9:59 AM, Sijie Guo wrote:
> Hi all,
>
> First thanks everyone who contributed to 4.5.0 in the past year, and
> especially thanks JV for spending time doing the release. The first release
> candidate of 4.5.0 is finally ou
Hi all,
First thanks everyone who contributed to 4.5.0 in the past year, and
especially thanks JV for spending time doing the release. The first release
candidate of 4.5.0 is finally out of review now. We are almost there.
We eventually merge the major features from 3 main folked branches
(Salesf
16 matches
Mail list logo