>> After the scathing blame-storming attack by Nick (just kidding),
;-)
I have been swimming against the email/work tide - and havent had a chance
to respond.
First of all, on behalf of many people: Hurrah!!!!
IMO All bugs and feature requests should be entered in Jira - otherwise its
very difficult to track them.
I know I have "raised bugs" before (B7) on the newsgroup and they are still
there - but I have no-one to blame for not entering them in Jira, but
myself.
What would be excellent is if once RC1 is released, we have a branch?
We want to be able to have development continue - but also, we want to be
able to fix bugs in RC1 while curring the stream of new ones - so that
branch stabilises.
There are a number of "bugs" that I am seeing at the moment with site
generation etc in CVS HEAD - and it would be nice to see the number of
these diminish.
I am busy trying to isolate them and Jira them.
I understand from other mails, that we are looking at something like next
week for RC1. Thats excellent.
I have a few projects I can test against here - and will be happy to help
in the pre-release testing. Problem is that I am behind a shitty firewall -
so its not so easy.
Is it possible to turn on tarballs on veiwcvs - or is it tightly controlled
by apache?
Thanks again all.
-Nick
Extranet
[EMAIL PROTECTED] - 11/06/2003 00:45
Please respond to [EMAIL PROTECTED]
To: users, dev
cc:
Subject: RC1 release plans
After the scathing blame-storming attack by Nick (just kidding), we've
decided to prepare for a Maven RC1 release.
You can track progress on our attempt to get everything ready for an RC1
via JIRA. All bugs attached to MAVEN-401 will be processed prior to the
release OR I will mail to the user / dev lists if I remove dependent
issues (highly unlikely).
If you have something that positively must be fixed you have one of
three choices
1) Find a compliant committer who will fix the problem for you. No
guarantees.
2) ***BEST PLAN*** Submit a tested patch and then find a committer who
will apply the patch and test it
3) Submit an issue and hope someone takes notice. No guarantees.
Changes to core functionality will probably not be considered at this
stage as we just want to clean up what we have, run it for a few days
and then release it.
Please note: If it's not logged in JIRA, the problem does not exist.
By all means post to the dev list to find out if it is known and listed
somewhere else, but ultimately, don't expect that mailing to the dev
list will get it fixed. IT MUST BE PUT INTO JIRA.
(Committers: Can you funnel changes to the MAVEN-401 dependant issues
through me please - Under NO circumstances unlink issues from MAVEN-401)
We'll be looking to lock down for release end of this week with an
internal release after the weekend and a public release mid week (all
things permitting).
Cheers,
Ben
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This message and any attachments (the "message") is
intended solely for the addressees and is confidential.
If you receive this message in error, please delete it and
immediately notify the sender. Any use not in accord with
its purpose, any dissemination or disclosure, either whole
or partial, is prohibited except formal approval. The internet
can not guarantee the integrity of this message.
BNP PARIBAS (and its subsidiaries) shall (will) not
therefore be liable for the message if modified.
---------------------------------------------
Ce message et toutes les pieces jointes (ci-apres le
"message") sont etablis a l'intention exclusive de ses
destinataires et sont confidentiels. Si vous recevez ce
message par erreur, merci de le detruire et d'en avertir
immediatement l'expediteur. Toute utilisation de ce
message non conforme a sa destination, toute diffusion
ou toute publication, totale ou partielle, est interdite, sauf
autorisation expresse. L'internet ne permettant pas
d'assurer l'integrite de ce message, BNP PARIBAS (et ses
filiales) decline(nt) toute responsabilite au titre de ce
message, dans l'hypothese ou il aurait ete modifie.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
