Bruno,
You can get snapshots from the maven snapshot repository at
http://wicketstuff.org/maven/repository.
Erik.
Bruno Borges schreef:
Martijn, isn't possible to release as an Early Access ? :)
[]'s!
--
Erik van Oosten
http://2007.rubyenrails.nl/
On 5/22/07, Johan Compagner [EMAIL PROTECTED] wrote:
But most api is now stable i think so if stable api was the deciding factor
if something is called beta or rc...
Mostly the open bugs in JIRA is the deciding factor in naming a
release. With 35 (give or take) open issues, I would not call a
really?
open up the eclipse bug database and do a open bug query when the are about
to release 3.3
i bet there are more then 35 issues then ;)
johan
On 5/22/07, Martijn Dashorst [EMAIL PROTECTED] wrote:
On 5/22/07, Johan Compagner [EMAIL PROTECTED] wrote:
But most api is now stable i think
On 5/22/07, Johan Compagner [EMAIL PROTECTED] wrote:
i think releasing one extra beta is fine.
But most api is now stable i think so if stable api was the deciding factor
if something is called beta or rc...
From my point of view, a release candidate is a distribution you plan
to graduate to
What would be the correct naming that the api is stable?
API not stable: Alpha
API stable: Beta
Release 'stable' : RC
?
johan
On 5/22/07, Xavier Hanin [EMAIL PROTECTED] wrote:
On 5/22/07, Johan Compagner [EMAIL PROTECTED] wrote:
i think releasing one extra beta is fine.
But most api is
I'm not sure a beta always mean a stable API, but you can add in the
release notes of a beta that the API is frozen. Look at the eclipse
project, they only produce milestones, and starting at one of them in
the release plan they say the API is frozen.
So if your next distribution is API stable,
On 5/22/07, Johan Compagner [EMAIL PROTECTED] wrote:
i think releasing one extra beta is fine.
But most api is now stable i think so if stable api was the deciding factor
if something is called beta or rc...
From my point of view, a release candidate is a distribution you plan
to graduate to
If there are no objections, I would like to build a distribution based
on thursday's code base, and vote on it during the weekend (giving us
some time to test it), and then submit the release to the IPMC on
monday.
With a bit of luck we can make the release available on thursday next
week (the
Looking at JIRA and some troubles we have on the lists, we won't be
able to pull 1.3 rc1 any time soon.
I therefore propose the folowing schema for the coming weeks:
- release 1.3.0-incubating-beta2
- graduate + transfer to TLP
- release 1.3.0-rc1
- release 1.3.0-rc2
- rename to 1.3.0
WDYT?
Martijn, isn't possible to release as an Early Access ? :)
[]'s!
On 5/21/07, Martijn Dashorst [EMAIL PROTECTED] wrote:
Looking at JIRA and some troubles we have on the lists, we won't be
able to pull 1.3 rc1 any time soon.
I therefore propose the folowing schema for the coming weeks:
-
a very important fix. Download Wicket now!
http://wicketframework.org
--
View this message in context:
http://www.nabble.com/1.3-release-graduation-schema-tf3793132.html#a10731160
Sent from the Wicket - Dev mailing list archive at Nabble.com.
11 matches
Mail list logo