You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pivot.apache.org by Sandro Martini <sa...@gmail.com> on 2012/05/16 12:55:09 UTC
release 2.0.2 approaching
Hi all,
since yesterday I started to do usual things just before preparing a
release (running check scripts for svn, for rat, etc) ...
I'm sorry but still hadn't time to prepare and upload an updated
snapshot in my area on people.apache.org .
We are discussing on some other small things but I think that during
this week we should solve them.
Important:
the only important issue still open is:
PIVOT-850 - Fail to take input characters other than English in Mac Lion
https://issues.apache.org/jira/browse/PIVOT-850
but note that it happens only in Mac Lion, so it's not-so-bad (for
others :-) ) ...
I'm sorry here but without a Mac with Lion installed it's impossible
to reproduce and so to fix (I'm speaking for me, but probably even
other Pivot developers are in the same situation) ... volunteers here
?
Unless objections or important things that should arise, my plan is to
start the release packaging during this week-end, and publish release
candidate artifacts on my area on people.apache.org . Of course just
after this I'll start the vote (max 5 / 7 days of duration).
Please tell me if someone of us need something different or need more
time (no problem, but I have to know before starting all the work).
And now another big question:
just after 2.0.2 my plan is to create a maintenance branch for 2.0.x ,
but only for fixing issues that should happen (and then maybe release
a 2.0.3).
So I'm thinking even to move all existing tickets from 2.0.3 to 2.1
because we really need to start real developments on 2.1 ... but I
doubt that someone of us has enough time even to do some backport from
2.1.x to 2.0.x ...
What do you think ?
Bye,
Sandro
Re: release 2.0.2 approaching
Posted by Sandro Martini <sa...@gmail.com>.
Hi Roger,
> Hmmm. I think the maintenance branch depends on whether there is going to be a 2.0.3 or not, and how soon we start on 2.1 features.
Yes, but a safer approach could be that I create a maintenance branch
for 2.0.x (just after 2.0.2 final) and if not needed I can delete it
... BUT to put it in (new) bug-fix only , attention.
> I don't know that we need to make the decision until we start in earnest on 2.1 stuff.
The problem with 2.1 is that there are some really interesting
features (more for a 2.5 release than only for 2.1, just to have an
idea of planned changes) but where maybe we need to change some API
inside, and we really need to start working on it.
One of main features to include (and hard/long to write) is the
abstraction to AWT for example ...
So my trouble here is that I (and probably none of us) has enough time
to do a backport of future features/fix from 2.1 (when started in the
trunk) to 2.0.x, this is the main reason because I didn't open
development of this already.
Of course we can even delay (another time) the start on 2.1/2.5 (I
like much more 2.5 to better mark it as a real transition to 3.0) ...
so my request to other Pivot developers, really what do you think ?
> I'm totally swamped by my release schedule, so I don't know if I'll have time to research / fix the OSX problem for 2.0.2 (I was up until 2:00am last night....)
Ok, don't worry ...
Bye
RE: release 2.0.2 approaching
Posted by "Roger L. Whitcomb" <Ro...@actian.com>.
Hmmm. I think the maintenance branch depends on whether there is going
to be a 2.0.3 or not, and how soon we start on 2.1 features. I don't
know that we need to make the decision until we start in earnest on 2.1
stuff.
I'm totally swamped by my release schedule, so I don't know if I'll have
time to research / fix the OSX problem for 2.0.2 (I was up until 2:00am
last night....)
~Roger
-----Original Message-----
From: Sandro Martini [mailto:sandro.martini@gmail.com]
Sent: Wednesday, May 16, 2012 8:54 AM
To: dev@pivot.apache.org
Subject: Re: release 2.0.2 approaching
Hi Roger ...
> Note that I have reproduced the OSX problem with the input characters
even on Snow Leopard...
Oh, this is great, so we should be able to fix it in time for 2.0.2 !!
Thank you very much, keep me updated :-) .
And on the maintenance-only branch for 2.0.x (just after 2.0.2), what
do you think ?
Bye
Re: release 2.0.2 approaching
Posted by Sandro Martini <sa...@gmail.com>.
Hi Roger ...
> Note that I have reproduced the OSX problem with the input characters even on Snow Leopard...
Oh, this is great, so we should be able to fix it in time for 2.0.2 !!
Thank you very much, keep me updated :-) .
And on the maintenance-only branch for 2.0.x (just after 2.0.2), what
do you think ?
Bye
Re: release 2.0.2 approaching
Posted by Roger and Beth Whitcomb <Ro...@rbwhitcomb.com>.
Note that I have reproduced the OSX problem with the input characters
even on Snow Leopard...
On 5/16/12 3:55 AM, Sandro Martini wrote:
> Hi all,
> since yesterday I started to do usual things just before preparing a
> release (running check scripts for svn, for rat, etc) ...
> I'm sorry but still hadn't time to prepare and upload an updated
> snapshot in my area on people.apache.org .
>
> We are discussing on some other small things but I think that during
> this week we should solve them.
>
> Important:
> the only important issue still open is:
> PIVOT-850 - Fail to take input characters other than English in Mac Lion
> https://issues.apache.org/jira/browse/PIVOT-850
> but note that it happens only in Mac Lion, so it's not-so-bad (for
> others :-) ) ...
>
> I'm sorry here but without a Mac with Lion installed it's impossible
> to reproduce and so to fix (I'm speaking for me, but probably even
> other Pivot developers are in the same situation) ... volunteers here
> ?
>
> Unless objections or important things that should arise, my plan is to
> start the release packaging during this week-end, and publish release
> candidate artifacts on my area on people.apache.org . Of course just
> after this I'll start the vote (max 5 / 7 days of duration).
>
> Please tell me if someone of us need something different or need more
> time (no problem, but I have to know before starting all the work).
>
>
> And now another big question:
> just after 2.0.2 my plan is to create a maintenance branch for 2.0.x ,
> but only for fixing issues that should happen (and then maybe release
> a 2.0.3).
> So I'm thinking even to move all existing tickets from 2.0.3 to 2.1
> because we really need to start real developments on 2.1 ... but I
> doubt that someone of us has enough time even to do some backport from
> 2.1.x to 2.0.x ...
>
> What do you think ?
>
>
> Bye,
> Sandro
>
>