Hi all,
as proposed below, I went ahead and created the 2_0_X maintenance branch
from master, then set version 2.1.0-SNAPSHOT and JDK 1.8 for master.
Regards.
On 05/09/2016 17:21, Colm O hEigeartaigh wrote:
+1.
Colm.
On Mon, Sep 5, 2016 at 4:16 PM, Francesco Chicchiriccò <[email protected]>
wrote:
Hi all,
as 2.0.0.M5 is done, we'll continue as scheduled with 2.0.0, possibly this
Friday.
After that, I would like to
1. create 2_0_X for maintenance from master
2. set version to 2.1.0-SNAPHOST + Java compatibility to 1.8 on master
WDYT?
On 2016-08-24 09:54 (+0200), Francesco Chicchiriccò <[email protected]>
wrote:
Hi all,
the work towards 2.0.0 seems to be almost complete: I should be able to
finish the larger missing part (e.g. documentation as per SYNCOPE-700)
by the end of this week.
At that point I would like to cut the last milestone release 2.0.0-M5
(mainly to verify once more that the release process is tuned up) then,
after a week or two, go out with 2.0.0.
Do you see any problems with this approach?
Regards.
--
Francesco Chicchiriccò
Tirasa - Open Source Excellence
http://www.tirasa.net/
Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC, Olingo PMC,
CXF Committer, OpenJPA Committer, PonyMail PPMC
http://home.apache.org/~ilgrosso/
