release schedule

[Robert Yates <ro...@gmail.com>]

There are a couple of in-house projects that would like to depend upon 
and ship abdera.  As we prepare the release schedule we need a somewhat 
stable release of abdera to include in our offerings.  Would it be 
possible to target a first "release" for sometime in July,

Many Thanks,

Rob

Re: release schedule

[Stephen Duncan <st...@gmail.com>]

Should that be a new thread?

I certainly see value in a release of the basic feed parsing/producing
code before the rest is done (the rest being something that needs to
be put up somewhere... Jira or a Wiki... validation, server-side
stuff, etc.)

-Stephen

On 6/20/06, Garrett Rooney <ro...@electricjellyfish.net> wrote:
> On 6/20/06, James M Snell <ja...@gmail.com> wrote:
> > It may sound a bit self-serving in that I wrote most of the code, but
> > the current implementation could be snapshot'd for a first milestone
> > fairly easily given a bit more work on the docs, samples, and test cases.
> >
> > I'm not quite certain how the milestone process works yet, tho.
> > Garrett/Paul, can you advise?
>
> Well, generally speaking the release process works like this:
>
> 1) The project needs to determine what the actual goals of a given release are.
>
> 2) Once that happens, we scramble around making sure all the Is are
> dottend and Ts are crossed with regard to legal stuff and all that
> jazz.
>
> 3) Then, when we've hit the goals for that first milestone, someone
> rolls a release (makes a tag in Subversion, creates the release
> tarballs/zips, etc) and puts it up someplace people can get at it.
>
> 4) The project votes whether or not to let the release out into the wild.
>
> 5) Assuming the project decides everything is cool, we get the
> incubator PMC to vote on the release.  If they accept it, then we
> actually roll it out for users.
>
> So, the first step for us is to figure out what the actual goals for
> our first release are.
>
> -garrett
>


-- 
Stephen Duncan Jr
www.stephenduncanjr.com

Re: release schedule

[James M Snell <ja...@gmail.com>]

I'd say the goals for M1 are pretty simple... produce a stable,
reasonably functional impl for folks to start working with.  Where
"reasonbly functional" means it implements the RFC4287 with no obvious
gaps. Complete Atom Publishing support would not be a goal for M1.
Having Java5 and JDK142 support would be a goal.  Decent docs and
samples would be a goal.  As would self-contained test case (no reliance
 on externally hosted resources).

Thoughts?

- James

Garrett Rooney wrote:
> [snip]
> So, the first step for us is to figure out what the actual goals for
> our first release are.
> 
> -garrett
> 

Re: release schedule

[Garrett Rooney <ro...@electricjellyfish.net>]

On 6/20/06, James M Snell <ja...@gmail.com> wrote:
> It may sound a bit self-serving in that I wrote most of the code, but
> the current implementation could be snapshot'd for a first milestone
> fairly easily given a bit more work on the docs, samples, and test cases.
>
> I'm not quite certain how the milestone process works yet, tho.
> Garrett/Paul, can you advise?

Well, generally speaking the release process works like this:

1) The project needs to determine what the actual goals of a given release are.

2) Once that happens, we scramble around making sure all the Is are
dottend and Ts are crossed with regard to legal stuff and all that
jazz.

3) Then, when we've hit the goals for that first milestone, someone
rolls a release (makes a tag in Subversion, creates the release
tarballs/zips, etc) and puts it up someplace people can get at it.

4) The project votes whether or not to let the release out into the wild.

5) Assuming the project decides everything is cool, we get the
incubator PMC to vote on the release.  If they accept it, then we
actually roll it out for users.

So, the first step for us is to figure out what the actual goals for
our first release are.

-garrett

Re: release schedule

[Garrett Rooney <ro...@electricjellyfish.net>]

On 6/20/06, Robert Yates <ro...@gmail.com> wrote:

> so we have a JDK 1.4.2 port :)  James mentioned that it is being
> discussed as to whether to manually maintain a JDK 1.4.2 branch or have
> it automatically generated from the JDK 1.5 branch.

Sure, I saw the messages from James about that.

I'm just saying that statements like "we are interested in
understanding the timelines for that" don't make a whole lot of sense
to me.  The timeline for that depends on the conclusion of that
discussion, and then on someone taking up whatever task we decide on
(either creating a 1.4.x branch, or setting up the 1.5->1.4 conversion
tools).  We can't possibly have a timeline until at least the first
part of that equation is finished, and even when that's done the
timeline is still the same timeline any open source project works on,
when someone finishes it.

-garrett

Re: release schedule

[Robert Yates <ro...@gmail.com>]

Garrett Rooney wrote:

> On 6/20/06, Robert Yates <ro...@gmail.com> wrote:
>
>> One more thing that I forgot to mention is that we actually need a
>> version of abdera that runs on JDK 1.4.2, so we are also interested in
>> understanding the timelines for that.
>
>
> Well Robert, you're on the list of committers for this project, so the
> best way for you to understand the timeline for that is for you to
> start working on it and tell us how long it's going to take ;-)
>
> -garrett
>
Garrett,

so we have a JDK 1.4.2 port :)  James mentioned that it is being 
discussed as to whether to manually maintain a JDK 1.4.2 branch or have 
it automatically generated from the JDK 1.5 branch. 

Rob

Re: release schedule

[Garrett Rooney <ro...@electricjellyfish.net>]

On 6/20/06, Robert Yates <ro...@gmail.com> wrote:

> One more thing that I forgot to mention is that we actually need a
> version of abdera that runs on JDK 1.4.2, so we are also interested in
> understanding the timelines for that.

Well Robert, you're on the list of committers for this project, so the
best way for you to understand the timeline for that is for you to
start working on it and tell us how long it's going to take ;-)

-garrett

Re: release schedule

[Robert Yates <ro...@gmail.com>]

Robert Yates wrote:

>>There are a couple of in-house projects that would like to depend upon
>>and ship abdera.  As we prepare the release schedule we need a somewhat
>>stable release of abdera to include in our offerings.  Would it be
>>possible to target a first "release" for sometime in July,
>>
>>Many Thanks,
>>
>>Rob
>>    
>>
One more thing that I forgot to mention is that we actually need a 
version of abdera that runs on JDK 1.4.2, so we are also interested in 
understanding the timelines for that.

Thanks,

Rob

Re: release schedule

[James M Snell <ja...@gmail.com>]

It may sound a bit self-serving in that I wrote most of the code, but
the current implementation could be snapshot'd for a first milestone
fairly easily given a bit more work on the docs, samples, and test cases.

I'm not quite certain how the milestone process works yet, tho.
Garrett/Paul, can you advise?

- James

Robert Yates wrote:
> There are a couple of in-house projects that would like to depend upon
> and ship abdera.  As we prepare the release schedule we need a somewhat
> stable release of abdera to include in our offerings.  Would it be
> possible to target a first "release" for sometime in July,
> 
> Many Thanks,
> 
> Rob
>