2011/2/18 Martin Cooper :
>> Besides it's more about promoting a release. I was asking about that
>> sometime ago. It would be great to promote Betas or RCs without
>> calling for a Vote.
>
> There is no such thing as a release without a vote. Every release must
> be voted on by the PMC, no excepti
On Mon, Jan 31, 2011 at 10:52 PM, Lukasz Lenart
wrote:
> 2011/1/31 Paul Benedict :
>> He he.. I'll give you the answer that I got whenever I wanted to do "beta"
>> releases. Votes determine the quality of the release, not the version label.
>> So 2.2.2 could be production if it's voted that way. W
On Thu, Feb 17, 2011 at 7:35 AM, Lukasz Lenart
wrote:
> 2011/2/17 Wendy Smoak :
> Yep, that's the one of the reasons I have, another is that we fixed 41
> bugs of total 50 assigned to 2.2.2 version. The most important are
> done, the rest is related to JSONPlugin (not everyone uses) or
> develo
On Thu, Feb 17, 2011 at 10:35 AM, Lukasz Lenart
wrote:
> I was looking for that discussion about labeling but didn't find,
> could you help and point to the right direction ? Maybe it was on PMC
> group ?
I poked around on MarkMail and found some discussion in late 2004.
Try this:
http://struts
2011/2/17 Wendy Smoak :
> But does it matter? If you've tested it and it works for your
> project, who cares what the Struts developers think. ;)
No, but it gives me a clear signal what can be the origin of my problem.
> One of the reasons it was done is to eliminate double work. If you
> use v
On Thu, Feb 17, 2011 at 10:01 AM, Lukasz Lenart
wrote:
> The answer is simple: I'm using Maven for development basis and it's
> easy for me to switch between versions. I don't need to go to a web
> page to check if 2.2.2 is a Beta or GA. I see it just in my pom.
But does it matter? If you've te
W dniu 17 lutego 2011 16:07 użytkownik Dave Newton
napisał:
> Why not RCn?
Fine for me, RC or Beta it's just a signal to community, work in
progress, stay tune
Kind regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
Kapituła Javarsovia http://javarsovia.pl
--
Why not RCn?
Dave
On Feb 17, 2011 10:02 AM, "Lukasz Lenart"
wrote:
> 2011/2/17 Wendy Smoak :
>> As release manager you can frame the vote however you want. If you
>> have specific reasons for calling it a Beta release (unfinished
>> feature, API not yet locked down,) then you can mention them.
2011/2/17 Wendy Smoak :
> As release manager you can frame the vote however you want. If you
> have specific reasons for calling it a Beta release (unfinished
> feature, API not yet locked down,) then you can mention them. It's
> unlikely the rest of the dev team will revolt and insist on labelin
On Thu, Feb 17, 2011 at 9:11 AM, Lukasz Lenart
wrote:
> So, is it possible to call for a Vote just with the [] Beta option ?
> If the Votes passes, the release can be officially promoted to Maven
> Central Repo as a Beta, if not, it can be deleted.
As release manager you can frame the vote howeve
I was thinking about that and there isn't possible to release Struts
2.2.2-BETA1, I mean, the intention is to always release a GA version,
but during the Vote process it can be changed to a Beta. My point of
view is more from technical perspective. Before calling a Vote I must
walk through Maven re
2011/1/31 Paul Benedict :
> He he.. I'll give you the answer that I got whenever I wanted to do "beta"
> releases. Votes determine the quality of the release, not the version label.
> So 2.2.2 could be production if it's voted that way. When you put out your
> vote, ask:
>
> [ ] GA
> [ ] Beta
> [ ]
He he.. I'll give you the answer that I got whenever I wanted to do "beta"
releases. Votes determine the quality of the release, not the version label.
So 2.2.2 could be production if it's voted that way. When you put out your
vote, ask:
[ ] GA
[ ] Beta
[ ] Alpha
If it's GA, it's production. Othe
13 matches
Mail list logo
