On 28/12/2016 14:12, Tobias Soloschenko wrote:
Hi Martin,

doh! Yees you are absolutley right. My fault. It is only required if you check out the github repository.

@Andrea sorry that I caused confusion.

@Martin thanks for that hint - seems that I really enjoyed the vacation to run into such thoughts. ;-)

Don't worry. It's nice to see I'm not the only one experiencing these "creative" moments :D
kind regards

Tobias

Am 28.12.16 um 14:07 schrieb Martin Grigorov:
Hi Tobias,

The eclipse module is not a child of the parent pom, so it is not released
at all with Wicket distro.
It is released by itself only when there are any changes in it.

Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov

On Wed, Dec 28, 2016 at 2:04 PM, Tobias Soloschenko <
[email protected]> wrote:

Hi Andrea,

is the release version also staged with 4-SNAPSHOT? I think this can't be, because maven does not allow to release versions with -SNAPSHOT. So is the
staged version released with version 4?

kind regards

Tobias

Am 27.12.16 um 14:56 schrieb Andrea Del Bene:

Master branch has 4-SNAPSHOT as version. Staging repository (
https://repository.apache.org/content/repositories/orgapachewicket-1081/)
does not contain wicket-eclipse-settings module.


On 27/12/2016 12:10, Tobias Soloschenko wrote:

Hi Andrea,

no I just saw that in master the version was 4-SNAPSHOT. There are no
requirements to release new versions each time. 1 was for 6.x, 2 was for 7.x and 3 was for master (8.x) branch. If version 4 is in the release now this is nothing bad, but it is not required to be released each time with
wicket.

Can you have a look at the released master version? If there is a 4 we also need to release wicket-eclipse-settings 4 - otherwise there will be
issues for all who downloaded the eclipse-settings module from the
marketplace - there will be an eclipse error saying that version 4 is not
available.

kind regards

Tobias

Am 27.12.2016 um 09:56 schrieb Andrea Del Bene <[email protected]>:
I'm afraid I wasn't aware of this module. Is there something specific
to do for the release?


On 27/12/2016 09:33, Tobias Soloschenko wrote:
Hi Andrea,

did you took version 3 of wicket-eclipse-settings for release 8-M3?

kind regards

Tobias

Am 26.12.2016 um 20:51 schrieb Andrea Del Bene <[email protected]>:
ok, I've manually closed it.


On 26/12/2016 20:02, Andrea Del Bene wrote:
@Martijn

I have a problem with staging repository. Apparently I can create it
but it's not exposed (https://repository.apache.org
/content/repositories/orgapachewicket-1080). Any clue?


On 26/12/2016 17:09, Maxim Solodovnik wrote:
Thanks a lot Andrea!

WBR, Maxim
(from mobile, sorry for the typos)

On Dec 26, 2016 23:08, "Andrea Del Bene" <[email protected]>
wrote:

everything went fine....except for the staging repository :-(. i
will try
later this evening .

On 26 Dec 2016 15:21, "Andrea Del Bene" <[email protected]>
wrote:

I've started the release right now. Give me a minute...a long one
:-)


On 26/12/2016 05:58, Maxim Solodovnik wrote:
Hello,

Any news on topic?

On Fri, Dec 23, 2016 at 5:48 PM, Tobias Soloschenko <
[email protected]> wrote:

One short note:

eclipse-settings version have been increased, but there are only
1,2,3 -
3
is for wicket 8 - so if the build fails go for version 3

kind regards

Tobias

Am 23.12.2016 um 10:15 schrieb Andrea Del Bene <
[email protected]>:
Yes, I can confirm that. But it's the first time I try to make a

release
so it might take some time :)
On 22/12/2016 23:07, Martijn Dashorst wrote:
AFAIK the release script can be run by Andrea. There were some
things
with passwords for services used (repository.a.o) but those
are not
insurmountable.

Martijn


On Thu, Dec 22, 2016 at 8:24 PM, Martin Grigorov <
[email protected]
wrote:

Hi Tobias,

According to the mail from Jim (legals director) any project
that

already
uses json.org should get rid of it until April 2017 (6 months
from the

announcement).
I don't mind merging the OpenJson branches now, but only if
we have
few
weeks to test before making a release.
I just want to avoid something like: you merge the branches
today and

few
days later Martijn cuts the release.

@Martijn and Andrea: what is the current state of the release
scripts?
Martijn said that you will work on them at ApacheCon to make it
possible to
run on Ubuntu too. It would be good if more than one person can
make a

release.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov

On Thu, Dec 22, 2016 at 8:07 PM, Tobias Soloschenko <
[email protected]> wrote:

Hi

should the release already exclude json.org or not - that
would be
my
question.

kind regards

Tobias

Am 22.12.2016 um 17:08 schrieb Andrea Del Bene <
[email protected]
:

I might find some time before the new year but I am not 100%
sure

yet.
Andrea.
On 22/12/2016 08:16, Maxim Solodovnik wrote:
We could use org.json without legal issues until April
2017.

Good to know :)

So as I can see no blockers for 7.6.0 release :))

On Thu, Dec 22, 2016 at 2:04 PM, Martin Grigorov <

[email protected]>
wrote:
Hi,
My personal opinion: the OpenJson change should be merged
to the
"production" branches only if we have some time to test
in those

branches.
I prefer to merge them right after the release of 6.26/7.6
so we

have

time
to find any issues.
I don't want this change to be merged and two days later
to make

a
release.
We could use org.json without legal issues until April 2017.

My 2c.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov

On Thu, Dec 22, 2016 at 4:28 AM, Maxim Solodovnik <

[email protected]>
wrote:

Hello Sven,
Maybe It's time to schedule the release? :)))
It was sort of scheduled [1]
I guess WICKET-6287 [2] is resolved now
And I really would like to have WICKET-6056 [3] changes
:)))

I believe both Wicket* and OpenMeetings releases would
be great
Christmas/NY presents for our users :)

WDYT?

[1] http://markmail.org/message/tzl2pdmywjsqd3vr
[2] https://issues.apache.org/jira/browse/WICKET-6287
[3] https://issues.apache.org/jira/browse/WICKET-6056

On Wed, Dec 21, 2016 at 9:58 PM, Sven Meier <
[email protected]>
wrote:

Hi Maxim,
your on the right list :P
There's just no ETA for the next release yet.

Have fun
Sven



On 21.12.2016 15:55, Maxim Solodovnik wrote:
Am I asking wrong mailing list? Or maybe there are no

estimates? :)
WBR, Maxim
(from mobile, sorry for the typos)
On Dec 19, 2016 21:13, "Maxim Solodovnik" <
[email protected]

wrote:
Hello All,

Do you have any estimates for the subject?
Maybe this can be released before NY? :)))

--
WBR
Maxim aka solomax


--

WBR
Maxim aka solomax





Reply via email to