Come on mentors, lets make this happen.
Thanks -Ransford
Dave Johnson <[EMAIL PROTECTED]> wrote:
The code in the Roller trunk, aka Roller 1.3, is stable and has been
running in production at at least one high-traffic site for some time
now. I propose that we release this code now as:
"Roller 1.3 (Incubating)"
The release will be made up of three files.
roller-1.3-incubating.tar.gz - the complete Roller webapp
roller-1.3-incubating-src.tar.gz - Roller source code
roller-1.3-incubating-tools.tar.gz - the jars required to build
from source
According to the incubator docs:
Incubation_Policy.html#Releases%0D>
We need the endorsement of a mentor and the approval of the Incubator
PMC.
So mentors, please advise.
- Dave
On Sep 10, 2005, at 2:59 PM, Allen Gilliland wrote:
> 1.3 is what i am calling the next release of Roller which is what's in
> the current trunk. 1.3 includes lots of stuff including bug fixes,
> the new theme management code which allows for shared themes, and the
> pojo wrappers stuff.
>
> i actually wanted to cut a 1.3 release about 6 weeks ago, but with ASF
> issues going on we couldn't do it. i definitely think we should do a
> 1.3 release ASAP and make that the final release from the 1.x branch.
> once we do that then according to our release plan we would move the
> current trunk to a 1.x branch and move the 2.0 branch to become the
> new trunk.
>
> personally, i don't care much for all these legal issues.
> sourceforge, java.net, asf ... they are all good places for opensource
> projects. if we honestly can't find a way to reconcile the ASF legal
> issues then i suggest we cut our releases from elsewhere until this
> stuff is resolved. i believe someone gave an example of a previous
> incubating project that continued to release code from java.net for a
> while? can we do that?
>
> -- Allen
>
>
> Anil Gangolli wrote:
>
>> I'm confused again.
>>
>> Was there a Roller 1.3 release, or is this a just a Sun BSC
>> deployment?
>>
>> If the latter, can we be a bit more careful with release numbering
>> for the Sun-internal releases?
>>
>> We rely on release numbers in bug tracking and in communications with
>> users, and we need to be able to understand where we are in a cycle
>> to assess what to commit and where, and what we can tell users about
>> when something was fixed or in which release to expect a fix.
>>
>> Also, are we planning any more 1.x releases before 2.0 (assuming all
>> ASF-related topics are covered)?
>>
>> --a.
>
---------------------------------
Yahoo! for Good
Click here to donate to the Hurricane Katrina relief effort.
