Hi Nour/all
First off, apols for the huge number of emails relating to SVN commits
and updates to JIRA tickets this morning ... hopefully you all (like me)
have filters in your mail client so that they get automatically shoved
off to an appropriate folder!
The reason for all those updates was that I was just tidying up what is
outstanding to do for our first release. As discussed a week or so
ago, we've decided not to wait until all the documentation is in place,
but just to push out a release with what we have.
What I've therefore done is created a new ticket, ISIS-89, to act as a
placeholder for the remaining documentation, and moved all outstanding
tickets there.
What still remains for our first release are those tickets tagged with
"0.1.2-incubating" (which will be our first formal release). As of
today, there are six in all:
- ISIS-20, which is parent for:
- ISIS-22 - core docs (minor updates, Dan will do)
- ISIS-27 - sql os docs (to confirm with Kevin, else will defer to
ISIS-89)
- ISIS-39 - restful docs (minor updates, Dan will do)
- ISIS-5 - reinstate DerivedFacet (Dan)
- ISIS-9 - fixes to Eclipse templates (Kevin).
I intend to get these all done or addressed for the middle of next week.
What I'd like help with is in the stuff that goes into making a formal
release, such as:
- the RAT tool (what does it do? how is it run?)
- Keys (I've documented how to generate them on our wiki [1], but I'm
not exactly sure how they are used)
- the Release process (I've referenced Donald Woods' instructions on our
wiki [2], but haven't read it through recently)
- anything else?
So, Nour (or anyone else)... what would really help me is if you provide
some guidance through this stuff.
One possibility might be for some hand-holding at the Apache retreat
weekend after next. Best case scenario I'm thinking of is:
- if I got some hand-holding from "those who know" on Friday
- with artifacts all ready for inspection, we could have a vote over the
weekend for release
- all being well, we then push out the formal release on Monday
Of course, it might not pan out like that, but that's what I thought we
might aim for.
Thoughts? opinions? clarifications?
Dan
[1] https://cwiki.apache.org/confluence/display/ISIS/GeneratingPgpKeys
[2] https://cwiki.apache.org/confluence/display/ISIS/ReleaseProcess
On 03/05/2011 13:08, Mohammad Nour El-Din wrote:
Hi Dan I am really lost in the tasks you defined on JIRA, would you
please give me directions where you want my help?
On Tue, May 3, 2011 at 2:39 AM, Mohammad Nour El-Din
<[email protected]> wrote:
Hi all...
I know I've been off for long time, and I already feel guilty about
it. Please I want to re-join and and even take the chance preparing
for the retreat in Ireland.
Dan any specific direction you would suggest me to look at ?
On Sat, Apr 23, 2011 at 11:53 PM, Mark Struberg<[email protected]> wrote:
Then all is fine. We are allowed to compile against jimi, but we must not provide it in our
binary distribution ( -> <scope>provided</scope> ).
Best is to check for the absence of jimi with Class.forName() or likewise, and
just don't provide image manipulation features if its not present.
But for what I've seen this is already done this way, isn't?
LieGrue,
strub
--- On Sat, 4/23/11, Dan Haywood<[email protected]> wrote:
From: Dan Haywood<[email protected]>
Subject: Re: thinking about a release
To: [email protected]
Date: Saturday, April 23, 2011, 9:44 PM
On 23/04/2011 21:57, Siegfried Goeschl wrote:
Is Jimi a mandatory or an optional dependency?
It's a built-time only dependency; it's used by the
maven-docbkx-plugin
to generate our PDFs and HTML.
There's no need for anyone using Isis to install JIMI
manually or otherwise.
Is that ok? else what advice for us?
Thanks
Dan
--
Thanks
- Mohammad Nour
Author of (WebSphere Application Server Community Edition 2.0 User Guide)
http://www.redbooks.ibm.com/abstracts/sg247585.html
- LinkedIn: http://www.linkedin.com/in/mnour
- Blog: http://tadabborat.blogspot.com
----
"Life is like riding a bicycle. To keep your balance you must keep moving"
- Albert Einstein
"Writing clean code is what you must do in order to call yourself a
professional. There is no reasonable excuse for doing anything less
than your best."
- Clean Code: A Handbook of Agile Software Craftsmanship
"Stay hungry, stay foolish."
- Steve Jobs
