I feel that I've already gone far above and beyond the call of duty regarding
this issue. In this particular case I was only focusing on Lubuntu Quantal as
indicated by the title of the post.
Abiword's maintainer has already spoken:
https://bugs.launchpad.net/ubuntu/+source/abiword/+bug/1019621
Le 08/14/2012 10:04 PM, Lance a écrit :
> https://bugs.launchpad.net/ubuntu/+source/abiword/+bug/1019621
Could we keep the discussion on only 1 place (the bug report), so
everyone have the same level of information ?
Just to make it clear, there will be not reversion to 2.8.6 in precise,
it's no
Right now I'm only concerned about Lubuntu Quantal. I want to be sure Lubuntu
12.10 ships with a usable version of 'abiword'.
Next week while testing Ubuntu and Xubuntu 12.04.1 candidates I'll try to raise
the issue regarding Precise which will be much more difficult.
I am of course assuming th
Lance, for quantal I don't know of any restrictions. We should be able
to update abiword as any other package in development. I see
2.9.2+svn20120603-1 is in there now.
For precise, I see an older svn copy of abiword, also 2.9.2. I am not a
ubuntu developer, so I don't know a ton about process
Sorry, I'd not seen this before posting my last reply.
What this really amounts to is disregarding the pkg maintainers advice so we'll
ship a broken version of 'abiword' just out of principle.
That makes no sense to me :^(
Lance
--- On Wed, 8/15/12, Nicholas Skaggs wrote:
From: Nicholas Skag
I'm not sure why SRU would come into play in Lubuntu Quantal since we're still
in development?
Since we started using "proposed" repos in the QQ testing cycle I'd think we
could just make a decision, then the pkg in proposed could be tested and
decided on :^)
What version of 'abiword' should b
Yes, I just had a chat with some folks from the SRU team.. Indeed, this
should be handled as an SRU. However, in order to meet requirements the
update must not cause any regressions or add any new features. In
essence, it must simply fix the bug in question and change nothing else.
By default a
We missed you in the meeting. Please note I do not speak for the release
team. However, at this point, any change is likely to need good reason
and undergo a lot of scrutiny. They don't want to introduce any
regressions, etc. With that said, this seems to me to be a matter of
getting a update p
8 matches
Mail list logo
